"Remote Assistance Failed "Error Message After You Switch to Terminal Server Mode
SYMPTOMSWhen you switch from Remote Administration mode to Terminal
Server mode, you may not be able to use the Remote Assistance feature. When you
use a Remote Assistance request to invite someone to help you, the assistant
may not be able to connect to your computer. Then, the assistant receives the
following error message: Remote Assistance failed
CAUSE This issue may occur in the following scenario:
RESOLUTION To resolve the issue, restart the Terminal Server, and then
re-create the Remote Assistance request. STATUS
Microsoft has confirmed that this is a bug in the Microsoft products that are
listed at the beginning of this article.
MORE INFORMATION 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:
APPLIES TO
| Article Translations
|
Back to the top
