Tuesday, April 24, 2012 2:50 PM
I have 5 Hyper-V servers clustered and attached to SAN storage, also I have SCVMM R2 SP1 (VDI-VMM) that manages these hosts and their VMs. I am using RD connection broker and session host (VDI-CB) for redirecting to the VMs with the VMM RDP Connector plugin.
When I connect to the VDI-CB it redirects me to my assigned VM successfully. But when the VM moves from one host to another, and try to connect to it through VDI-CB it displays a message "Waking up virtual machine." which is already awake and ready after the migration process, after a while everything gets back to normal.
Since I have installed the VMM RDP Connector and configured it successfully, I find this issue very weird and plus unacceptable in the production, please can anyone help me fixing this issue.
Tuesday, April 24, 2012 3:16 PMModerator
Are you using DNS to connect? And is DNS resolving correctly?
If the VM is powered off when it moves and the MAC is set to dynamic it will get a new IP address and then you have to wait for everything to update.
Time lags like this with VM moves are common problems with Live Migrating VDI VMs. How quickly the VDI brokwer infrastructure adapts to the change is an issue.
If you have a dependancy on SCVMM this refresh can take minutes, easily. As you have to wait for SCVMM to refresh and the broker to notice and then it needs to refresh.
Learn. Apply. Repeat.
Disclaimer: Attempting change is of your own free will.
- Edited by BrianEhMVP, Moderator Tuesday, April 24, 2012 3:17 PM
Wednesday, April 25, 2012 11:27 AMI have assigned static IP to the machine but this didn't fix it, this issue only occurred when the VM moved from one host to another or when it shuts down. It takes up to 10 mins until I can connect to it through the broker!
Wednesday, April 25, 2012 1:17 PM
Try to check the permission that is assigned to the HOST on the virtual machine
- Marked As Answer by Nader G Thursday, April 26, 2012 12:47 PM