A snippet from the upcoming Microsoft Windows Server 2008 R2 Remote Desktop Services Resource Kit:
I ran into a few obscure errors when implementing RD Virtualization Host with pooled and personal VMs, so I thought I would share them with you and save you some troubleshooting time!
WAKING THE VM…
When a user tries to access a pooled or personal VM they may get this message: “Waking the VM…” and an eventual timeout. Meanwhile, you can clearly see the VM "waking up fine in Hyper-V Manager...
There are a few reasons for this, all of which stem from not having the endpoint (the VM) configured correctly. You will receive this cryptic message for the following reasons:
- The endpoint has not been prepped properly. You will experience this situation when any of the prep work was not done including the exceptions in the firewall, the registry entry adjustments, or the wmic commands
- The endpoint was prepped properly but the Rollback snapshot was taken before the prep work was finished and had reverted the endpoint to a state that is no longer prepped properly.
UNABLE TO VERIFY SETTINGS IN THE RDP FILE...
Another scenario that gives obscure event log errors is one in which the Connection Broker has issues connecting the client to the requested endpoint VM. The user tries to initiate a connection to a pooled or personal VM. They receive an error message saying that the connection could not be established because the Connection Broker was unable to verify the settings in the RDP file. On the Connection Broker the following two errors are logged in the TerminalServices-SessionBroker-Client event log:
Event ID 1296:
Remote Desktop Connection Broker Client failed while getting redirection packet from Connection
User : ASH\kristin
HRESULT = 0x80070490
Event ID: 1306:
Remote Desktop Connection Broker Client failed to redirect the user ASH\kristin.
HRESULT = 0x80070490
Remedy this situation, re-running the Configure Virtual Desktops Wizard on the RD Connection Broker server. You do not need to change any of the settings (unless they are wrong of course). Just re-run the wizard with the same settings as you had before, and the Connection Broker will resume working properly.