This behavior occurs even though the load of other terminal servers on the network is low. Additionally, after this problem occurs, events that resemble the following are logged in the session broker log Tssdis. A pending redirection occurs when a new user logs on to the farm of terminal servers, and TS Session Broker points the user to a particular terminal server before the logon process has finished. The session directory tracks the number of pending redirections for each terminal server, and then it increases the count when the TS Session Broker determines the target server.
Additionally, the session directory decreases the count after the logon process is complete. However, the TS Session Broker service incorrectly increases the count of pending redirections for disconnected terminal sessions, and it never decreases the count. Therefore, when the pending redirection count on a terminal server reaches its limit 16, by default , the TS Session Broker service no longer redirects new terminal sessions to this terminal server.
Eventually, the number of available servers decreases to a small set or to only a single server. A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing.
Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix. If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix. Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request.
The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:.
Would loopback processing work? According to your description, you have defined the following group policy:. Interactive logon: Message title for users attempting to log on.
Interactive logon: Message text for users attempting to log on. As they are computer specific settings, no need to use loopback. How did you link the GPO? If you want to disable the messages from appearing on terminal servers, why not moving the terminal servers out of the OU where the GPO is linked to and create a new OU for these terminal servers?
You can also use security filter. For more information, please refer to the following link:. Office Office Exchange Server. Not an IT pro? Active 9 years, 10 months ago. Viewed 3k times. What should I do? Improve this question.
Rob Moir Add a comment. Active Oldest Votes. By default, normal users cannot log in interactively to a Windows Server, so one of at least 2 things must have happened 1 They know an admin password and logged in with that, or someone made their accounts admins, etc. Improve this answer. Rob Moir Rob Moir Sign up or log in Sign up using Google. Sign up using Facebook. Sign up using Email and Password.
0コメント