Hi all,
Thanks for taking the time to read.
We have 7 servers configured for our testing of Microsoft's Virtual Desktop solution.
All servers are Windows 2012 standard (x64) with roles installed as follows:-
1 x Web+Gateway
1 x Broker
3 x Virtual Desktop Host
2 x Session Host
All servers are fresh installs with roles configured with no apparent issues.
Via the web frontend the RemoteApps via the session hosts work perfectly and indeed the Virtual desktops also work OK apart from them not rolling back to the RDV_ROLLBACK snapshot.
* The Virtual Desktop OS is Windows 7 Pro (x86).
* VM Template created with all windows updates and KMS client key.
* Firewall disabled on the desktop.
* Template SYSPREPed using OOBE, shutdown and Generalize options.
* Pooled Virtual Desktop collection created successfully with Rollback enabled from the shutdown SYSPREPed template.
The pool creation is actually only successful if I add the computer account for the Broker to the local admins group on the RDVHost server. I'm wondering if that could be a clue to the problem I am having with the Rollback?
If I do not add the broker to the local admins group I get an error stating the following:-
"Could not identify the state of the virtual desktop. Ensure the RD Virtualization host server SERVERNAME is available on the network and that the virtual desktop PRC-Template is shut down."
To clarify - the RD Virtualization host server IS available on the network as its the very same server I am using to generate the new collection, ie its the one that holds the template and is the one I am working on. The PRC-Template IS shut down after the
SYSPREP.
We have our servers configured on one VLAN and the Virtual Desktops are available on another. Even if I create them temporarily on the same VLAN as the servers the collection creation and Rollback problem still exists.
I know there is at least one other thread on here where someone else is having similar issues with the template but its the Rollback issue that's my main concern at the moment.
Apologies for muddling with 2 issues but I am genuinely not sure whether or not they are related.
What logs do I need to be looking at to work out whether Rollback is actually being attempted and if so why is it failing.
I have checked the various TerminalServices-TSV, Hyper-V and Rdms-UI logs on the servers but cannot see anything obvious but of course I may have missed something.
What is it that triggers the rollback, at logoff what actually happens in order to kick off that process?
Incidently I can manually rollback to the RDV_ROLLBACK snapshot without any errors.
Many Thanks for any help and advice you may be able to offer.
Lynton