Re: Applying User Configuration policies to non-administrators on Win2K3

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Hi Steve,

Thank you very much for your reply. You've come up with some great
things to try and look at. Here are the results.

The RSOP does show exactly the same results as the modeling mode for
that user. It matches the RSOP seen on the XP box as well as the XP
modeling simulation. Group membership is mostly the same on the XP box
and the Terminal Server - the Terminal Server has two extra groups that
are probably just Win2K3 specific and XP is not aware of them:
"TERMINAL SERVER USER", and "This Organization". Running
gpresult on the XP and 2003 boxes do show they are in the identical OU.
It should be noted that running gpresult on the 2003 box as the
regular did not show any computer information - I had to run it as
administrator, but that did not necessarily strike me as odd. What did
strike me as odd, however, was the following:

Last time Group Policy was applied: N/A
Group Policy was applied from: N/A

This is under the "USER SETTINGS" section of the output on the 2003
box. Further down the output, though, under "Resultant Set Of
Policies for User", the setting is indeed there to remove the user
name from the start menu.

Administrative Templates
GPO: Remove name
KeyName:
Software\Microsoft\Windows\CurrentVersion\Policies\Explorer\NoUserNameInStartMenu
Value: 1, 0, 0, 0
State: Enabled

This registry key does not exist under HKCU on the Win2K3 box but is
present under WinXP.

As for the "\windows\system32\group policy" folder, one does not
exist on any machine, regardless of the user/administrator that is
logged in. I'm not sure what you mean by this.

Thank you again for your input. If you or anybody else has any other
ideas, suggestions, or comments, please send them along!

Thanks,
-Troy

.

Relevant Pages

  • RE: Group Policy Results Wizard not working
    ... After I ran RSoP on the client I tried the Group Policy Results Wizard again ... Microsoft Online Newsgroup Support ...
    (microsoft.public.windows.server.sbs)
  • Re: GPO Password length not working
    ... The errors running RSOP in logging mode on the XP Pro computers could be ... Configure some settings for both user and computer ... You mention that you are using Group Policy filtering by using groups other ... >> domain container and that the default domain controller Group Policy is ...
    (microsoft.public.windows.server.security)
  • RE: Group Policy Results Wizard not working
    ... Did you run Group Policy Results Wizard as a domain administrator? ... In the RSoP snap-in, right-click Resultant Set of Policy, and then click ... Microsoft Online Newsgroup Support ...
    (microsoft.public.windows.server.sbs)
  • Re: Domain Users into Local Admins
    ... Was your RSoP error "Invalid Namespace"? ... Server User Assistance - Group Policy ... >> 1) Machine or user must be a domain member and authenticate with the ... Kerberos authentication may not work. ...
    (microsoft.public.windows.server.security)
  • Re: Local Group Policy Filtering: Not Applied (Empty) ?
    ... That message simply means that the local GPO's user settings were not applied because no settings were defined in it. ... Script Group Policy Settings with the GPExpert Scripting Toolkit for PowerShell! ... Default Domain Controllers Policy ... Filtering: Not Applied ...
    (microsoft.public.windows.server.active_directory)