Article ID: 2844958 - View products that this article applies to.
Important This article contains information about how to modify the registry. Make sure that you back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/322756/ )How to back up and restore the registry in Windows
Considering the following scenario:
Your credentials did not work.
This problem occurs because of an obsolete registry entry in the following subkey:
The SessionDirectoryRedirectionIP registry entry stores the IP address of an RD Session Host server that was assigned when the RDS deployment was created. Although the IP address of the RD Session Host server is changed, the IP address in the RD Connection Broker setting is not updated. Therefore, RDS clients cannot connect to the session collection.
Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall the operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.
To resolve this problem, delete the SessionDirectoryRedirectionIP registry entry of the following registry subkey from each RD Session Host server in the session collection:
Alternatively, you can run the following PowerShell script. This script deletes the registry entry from every RD Session Host server in the deployment.