Surgient Success

We recently experienced a power incident that briefly took down my ESX hosts and VQMS server. Although I was able to recover most of the virtual machines, I am unable to access them using the console. RDP access works without problem. I assume that the unique URL to the VMs changed during the server reboots (please correct me if I'm wrong). Is there any way to have VQMS get new URLs for these VMs or is there a manual process I can use to provide them? While most users will probably be happy with RDP access, one or two absolutely need console access.

Thanks

Console URLs do not change during the deployment session even if the servers are rebooted.  Are you trying to reuse a bookmarked URL or are you clicking the Console link in the Surgient web app?  What is the error you're receiving?  Is the VM console accessible via the VI3 Client or VMware Web UI?

I am clicking the Console link in the Surgient Web App. When I try it spins for a while and comes back with the error "Unable to connect to remote server." A look at the console.log file on the VQMS server indicates that it is timing out. Newly deployed VMs work fine.

 I can access the VMs via the VC client and through the VMware Web UI. It is only failing when I use the Console link from within the Surgient Web App.

While you are waiting for the Console to connect, if you click on the spinner graphic, a log file will pop up with more details.  You should review that for more details on the problem.  You can contact Surgient support with that log but review it for sensitive information as temporary passwords may be logged in there.