Terminal Server uses a License Server to issue a Terminal
Services client license when you create a Remote Assistance request. Terminal
Server requests an X509 certificate from the License Server and uses it with
the Microsoft Remote Desktop Protocol (RDP) to encrypt communication between
Terminal Server and the Terminal Server client.
If a server running
Terminal Server Licensing is unavailable, Terminal Server uses a less secure
method. This method uses a public key to create a Remote Assistance request.
Terminal Server continues to try to register with a server running Terminal
Server Licensing until such a server is contacted.
When Terminal
Server contacts a server running Terminal Server Licensing, all existing Remote
Assistance requests that were created by using the public key become invalid.
Therefore, when you try to use the Remote Assistance request that was created
before Terminal Server has contacted the License Server, you may receive the
"Remote Assistance failed" error message.
For example, this issue may
occur in the following scenario:
- You switch from Remote Administration mode to Terminal
Server mode and then restart the computer.
- You create a Remote Assistance request before the computer
has identified a server running Terminal Server Licensing. Terminal Server
issues the Remote Assistance request by using the less secure method (the
public key instead of the X509 certificate).
- Terminal Server finds a License Server, and any subsequent
Remote Assistance requests are created with the X509 certificate.
- The assistant tries to use the Remote Assistance request
(that was created without the X509 certificate) to connect to Terminal
Server.
- The assistant receives the �Remote Assistance failed� error
message, because the Remote Assistance request that was created with the public
key is invalid.