T
Threep13372
Hello, I am experiencing a strange problem on multiple servers, where when I add the server to a security group in AD, reboot the server, and then do a gpresult /r /scope:computer, the security groups that the computer is a member of do not show up in the list, and group policies which are filtered to these computer groups do not apply. I have resolved this on one server by re-adding the server to the domain, but that is a workaround solution and I would like to figure out why this is happening.
Things I have tried:
1. Removing and re-adding the computer to the groups.
2. Moving the computers object in AD to one OU, and then back to its original location.
3. using psexec to login as the system account and purge the Kerberos TGT.
4. Rebooting the server
The only solution so far has been to re-add it to the domain but this seems fundamentally wrong for something very simple like adding a computer to a security group.
At this point I am at a total loss of what could be happening, if anyone has any suggestions it would be appreciated.
Continue reading...
Things I have tried:
1. Removing and re-adding the computer to the groups.
2. Moving the computers object in AD to one OU, and then back to its original location.
3. using psexec to login as the system account and purge the Kerberos TGT.
4. Rebooting the server
The only solution so far has been to re-add it to the domain but this seems fundamentally wrong for something very simple like adding a computer to a security group.
At this point I am at a total loss of what could be happening, if anyone has any suggestions it would be appreciated.
Continue reading...