Group Policy Not Being Applied

  • Thread starter Thread starter MJC
  • Start date Start date
M

MJC

I built a new Windows 2003 server and our Group Policy is not being applied,
we keep getting the message below....the same policy is working on a Windows
2000 server in the same container.

Event Type: Error
Event Source: Userenv
Event Category: None
Event ID: 1053
Date: 1/13/2006
Time: 4:01:52 PM
User: NT AUTHORITY\SYSTEM
Computer: MFR-RMHI-JRNY
Description:
Windows cannot determine the user or computer name. (The specified domain
either does not exist or could not be contacted. ). Group Policy processing
aborted.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
 
Paul, thank you for answering, perhaps you can tell me if the following
scenerio is working by design:
We have the user's login script stored in a group policy applied to the OU
where the user account resides.

- LOGIN-SCRIPT > MCartier, users, wbny, NY, rphi, com



We have another policy that is applied to the OU where the terminal server
resides. The policy has settings within the user configuration such as
"hiding the C drive" and "Hiding the Network Places Icons".

- TERMINAL-SERVER-LOCKDOWN > MFR-RMHI-JRNY, Terminal Servers, Applications,
rphi, com



When I login to the Server (MFR-RMHI-JRNY) as MCartier, I get my drive
mappings via the "LOGIN-SCRIPT" policy...but the user settings in the
"TERMINAL-SERVER-LOCKDOWN" policy are not applied. Only after I enabled the
"User Group Policy Loopback Processing Mode" with the "Merge" feature does
both settings get applied. Is this working by design??
 
Yes, you are trying to apply a user policy that is defined where the TS
machine is. The only way you can get the user portion of a gpo to be
applied is to have the user in that gpo or inherit from a parent ou's gpo.

--


Paul Bergson MCT, MCSE, MCSA, CNE, CNA, CCA

This posting is provided "AS IS" with no warranties, and confers no rights.
 
Back
Top