A new KB article (KB2844958) was released last week regarding changing IP addresses of RD Session Host servers part of a Windows Server 2012 deployment. Apparently 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.
“…Considering the following scenario:
- You set up a standard deployment of Remote Desktop Services (RDS) in Windows Server 2012. The deployment contains Remote Desktop (RD) Session Host servers, an RD Connection Broker server, and an RD Web Access server.
- You create a session collection that can be accessed by RDS clients through the RD Web Access website.
- The IP addresses of all RD Session Host servers in the session collection are changed.
Your credentials did not work...”
“…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: