|
Ok, I don’t know how this could have happened, but it just seemed to. We suddenly could not log in locally to many of our servers, we kept getting a local policy didn’t allow access to Log on Locally. Luckily I had a connection open to one of the servers we couldn’t log into and I quickly looked at the Local Security Policy and it listed one of our users as the only one that could log in locally as the Effective Policy Setting. I quickly looked at the GPOs that were attached to the OU the machines were in (this was affecting around 10 servers) and there were no GPOs applied to it (or higher up the tree, except the Default Domain Policy which was clean.) I did a secedit /refreshpolicy on the box and it fixed the problem, suddenly we could log in. I’ve been pouring through the log files and I can’t see any changes to the local security policy, nor is there anything listed on the DCs where someone had added a GPO to the servers OU (then deleted it). Nobody who could have changed it claims to have made any changes to the OU. Basically I’m looking to find out, and I feel foolish even asking this, but has anyone heard of local policies changing like that on its own? Could it have been some kind of strange Active Directory database corruption that then fixed itself?
Brad Martin Go Daddy Software, Inc. 480.505.8800 ext. 250
|
<<image001.gif>>
