Re: Policies having no effect on XP workstation

From: Chriss3 (noSpamHere_at_chrisse.se)
Date: 02/19/04 

Date: Thu, 19 Feb 2004 23:00:32 +0100

If the nothing else is define yes the changes are made at the server holding
the PDC Emulator FSMO.

If you check the GUID of the particular GPO object you can see if a such
policy exist in the SYSVOL share at the local site DC. You can also check
the content of the PDC and see if itīs different than the local DCīs SYSVOL. 

-- 
Regards,
Christoffer Andersson
No email replies please - reply in the newsgroup
If the information was help full, you can let me know at:
http://www.itsystem.se/employers.asp?ID=1
"Derek Melber [MVP]" <derekm@braincore.net> skrev i meddelandet
news:%23tZLbhx9DHA.1632@TK2MSFTNGP12.phx.gbl...
> Maurice,
>
> The convergence time for GPOs can vary dramatically. You need to consider
> replication in the site, and inter-site as well. If you have multiple
sites,
> that are chained together, it can take hours for some clients to see the
> changes. Also, the initial change is made to the PDC emulator DC, so it
> starts here and replicates outward.
>
> -- 
> Derek Melber
>
> "Maurice Reed" <anonymous@discussions.microsoft.com> wrote in message
> news:1350f01c3f707$f4e13ee0$a501280a@phx.gbl...
> > Having investigated further I realised it was the DNS
> > settings on the PC at fault. The PC had been used on our
> > main domain(same IP subnet)and had our main Internet
> > server as its preferred DNS. Once I changed that to point
> > to the W2K3 server the policies started working. Just to
> > prove it I made some changes to the policy settings and
> > they were reflected on to the PC.
> >
> > One thing though, when a change is made on the server to
> > some of the policy settings how long should it be before
> > they come into effect? I found that if I made a change and
> > then logged the PC off and back on again the changes were
> > not in effect. If I logged off and then logged back on
> > sometime later the changes took effect.
> >
> > cheers
> >
> >
> > >-----Original Message-----
> > >Did you setup policies in GPOs that are linked to BOTH of
> > the OUs? remember,
> > >policies apply to users OR computers, depending on which
> > portion of the GPO
> > >you have configured.
> > >
> > >-- 
> > >Derek Melber
> > >
> > >"Maurice Reed" <anonymous@discussions.microsoft.com>
> > wrote in message
> > >news:11e9601c3f63c$07cafcc0$a301280a@phx.gbl...
> > >> Hi, I am soon to upgrade to Server 2003 from NT4 on a
> > LAN
> > >> that needs restricted desktops.
> > >>
> > >> I have downloaded and installed GPMC and also downloaded
> > >> the CommonScenarios from MS too. I have taken an XP
> > >> workstation and added it to the test domain and got the
> > >> usual 'welome to xyz domain' message. On the server I
> > >> opened up AD Users & Computers and could see the
> > computer
> > >> in the computers folder so moved it to:- Common
> > Scenarios-
> > >> >Computers->Highly managed->Taskstation.
> > >>
> > >> I then created a test user in the Common Scenarios-
> > >Users-
> > >> >Highly managed->Taskstation Container.
> > >>
> > >> I enabled the policies and then logged in as the test
> > user
> > >> on the test PC and the policies have NO effect
> > whatsoever!
> > >>
> > >> Obviously I have missed something but have gone through
> > >> the properties of the user, PC and both policies to
> > >> checked everything looks ok but no joy.
> > >>
> > >> I am getting desparate as next week I will be going live
> > >> with 12 XP workstations on a W2003 server and must get
> > the
> > >> desktops locked down as they will be used by students.
> > >>
> > >> TIA
> > >
> > >
> > >.
> > >
>
>

Relevant Pages

  • RE: Computer Policy Not applied
    ... Have you run RSoP from the server side to validate the ... asynchronous application of the GPO is failing. ... > I cannot seem to get computer policy to work through our group policies. ...
    (microsoft.public.windows.server.active_directory)
  • Re: TS and Non TS working
    ... Administrator Accounts and Selected Users in Windows Server 2003 ... MCSE, CCEA, Microsoft MVP - Terminal Server ... policies are still applying - is there any way around this ... Link the restrictive GPO to the OU which contains the TS ...
    (microsoft.public.windows.terminal_services)
  • Re: Accessing Windows 2000 Server Remote Registry
    ... On the inaccessible W2K Member Server, ... Also all of the Secure Channel policies are disabled both locally ... and via GPO. ... > Take a look at a couple settings first on the inaccessible W2k: ...
    (microsoft.public.win2000.security)
  • Re: AD Cant restrict access to server
    ... I then ran gpupdate on the server that the policies were ... > if you wish to include a script sample in your post please add "Use of the ... I created a new GPO, put it at the top of the order. ...
    (microsoft.public.windows.server.active_directory)
  • Re: AD issues
    ... The domain controller will also act as DNS server i assume, so make sure that all domain machines uses this one as the DNS server on the NIC, not other external DNS servers. ... You should not change the default domain policy and the default domain controller policy, leave them as they are so in case of problems you can always revert back to the starting policies. ...
    (microsoft.public.windows.server.active_directory)