Quantcast
Channel: Remote Desktop Services (Terminal Services) Forum
Viewing all articles
Browse latest Browse all 27656

Event ID 4105 - Need to fix corrupted DACLs

$
0
0

I'm receiving event id: 4105 on my RDS license server event logs.  I've determined that I have a corrupted DACLS because I have reviewed the following articles:

http://support.microsoft.com/kb/2030310

http://itinternals.blogspot.com/2012/01/resovling-event-id-4105-terminal.html

Basically if I follow these directions:

Make sure, the domain group "Terminal Server License Servers" has the following permissions to the active directories users:
- Open Active Directory Users And Computers
- Tick View -> Advanced
- Right click on the root of your domain and select properties.
- Select the Security tab.
- Check if "Terminal Server License Servers" is listed with special permissions. If not, click on "Advanced" and add the domain group "Terminal Server License Servers", select "Applies onto" "User objects", then tick the permissions "Read Terminal Server License Servers" and "Write Terminal Server License Servers".

I don't see "Read Terminal Server" or "Write Terminal Server"

The solution suggested in the MS article states the following resolution:

Windows Server 2003 level Schema

dsacls "CN=XXXX,OU=XXXX,OU=XXXX,OU=XXXX,DC=XXXX,DC=XXXX,DC=XXX" /G
"BUILTIN\Terminal Server License Servers:WPRP;terminalServer"

When you grant the permissions on a container, you should use the following command:
dsacls "OU=XXXX,DC=XXXX,DC=XXXX,DC=XXX" /I:S /G 
"BUILTIN\Terminal Server License Servers:WPRP;terminalServer;user"

 

My question is, am I really typing XXXX or do I need to determine what my CN, OU, DC are?  It's not clear what I should be typing to replace the X's if that I what I should be doing.  Can anyone help?

 



Viewing all articles
Browse latest Browse all 27656

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>