Our community is talking about the new Dell Technologies. Join the discussion in the Dell EMC Community Network:
Quest Software will be at the following SharePoint Saturdays this summer (and more as they are added!).
SharePoint Saturdays are a great place to network and learn about SharePoint from your peers, experts and MSFT MVPs. In fact, if you’ve heard of SharePoint, you’ve likely heard about or attended a SharePoint Saturday…Do you remember when they began?
It was a cold day (well, I assume it was cold!) toward the end of 2008 when Michael Lotter, Susan Lennon and Kevin Israel began planning the first event. In January of 2009, the very first SharePoint Saturday was born. It took place in Virginia Beach. Within one year, 32 events happened across the globe! The original idea was supposed to be a single event in NYC but, says Lotter, it turned into a “SharePoint Community Craze”. Now, there is rarely a Saturday that goes by that is “SharePoint free”. These events are put together by a non-profit organization – SharePoint Saturday.org. The people who put them together are volunteering their time and energy to make them happen…and it’s a lot of time and energy.
I think a thank you is in order here....Thank you to all of the volunteers, committees, organizers, speakers, sponsors, vendors and attendees. Thank you for taking time out to put on these amazing events and to continue to build on the strong networking and camaraderie that is the SharePoint Community. And, I hope to see you at a SharePoint Saturday soon!
We'd all love to hear your comments about SharePoint Saturday - please leave them below or contact me at email@example.com and I'll add them!
Migration Suite uses Microsoft Outlook and your Outlook profile to enumerate and retrieve public folders and items. Depending on how Windows and Outlook are configured on the computer, you may see the following warning when accessing mail folders from the Connections pane:
It might not be easy to notice the window as it is not brought into the forefront, but instead blinks in the Task bar. You can allow access to Migration Suite temporarily using this window, but the longest period it can be suppressed is 10 minutes. Which is okay for a quick test, but becomes a pain for a larger production migrations.
The reason why this warning is displayed is the default Outlook setting that warns the user when a program tries to connect to Outlook programmatically and there is no or outdated antivirus on the computer to handle the potential threat.
To locate the setting, open Outlook Options , select Trust Center and click Trust Center Settings. Then select Programmatic Access:
You can switch off the feature completely for the time of migration, but installing/updating the antivirus software on the computer is not a bad idea either.
One of the great new features that we introduced in vWorkspace 7.5 was the ability to (very) quickly deploy virtual Remote Desktop Session Hosts (RDSH)/Terminal servers using Quest’s Hyper-V Catalyst components HyperCache and HyperDeploy. You can find some more information on RDSH provisioning here
In Quest Workspace Desktop Virtualization 7.6 (QWDV and formally vWorkspace) we have improved this feature again. It’s on the surface a small change but it’s very helpful for the administrator especially if you have a large number of published applications. Now when we deploy new RDSH server we will automatically assign (publish) the existing published applications to the new deployed RDSH servers.
The video demonstrates the provisioning of virtual RDSH servers (in real time, 102 seconds) and the automatic publishing of the applications.
During the next couple of weeks we will discuss these and all the other new functionality in much more detail right here on our blog, so make sure to stay tuned for that. In the mean while we understand that you will want to have a look for yourself. There’s nothing we would like more. Here are some things you can do to learn more:
This blog post is written by Kiran Poluri and Krishnaprasad K from Dell Hypervisor Engineering team.
When upgrading from Dell customized VMware ESXi 5.0 to a later update using Dell customized VMware ESXi 5 ISO image, it fails with an error message as shown below.
This error occurs since the later versions of Dell customized VMware ESXi 5 ISO image carries different VIB name which provides the same set of files compared to Dell customized VMware ESXi 5.0. The upgrade is not successful when you encounter this issue. Once you reboot from this error prompt, it rolls back to ESXi 5.0. There is no data loss or configuration loss due to this error. Follow one of the below methods to resolve the issue before upgrade or after the issue is seen.
Method1 From the ESXi 5.0 shell, run the following commands. ~# esxcli software vib remove –n Dell-Configuration-VIB ~# esxcli software vib remove –n Dell-License-VIB
Once the command execution is successful, start upgrading using Dell customized VMware ESXi 5 ISO.
Method2 Use VMware native ESXi 5 ISO image or VMware upgrade package to upgrade from Dell customized VMware ESXi 5.0.
I was working on an upcoming presentation for next month’s SPTechCon in Boston, and I was reviewing some prior materials on SharePoint governance and security management.
SharePoint information architecture can be hard. When IA is done correctly, contexts and navigation flow smoothly. Users are more likely to put documents in the “right” place and keep them there. Conversely, if users aren’t sure where to put a new document or find an existing one, they may create their own version or add a new site. And the more points of entry you have the more places you may need to control or inspect for improper security. Native functions, and solutions like Quest’s Site Administrator for SharePoint can help catalog and rein in an unruly information architecture – but ultimately, this is an information governance question.
What occurs to me is the same problem on a large scale. It can become really convenient to add documents for convenience sake to multiple different areas. I’ve added extra documents to SharePoint Team Sites, My Sites, SkyDrive, and Drop Box as I’ve demoed different aspects for each for collaboration. And I noticed that, of course, I don’t keep all the copies in sync. It’s not really critical if all I need to do is shows the Word Web App client as part of SkyDrive.
In ordinary collaboration, many users inadvertently “extend” their IA when they share docs via e-mail. “I’ll just email it to myself so I can work from home this weekend” is a starting point. Pretty soon, versions of the same content are showing up in Office 365, corporate SharePoint, Google, Facebook, Drop Box, YouSendIt, etc. That’s not a bad thing – if you can remember where all the copies are.
And lets even suppose you have a handle on all the required user security for each of those locations. What could possibly go wrong?
Not all clouds are good clouds…
We may be “One World” on the Internet – but we are far, far away from One World of regulations. On one hand, we have applications of US-based regimes like HIPAA which mandate that certain classes of health related personal information cannot leave US controlled servers. And on the other hand, some non-US companies are careful to keep their corporate data away from US-based “cloud” services because of the international impact of USA PATRIOT and other regulatory regimes.
Clear guidance on intended usage helps. Information governance is as much about policy as enforcement. But sometimes the best approach is one that steers people toward “preferred” collaborative stores, so user behaviors don’t inadvertently create security or regulatory issues. (This is part of the rationale for our AttachThis solution, now in public beta.)
What do you think? How do you engage information sprawl outside SharePoint?
Earlier we held our Five Pillars of SharePoint Governance – Supportability webcast featuring Jason Himmelstein of Sentri and Chris McNulty (get the recording here).
Now you can take a more in-depth view as to how Quest Software can help you implement the supportability portion of your governance plan.
The Five Pillars of SharePoint Governance – Supportability (a tech brief)
Read the Tech Brief >>
Though SharePoint can be easily customized to make it almost anything you need, that flexibility can also create a supportability nightmare for administrators. Random custom coding and content that can’t be migrated are only half the problem. The other half is supporting end-user requests in a reasonable time.
In this tech brief, you’ll get helpful insight into the key areas of supportability that every organization should consider when planning their governance program.
You’ll also learn how Quest solutions for SharePoint can address these key supportability concerns, making it easier for you to support your environment and your users, as well as ensure customizations are supportable and upgradable in your environment.
Today Dell released an BIOS update that affects many of our Dell PowerEdge 12th Generation servers. The BIOS update includes a change which can improve system performance with many Linux distributions.
First, a little background: Systems with NUMA architecture have memory that is connected to a particular CPU socket. So, on systems with more than one CPU socket, this means that each CPU can access some memory (the memory connected directly to it) faster than other memory. This isn't new--this architecture has been used in previous generations of Dell servers as well as our new 12th Generation servers. ACPI tables provided by system firmware (BIOS) provide the details to the operating system so that it can make sure that the right memory is used by the right CPU, to minimize memory access times.
In our 12th Generation servers, each PCI device is also "closer" to one of the CPUs in the system (and also closer to the memory connected to that CPU), unlike our previous generations of servers. With the BIOS update released today, this PCI proximity information is also provided to the operating system, so that it can ensure that the optimal CPUs are talking to the PCI devices when they need attention, and to make sure the memory with the fastest access times is assigned for use by the PCI devices.
This can increase performance when using Linux distributions, such as Red Hat Enterprise Linux 6 and Novell's SUSE Linux Enterprise Server 11. Note that this change will only affect systems with at least two occupied CPU sockets, and node interleaving must also be disabled in BIOS setup. (Node interleaving masks the effect of certain CPUs and PCI devices being closer to certain memory, which is useful with older operating systems that don't understand NUMA architecture.)
In a previous feature spotlight we talked about the User Workspace Context Feature of QWDV (vWorkspace) 7.6. That blog post detailed exactly what information User Workspace Context provided. In this blog post we will have a look at how IT can use that information to provide the best possible workspace for the user.
With QWDV (vWorkspace) 7.6 you have the ability to use part of the User Workspace Context in an advanced target. Specifically you can use the Connector Type, the Connector Version and the Web Access Site:
The Connector type advanced target condition allows you to specify the type of Connector. As usual, you have full control: allow all or nothing and every possible combination in between.
Our early discussions with customers about this functionality revealed many interesting scenarios for this feature, amongst the most interesting where
The 'Connector Version' advanced target condition is great for customers who want to control which versions of the QWDV Connector can be used to access the user workspace.
This could be great for customers who have a (internal) support guideline that only supports certain version of the QWDV Connector or customers that want to allow access to a certain multimedia only from the latest QWDV Connector because of performance improvements.
Web Access Site name
The final new advanced target type condition allows customer to specify which Web Access site must be used in order to get access to a certain QWDV resource (application for example):
You can select from a list of Web Access sites that the QWDV farm hosts. This functionality has been in popular demand by our MSP customers who host multiple Web Access sites for multiple customers (on the same Web Access servers). This allows them to prevent customer A to use Web Access site B that is designated for customer B.
That’s it for now. We hope that you are as excited about Quest Workspace Desktop Virtualization (formerly vWorkspace) 7.6 as we are! Please let us know what you think - also using the (new) social sharing buttons on the top right of this post.
At the recent International Supercomputing Conference (ISC) in Hamburg, Germany, Dell's Martin Hilgeman of the Global HPC Group, sat in the Hot Seat, as he handled a barrage of questions from Rupak Biswas of NASA Ames Research Center, and Addison Snell of Intersect360 Research.
After a brief introduction of high performance computing (HPC) at Dell, Martin fielded a variety of questions ranging from HPC differentiation, to storage, to building HPC ecosystems. Below are a few highlights:
The Power To Do More
In his introduction, Martin discussed how Dell is focused on creating systems that are powerful, capable and efficient. And of course, Dell is focused on doing this by using Open Standards & common building blocks – as opposed to proprietary technologies.
In talking about Dell’s HPC strategy, Martin displayed this graphic that accurately tells the story. Dell is about creating simple solutions that are derived partially out of innovative collaboration with top research institutions such as Cambridge University and the University of Texas and the Texas Advanced Computing Center (TACC). Finally, to complete the strategy, Dell partners where it makes sense.
Hot Seat Answer Sound Bites
“ … I’m glad we are being recognized as an efficient integrator …”
“ … accelerators will be come increasingly more important in the future …”
“ … we do work with the Lustre community and publish our data …”
You can view the entire Hot Seat session here.
written by Jerry Clement, Dell Enterprise OS Engineering, Project Manager/Engineer for Citrix XenServer
Dell is continually working with our OS vendors to get native driver support in the latest version of the OS to support our new peripheral offerings. As was the case for the Dell PowerEdge 12th Generation Servers. We worked closely with Citrix to get native drivers into XenServer 6.0 to support our new peripherals. For instance the really cool Dell Rack Select Network Adapter options that provide flexibility in choosing a LOM subsystem that is right for your infrastructure. Unfortunately the schedules for the projects never aligned in our favor. Citrix launched XenServer 6.0 before we were able to lock down all the required driver versions that were in development for the 12th generation servers, but we have an excellent partnership with Citrix and we were confident that we could find a solution. We identified the required drivers and Citrix agreed to post driver disk supplemental packs on the XenServer 6.0 download page at mycitrix.com to support our 12th generation servers. Thank you Citrix and all of the engineers who made it possible.
We do a LOT of installs during the initial testing of an OS. So while testing XenServer in our OS Engineering Lab here in Austin, Texas, we tried setting up a PXE installation to speed things up. It was impossible to include a network card driver disk supplemental pack into the PXE installation. It was a "chicken or the egg paradox" and it became obvious that in order for the PXE install to work; we would have to install an older network card that was supported by a native driver. This just wasn’t a viable option because we would not expect our customers to do hand installs with the driver disks or install an older network card on a new server to get it done with PXE. Can someone please help?
Well, Citrix in the 11th hour provided us with a win/win solution that made us all very happy. Citrix agreed to release an updated version of XenServer 6.0 to nicely coincide with a new XenDesktop release and our 12th Generation server launch. All of the driver disk supplemental packs previously qualified for XenServer 6.0 were included as native drivers in XenServer 6.0.2.
Yes! Fist Bump? No? ok.. Anyway...
This update now allowed us to set up our PXE installs without having to take any extra steps. It is very satisfying to install from the XenServer main.iso and not have to make any other accommodations. Oh, Did I mention that XenServer 6.0 has a simplified installer. Previous installations required two iso files. Now, host installations only require a single iso... nice! Mentioned... check!
If you are planning to install XenServer on your new Dell PowerEdge 12th Generation Server, we recommend downloading XenServer 6.0.2. It will save you some time and simplify your install. Purchasing a Dell PowerEdge 12th Generation Server and running XenServer 6.0.2 is a great choice. Citrix has made some excellent improvements to XenServer 6.0 and 6.0.2... Here are just a few of the improvements:
Enhanced Guest OS Support. Support for Ubuntu 10.04 (32/64-bit). Updated support for Debian Squeeze 6.0 64-bit, Oracle Enterprise Linux 6.0 (32/64-bit) and SLES 10 SP4 (32/64-bit). XenServer 6.0.2 also now includes CentOS 5.7 (32/64-bit), CentOS 6.0 (32/64-bit), Red Hat Enterprise Linux 5.7 (32/64-bit), Oracle Enterprise Linux 5.7 (32/64-bit). Experimental VM templates for Ubuntu 10.10 (32/64-bit) and Solaris 10.
Host Architectural Improvements. XenServer 6.0 now runs on the Xen 4.1 hypervisor, provides GPT support and a smaller, more scalable Dom0.
Networking Improvements. Open vSwitch is now the default networking stack in XenServer 6.0 and now provides formal support for Active-Backup NIC bonding.
XenServer is a great choice for anyone wanting to learn about virtualization because... it can be used for Free! And there are plenty of resources available to help you get started. Speed Reading 101 is a prerequisite!
Having Citrix as a trusted partner is certainly proving that we are "Better Together." Tell us about your success with XenServer.