Event ID - 1001

Event Id1001
SourceMicrosoft-Windows-TerminalServices-SessionBroker-Client
DescriptionThe remote procedure call (RPC) to join TS Session Broker to %1 failed.The following error occurred: Access Denied.
Event InformationAccording to Microsoft :
Cause :
This event is logged when the remote procedure failed to join .
Resolution :
Add the terminal server to the Session Directory Computers group and try to join TS Session Broker again
To resolve this issue, do the following:
1.Add the computer account for the terminal server to the Session Directory Computers local group on the TS Session Broker server.
2.Try to join the terminal server to a farm in TS Session Broker again.To perform these tasks, refer to the following sections.
Add the computer account for the terminal server to the Session Directory Computers local group on the TS Session Broker server
To perform this procedure, you must have membership in the local Administrators group, or you must have been delegated the appropriate authority.
To add the computer account to the Session Directory Computers group:
1.On the TS Session Broker server, open the Local Users and Groups snap-in. To open Local Users and Groups, click Start, click Run, type lusrmgr.msc, and then click OK.
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, click Groups.
4.In the right pane, right-click the Session Directory Computers group, and then click Properties.
5.Click Add.
6.In the Select Users, Computers, or Groups dialog box, click Object Types.
7.Select the Computers check box, and then click OK.
8.Locate and then add the computer account for the terminal server.
9.Click OK to close the Select Users, Computers, or Groups dialog box, and then click OK to close the Session Directory Computers Properties dialog box.
Try to join the terminal server to a farm in TS Session Broker again
To perform this procedure, you must have membership in the local Administrators group, or you must have been delegated the appropriate authority.
To join the terminal server to a farm in TS Session Broker:
1.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.
2. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
3.Under TS Session Broker, double-click Member of farm in TS Session Broker.
4.On the TS Session Broker tab, do the following:
a)Under TS Session Broker server name or IP address, enter the computer name or IP address of the TS Session Broker server.
b)Under Farm name in TS Session Broker, enter the name of the farm to join.
5.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 Name:
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 ControlM 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 LinksEvent ID 1001 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

Did this information help you to resolve the problem?

Yes: My problem was resolved.
No: The information was not helpful / Partially helpful.