Mid May I presented a methodology to successfully migrate physical PCs to a virtual desktop environment delivered by Citrix XenDesktop. The key area of focus was thereby around the planning and performing of a migration.
During this TechTalk, not all questions could be answered and therefore, I would like to share the related information below. In case you miss a question not being answered or have further questions, please use the comments field and I will get back to you.
Since many of the attendees asked for the presentation, you can download it from here.
I hope the migration methodology provides guidance during a transition from physical PCs to virtual desktops and don’t skip the planning phase since this will ensure a successful migration.
Follow me on Twitter: http://twitter.com/TarkanK
Questions & Answers
Q: What is the best practice for implementing XenApp to deliver applications? A physical or virtual server?
This is a good question. In the past, we followed a best practice “never ever” virtualize a Terminal Server or XenApp server since real-time work was impacted. However, virtualization of workloads made so much progress that this is negligible compared to the benefits you can gain with it. Therefore, if you have a virtualization infrastructure based on XenServer, I would recommend using virtual machines to provide XenApp since you will benefit from the XenApp specific optimizations on XenServer as well as have a more dynamic server management rather than being dependent on a physical machine. Other benefits are definitely around hardware savings, power and cooling costs (even though you will have probably a bigger box for the virtualization infrastructure).
Q: From the application delivery perspective, the slides suggest that streaming is the primary (and recommended) method. Hosted seems to be a secondary method. Why is it *not* recommended to put the “Core” (Office, Adobe Reader, etc.) applications installed on the Virtual Desktop?
The easiest way of delivering apps is probably by installing them into the virtual desktop and you are good to go. There is nothing against this approach. Using this approach for core applications such as Microsoft Office, Adobe Reader is definitely doable; especially considering the fact of Microsoft Office 2007 updates being integrated into the Microsoft Windows Update mechanism simplifies the Office update process.
However, reasons for primarily recommending streaming as the choice for even core apps is mainly driven by the following points:
- Allows virtual desktops being slimmer, especially if hosted apps are used, increasing the number of concurrent virtual machines on a virtualization host.
- Central delivery of applications to virtual desktops, physical desktops, and XenApp servers.
- Simplifies virtual desktop OS maintenance and upgrades
The key for a successful app delivery strategy is that it needs to meet your requirements for app criticality, app type, update frequency, resource usage, and compatibility. Considering these areas may even lead to an app delivery solution leveraging all three methods. My coworker Daniel Feller already created a blog Simplifying Application Delivery into the Virtual Desktop that gives some insights as well.
Q: What is the tested maximum number of Windows XP virtual desktops in a single XenDesktop farm?
We are conducting regular tests based on the latest XenDesktop release version to verify scalability of a XenDesktop farm. However, bear in mind the fact that XenDesktop is a collection of components that interact with each other and each components scalability such as Desktop Delivery Controller, Provisioning services, and virtualization infrastructure may impact the overall architecture. The most recent test results (that were shared during the Citrix Synergy session “iForum221 – Advanced strategies for virtual desktop scalability”) simulated a XenDesktop farm with a 9 am logon storm scenario. In this scenario, the XenDesktop farm could easily handle 4,500 logons to virtual desktops within 15 minutes and the peak CPU utilization was at 60% and memory at 2 GB (used hardware specs: dual quad-core, 1.8 GHz, 16 GB RAM). Once the Desktop Delivery Controller brokered a connection, it is not very active. Therefore, the next stop for scalability to look for is Provisioning services and the virtualization infrastructure. In this case factors such as used server hardware or virtual server configuration impacts the scalability and the virtual desktop type (user, OS, workload).
Q: Migrating from physical desktops to virtual desktops, how do you calculate how many users you can get on a server?
This is exactly the point, where the assessment as part of the planning phase is important to have. Therefore, you should assess the following:
- Target virtual desktop OS type – Windows XP, Windows Vista, or Windows 7
- Desktop hardware requirements (CPU, memory, network) to apply the right configuration to virtual machines
- Storage space
Based on this information and the target server hardware running the virtualization infrastructure will allow you a better sizing estimate. Better is to run a scalability test on at least a single server.
Q: Where would you start the migration process for a company with 200 users and 7 different departments?
As part of the migration planning, one action item is definitely to define the migration process. To do so, there are some factors influencing this process, which is not solely depending on the number of users or departments:
- Hardware refresh requirement
- OS upgrade requirement
- User groups
- Maintenance schedules
This should allow the prioritization of where to start and how to sequence the migration process.
Q: Users will want their music files (currently stored on desktop). We have cheap disk but it’s only available as NFS (putting this on the SAN is not an option due to expense of storage and low business value of the MP3s). Any idea how we could make this work, maybe by dynamically creating an NFS mount for each user, say an E drive?
One key benefit of XenDesktop is the user experience provided by HDX (High-Definition user eXperience). Leveraging this capability allows mapping of USB drives or local drives of an endpoint into a virtual desktop running in the datacenter. This provides users’ access to their files, in this case MP3s and therefore, IT does not need to handle this. However, IT should consider related security measurements and the impact on LAN/WAN usage if users have large files to copy.
Q: Can you share a base image disk among multiple desktops?
This is the key benefit of Provisioning services to provide a vDisk to be shared by multiple desktops. These are the available vDisk types:
- Standard Mode – read only OS image and shareable with multiple desktops
- Private Mode – read/write OS image and is assigned to a single desktop (not shareable)
Q: Is there some type of sysprep or utility that needs to be run every time the vDisk is opened up? Does Provisioning Server handle this and dynamically provide a Windows hostname when a Virtual Desktop is booted up?
Provisioning services does not require sysprep to allow sharing of a single vDisk by multiple virtual desktops. Once the “golden” image has been created, Provisioning services takes care about computer accounts and the computer account passwords within the Active Directory. This is also the reason, why Provisioning services should be setup with domain administrator rights. A more comprehensive overview of this process is described in the Provisioning services Administrator’s Guide - section “Managing Domains and Active Directory Integration”.
Q: If the master image gets updated on Saturday after all users have logout, will there be any delay in OS delivery when the users come in next Monday?
If the master image has been updated on Saturday and you know how many logons you have simultaneously on Monday, you can adjust the setting “Idle Pool” of a Desktop Group. This Desktop Group setting allows you to configure how many idle desktops (booted and waiting at the Windows logon screen) you want in your pool at certain times of the day. You can also configure a peak period to cover the time at which most users will be logging on to their desktops. This period starts at the beginning of your business day.
Q: How do you manage (add/delete) applications on the golden image? Is there a tool to do this?
Due to the fact that the golden image is a read only OS image and this golden image needs to be started in Private Mode (read/write). If the OS or applications need to be updated in the golden image, the best approach is:
- Take a copy of the file and rename it to reflect a newer version
- In Provisioning services, change the newer version of the golden image into Private Mode
- Assign this golden image to a virtual machine and boot from it
- Apply required changes and updates
- Shutdown virtual machine
- In Provisioning services, change the updated golden image into Standard Mode and assign it to the virtual machines
There is also a way to automate the assignment if the Provisioning services option “Automatic Updates” is selected and versioning of golden images is used.
Q: Is there a way to have two (2) different DHCP´s with only one XenDesktop farm?
Sure, however the DHCP scopes should not conflict in order to avoid duplicate IP addresses. As part of a redundant DHCP solution this would be Microsoft best practice called split scope DHCP.
Q: How is a dual monitor connected?
There is no requirement for any specific configuration on the endpoint device to support dual or multiple monitors for a virtual desktop. Multiple monitors are detected on endpoint device and virtual desktop is displayed across all monitors. A single virtual desktop can span up to 8 monitors in a rectangular shape (e.g. 1×8, 2×4), where each monitor must have the same resolution.
Q: How do I solve the road warrior without Internet? Is there a checkout feature available today or being planned?
At the current stage XenDesktop does not have a feature to support offline usage of virtual desktops. However, the showcased XenClient during Citrix Synergy will provide this capability in the near future. This is being developed as Project Independence.