Having a TeamViewer unattended host on a server is a million times better than remote desktop in many situations. First off screen resolution by default isn’t an issue. Secondly you can also let someone else see what is going on with the physical server. Today I came across an interesting thing. We had remote access to a server through RDP so we installed TeamViewer (Version 10). With that logged in RDP account. Everything was great and the ID for this account was quickly added into our list of servers that we manage. Then we logged off of Remote Desktop. When this happened we noticed a strange thing, the remote desktop killed the TeamViewer. After a few hours of searching the Internet to no avail and trying over a dozen things we tried locking the screen with the remote desktop. When we did we got the following error with a black screen:
“The screen cannot be captured at the moment. This is probably due to fast user switching or a disconnected/minimized remote desktop session”. That is a great bit of information but gives no solution on how to fix the problem. I thought the service must not be starting with the session so I will try a remote reboot to see if we can force the service. This is when I stumbled on the answer to the problem.
The Remote Desktop Session through RDP has a different TeamViewer ID than the standard service running. When you tell the server to remote reboot it gives you the prompt that “Multi User View Mode is enabled” and that logging on again will require you to log in with the new ID XXX XXX XXX. To connect to the correct ID note it down and then cancel the remote reboot. Once that is finished you can log out of the RDP and then log in with the new TeamViewer ID. This will be your permanent ID outside of the RDP Scope.
I hope this saves someone a few hours of time.