| Event Id | 1013 |
| Source | Microsoft-Windows-TerminalServices-SessionBroker-Client |
| Description | The server failed to retrieve the local computer name. Win32 error code: %1 |
| Event Information | According to Microsoft : Cause : This event is logged when the server failed to retrieve the local computer name. Resolution : Shorten the computer name for the terminal server To resolve this issue, shorten the computer name for the terminal server so that the computer name is 15 characters or less. Changing the name of the computer will require the computer to be restarted. Note: The character limit for the computer name is a limitation imposed by operations that are dependent on using NetBIOS names. To perform this procedure, you must have membership in the local Administrators group, or you must have been delegated the appropriate authority. To change the computer name for the terminal server: 1.On the terminal server, click Start, click Run, type control system, and then click OK. 2.Under Computer name, domain, and workgroup settings, click Change settings. 3.If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue. 4.Click Change. 5.In Computer name, type the new name for the computer, and then click OK. 6.Click OK, click Close, and then click Restart Now. 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. 1.On the terminal server, open Event Viewer. To open Event Viewer, click Start, point to Administrative Tools, and then click Event Viewer. 2.If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue. 3.In the left pane, expand Windows Logs, and then click System. 4.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 1.On the terminal server that has been joined to a farm in TS Session Broker, start a new Terminal Services session. 2.After the session is established, disconnect the session. 3.On a different terminal server, but one that is also a member of the same farm in TS Session Broker, try to reconnect to your existing session. If you are able to reconnect to the existing session, the terminal server is successfully joined to a farm in TS Session Broker. |
| Reference Links | Event ID 1013 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.