Event ID - 1015

Event Id	1015
Source	Microsoft-Windows-TerminalServices-SessionBroker-Client
Description	This terminal server cannot participate in TS Session Broker load balancing because the server is configured to use a Microsoft Windows Server 2003-based Session Directory server %1. The Session Directory feature in Windows Server 2003 does not support Terminal Services Session Broker load balancing.
Event Information	According to Microsoft : Cause : This event is logged when the terminal server cannot participate in TS Session Broker load balancing because the server is configured to use a Microsoft Windows Server 2003-based Session Directory server. Resolution : Use a Windows Server 2008-based TS Session Broker server To resolve this issue, configure the terminal server to use a Windows Server 2008-based TS Session Broker server. A Windows Server 2008 terminal server that is configured to use the TS Session Broker Load Balancing feature cannot be configured to use a Windows Server 2003-based Session Directory server, because a Windows Server 2003-based Session Directory server does not support the TS Session Broker Load Balancing feature. If you have an existing Windows Server 2008-based TS Session Broker server in your environment, you can configure the terminal server to use that server. Otherwise, you should consider upgrading the existing Windows Server 2003-based Session Directory server to Windows Server 2008 or not using the TS Session Broker Load Balancing feature. To perform this procedure, you must have membership in the local Administrators group, or you must have been delegated the appropriate authority. To configure the terminal server to use a Windows Server 2008-based TS Session Broker server: On the terminal server, open Terminal Services Configuration. To open Terminal Services Configuration, click Start, point to Administrative Tools, point to Terminal Services, and then click Terminal Services Configuration. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue. Under TS Session Broker, double-click Member of farm in TS Session Broker. On the TS Session Broker tab, under TS Session Broker server name or IP address, enter the computer name or IP address of a Windows Server 2008-based TS Session Broker server. Click OK to close the Properties dialog box. Verify : To verify that the terminal server has successfully joined a farm in TS Session Broker, use either of the following methods: Method one To perform this procedure, you must have membership in the local Administrators group, or you must have been delegated the appropriate authority. On the terminal server, open Event Viewer. To open Event Viewer, click Start, point to Administrative Tools, and then click Event Viewer. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue. In the left pane, expand Windows Logs, and then click System. Look for an event with a Source of TerminalServices-SessionBroker-Client and an Event ID of 1005. This event indicates that the terminal server has successfully joined a farm in TS Session Broker. Method two On the terminal server that has been joined to a farm in TS Session Broker, start a new Terminal Services session by using the IP address of the terminal server. After the session is established, disconnect the session. To connect to a different terminal server that is also a member of the same farm, use the IP address of that terminal server and the same user credentials that you used to connect to the first terminal server. If you are able to reconnect to the existing session on the first terminal server, the terminal server is successfully joined to a farm in TS Session Broker.
Reference Links	Event ID 1015 from Source Microsoft-Windows-TerminalServices-SessionBroker-Client

Catch threats immediately

We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.

See what we caught