Forum Discussion
mgy333
10 years agoContributor
Hi Simon,
The problem in our case is that everything is automated, so there is no chance to login to a headless machine, whether it is from RDP or VNC. I am looking for a way to maybe open a virtual gui session automatically, maybe? I am thinking about trying to call VNC in loopback, but that's not very elegant solution even if it works.
There is a way to use RDP for automation. It doesn't work in my case, but maybe you'll find this useful.
Creat a batch file with the following lines:
tscon.esxe 0 /dest:console
tscon.esxe 1 /dest:console
tscon.esxe 2 /dest:console
tscon.esxe 3 /dest:console
When closing RDP connection from the host, don't just close it, but to call the batch file (you can keep the shortcut close by). The gui automated test keeps running even when you close RDP window.
The problem in our case is that everything is automated, so there is no chance to login to a headless machine, whether it is from RDP or VNC. I am looking for a way to maybe open a virtual gui session automatically, maybe? I am thinking about trying to call VNC in loopback, but that's not very elegant solution even if it works.
There is a way to use RDP for automation. It doesn't work in my case, but maybe you'll find this useful.
Creat a batch file with the following lines:
tscon.esxe 0 /dest:console
tscon.esxe 1 /dest:console
tscon.esxe 2 /dest:console
tscon.esxe 3 /dest:console
When closing RDP connection from the host, don't just close it, but to call the batch file (you can keep the shortcut close by). The gui automated test keeps running even when you close RDP window.