My name is Ajay Kumar and I am a developer on the Remote Desktop Virtualization (RDV) team. In Windows Server 2012 (WS2012) we introduced a new feature for VDI deployments, which allows admins to automatically create multiple virtual machines (VMs) using a single image as input and deploy them as a virtual desktop collection. These virtual desktop collections, where VMs are automatically created by Remote Desktop Services (RDS) are referred to as managed virtual desktop collections.
In a previous blog post my colleague Omair Gillani has already demonstrated how an admin can create a Remote Desktop Services deployment and a managed virtual desktop collection using Windows PowerShell. In this blog post I will share some more details about managed virtual desktop collections and how an admin can use single Master VM to create and update hundreds of VMs in a managed virtual desktop collection (Single Image Management).
A Master or Gold VM is formally referred to as “virtual desktop template” in the WS2012 Server Manager UI console and the cmdlets in Remote Desktop Services module for Windows PowerShell. It is an input to the managed virtual desktop collection creation process that allows an admin to manage a virtual desktop collection. The Master VM is created and managed by the admin and it specifies the hardware properties and software contents of all the automatically created VMs in that managed virtual desktop collection. For example, if the master VM is assigned 2GB of RAM, then each of the automatically created VMs in the managed virtual desktop collection will be assigned 2GB RAM.
In this section, I will describe the various supported options and requirements for the Master VM.
To automatically update all the VMs in a pooled virtual desktop collection, the admin has to first apply the desired changes to the Master VM manually (for example, increase RAM from 1GB to 2GB or apply a software patch). Once the Master VM has been updated the admin can use either WS2012 Server Manager console or Windows PowerShell to push the updates to all the VMs in a pooled managed collection.
To update the VMs in a pooled virtual desktop collection using the WS2012 Server Manager console please follow these steps:
Here is an example of the Update-RDVirtualDesktopCollection cmdlet which can also be used to push updates to the VMs in a managed pooled virtual desktop collection:
PS C:\> import-module RemoteDesktop PS C:\> $time = Get-Date PS C:\> Update-RDVirtualDesktopCollection -CollectionName MyPooledCollection -VirtualDesktopTemplateName masterVm -VirtualDesktopTemplateHostServer Host1.contoso.com -StartTime $time.AddDays(1) -ForceLogoffTime $time.AddDays(2)
During the update process, The Master VM is exported again and a new Master VM copy is created on the collection storage. All the VMs in the managed pooled virtual desktop collection are recreated by the Remote Desktop Services using the newer copy of the Master VM. Once the update process is complete and all the VMs in the collections have been successfully recreated, the Remote Desktop Services delete the old copy of the Master VM from the storage.
I would like to clarify that although a Master VM can be used to automatically create VMs in both types of collections (pooled and personal virtual desktop collections) but it can be used to update only the pooled virtual desktop collection VMs. Master VM cannot be used to push updates to existing VMs in a personal virtual desktop collection.
The update process for managed pooled virtual desktop collection provides three options to the admin to decide when\how the updates will be applied to a managed pooled virtual desktop collection:
If an admin selects the option a) and provides a time period, the update process for pooled virtual desktop becomes aware of the active user sessions on the VMs in the pooled virtual desktop collection. Only the unused VMs are updated during this time period. If a user logs off on his own before the end of the admin specified time period, the VM will be automatically queued up for the update process. At the end of the time period the users, which are still active on non-updated VMs, are forcefully logged off from the non-updated VMs and the update process for these remaining VMs will start.
All the VMs (updated\non-updated) in the collection are available for the user connections during this time period, except for the VMs on which update is in-progress.
In the previous section I have already given a PowerShell example for the option a). Here is a PowerShell example for the option b), which starts updating the VMs in the collection forcefully as soon as the Update-RDVirtualDesktopCollection cmdlet is executed:
PS C:\> import-module RemoteDesktop PS C:\> Update-RDVirtualDesktopCollection -CollectionName MyPooledCollection -VirtualDesktopTemplateName masterVm -VirtualDesktopTemplateHostServer Host1.contoso.com
Here is a PowerShell example for the option c), which starts updating the VMs in the collection forcefully at the specified time:
PS C:\> import-module RemoteDesktop PS C:\> $time = Get-Date PS C:\> Update-RDVirtualDesktopCollection -CollectionName MyPooledCollection -VirtualDesktopTemplateName masterVm -VirtualDesktopTemplateHostServer Host1.contoso.com -ForceLogoffTime $time.AddDays(2)
In all of the three examples above, the input values of cmdlet parameters -CollectionName, -VirtualDesktopTemplateName and –VirtualDesktopTemplateHostServer represent the variables that are specific to a deployment.
While trying these example cmdlets, please replace these names with the appropriate values in your deployment.
To summarize, the managed virtual desktop collections in WS2012 make it really easy for the admin to create and manage hundreds of VMs using a single Master VM as the template. In this blog post I have tried to describe the role of a Master VM in a managed virtual desktop collection and the supported options for a Master VM. I have also described how an admin can use Master VM to roll out updates to managed pooled virtual desktop collections. I hope you will find it useful while creating and updating VMs in your managed virtual desktop collections.
Looking forward to your questions and feedback,
great work beautifully documented.
was a great help.
Great Article , Straight to the point .
Thanks :) .
I am having a problem with using Server 2012 Remote Desktop Services with Windows 8 Remote Desktops. It is an issue with the Windows Store not transfering between Virtual Desktops. I don't know if you can help or maybe direct me to another team at Microsoft.
We are deploying VDI 2012 managed pooled for Windows 7/8.
1. Do we need to activate the master gold template if we plan to use MAK key for virtual desktop? Which mean enter Windows activation key prior sysprep.
2. Do we need to activate the master gold template if we plan to use KMS key for virtual desktop? Which mean enter Windows activation key prior sysprep.
3. Refer to question #1, if we activate the Windows with MAK and sysprep in the master gold template. Does the pooled virtual desktop do need to perform Windows activation whenever user login since the pooled virtual desktop will roll back to initial clean stage?
4. Refer to question #2, if we activate the Windows with KMS and sysprep in the master gold tempalte. Does the pooled virtual desktop do need to perform Windows activation whenever user login since the pooled virtual desktop will roll back to initial clean stage?
5. On the user profile disk, noticed that the quota size cannot be modified(grey out) after the collection was created. Any way to change it? What will happen if the user hits the quota limit of user profile disk? Any alerts or warning notified user when hit the quota limit?
6. Does the VDI desktop support 64 bits of Windows 7 SP1 and Windows 8?
how about sysprep requirement everytime, after 3 rearm it does not allow to sysprep
@ Prasanta Kumar Panda:
For Win8, you could sysprep the master\template VM any number of time; the rearm limit of 3 has been removed.
For Win7, you could workaround the max rearm limit in two ways:
1. As I have explained in the blog above ( #4 under "Master (Gold) VM in Managed Virtual Desktop Collections"), Take a snapshot on the master\template VM AFTER you are done installing patches\updates\applications and just BEFORE you are about to run sysprep. First take the snapshot and then run sysprep and then use the master VM to create\patch the virtual desktop collection. After the create\patch collection operation is complete, you could apply the snapshot on the master\template VM to revert it to the state it was in before the sysprep was executed and delete the snapshot. This last step will reset the rearm count to initial value in the master VM.
2. Run sysprep command with an unattend file which will cause rearm count not to increase.
a. Configure skip rearm unattend setting as per: technet.microsoft.com/.../cc722350(v=ws.10).aspx
b. Place the unattend file (e.g. see one attached from Rajesh) into some location c:\unattend.xml
c. Run sysprep.exe /generalize /shutdown /oobe /mode:vm /unattend:C:\unattend.xml
d. Then when you boot up this image again and it goes through specialize, it’s not going to use the rearm setting.
Regarding the activation, Windows Server 2012 VDI only support KMS activation method. You have to activate the master\template VM with the Windows version specific KMS Key and make sure that your KMS Server is auto discoverable.
The snapshot on the automatically created pooled collection VM is taken before KMS activation is initiated from the guest OS. So the KMS activation would take place only after user logs on. And if rollback is enabled, the pooled VM will rollback to clean state and may perform the windows activation again when any user logs on to the VM again.
If rollback is not enabled on the collection then no snapshot is taken and the VM will activate only once. In this case it will only require activation again when the pooled collection VM is recreated with a patched master\template VM.
There is no way to change the user profile disk size after pool creation and there are no alerts shown (to user or Admin). The user profile VHDs are "dynamic" VHDs which grows in size as user data grows. So an admin could set the user profile VHD size to sufficiently large value during collection creation.
Only way to increase the user profile VHD size after collection creation is by using hyper-V manager console->edit disk option or by running a hyper-V WMI script which edits the disk to increase the maximum size of the user profile VHD.
Yes Windows Server 2012 VDI does supports 64 bit versions of Win7 SP1 and Win8.