Terminal Server high availability – RDS session broker – Server 2008

Things to consider before implementation:

  • You would need to setup Roaming profiles for all TS users. All the local profiles on the current terminal servers would need to be moved to a central network location.
  • All clients that will be connecting to the TS server would need to have RDP version 6.1 or later (Otherwise the client would need to log in twice when they are redirected to another TS server via TS Session Broker – This happens when load balancing kicks in).

You can use the MS technet article for the installation of Session Broker:


Possible problems you might face after implementation:

  • Users keep on being logged in with a temporary profile (This usually only happened on a problematic TS server, not all of them). To resolve this:
    • Delete the registry key that specifies the location of the user’s profile (This will be automatically recreated when the user logs in again).

The location of the registry key: Computer\HKEY_LOCAL_MACHINE\Software\Microsoft\WindowsNT\CurrentVersion\ProfileList



Leave a Reply

Your email address will not be published. Required fields are marked *