When you install a Terminal Server Session Broker service on
a Windows Server 2008-based computer that is running Cluster Service, the
Session Broker service does not start.
↑ Back to the top
The issue occurs because of an un-initialized variable in
the Tssdis.exe process.
↑ Back to the top
If you install Session Broker on a host computer that is
part of a Windows cluster, you should also configure the service as a cluster
resource. This issue will be fixed in Windows Server 2008 Release 2.
↑ Back to the top
Microsoft
has confirmed that this is a problem in the Microsoft products that are listed
in the "Applies to" section of this article.
↑ Back to the top