Unable to logon locally error

[bazagee]

Hello all,
I'm a newbie to GP mostly and I'll prove that in a minute. First the problem; After applying a GPO to update machines for the new N. American DST, I had some users getting above error.

Interestingly this was only a problem with machines that had not been rebooted. So a user would log off the past logged on user and get this error. It seems that all other machines in the same OU that where shutdown over night did not have an issue.

So I'm just interested in the rule that caused this problem and how to get around it in the future.


The steps I took:
Most all of your machines are in the default Computers OU. We have a domain policy applied at the root level. I had an OU off the root for sometime containing our DC's. I thought in order to keep machines 'findable' I'd create another two OUs under the DC's putting servers in one and workstations in the other. I blocked Inheritance since I didn't want a policy applied to the DC's filtered down. I applied the Domain GPO to the Workstations OU and the new DST2007Update policy.

When informed of the problem I moved the Workstation OU into the root and removed the inheritance block along with the link to the domain GPO (because it should now get it as a child). This however didn't fix the problem.

Moving machines with the logon problem back into the default "computer" OU solved the issue.

So what basic education am I missing here?

Great Forum - glad to have found it!

Barry

[bazagee]

Ok since there are no replies thus far I can assume my methodology isn't to far off left base?

For the sake of other readers of this post, I re-added my trouble-some workstations back into the workstations OU and at the next reboot / logon they recieved the update scripts as required. Without error this time.

I guess I'll have to put it down to "one of those things". Still would still be nice to know 'why' as it cost me a 5:30am wakeup call. :x