Re: Registry settings not changed after policy applied

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: Sarah G. (sguo_at_coopervision.com)
Date: 03/15/04 

Date: Mon, 15 Mar 2004 13:37:14 -0500

So I was looking at wrong path. I've checked the path accordingly under
policies, that is right. Thanks, Sarah
"Derek Melber [MVP]" <derekm@braincore.net> wrote in message
news:OGW0birCEHA.1128@TK2MSFTNGP11.phx.gbl...
> I think this is the correct path... in the ADM that I have:
>
> Software\Policies\Microsoft\Windows\WindowsUpdate\AU
>
> --
> Derek Melber
> BrainCore.Net
> derekm@braincore.net
> "Sarah G." <sguo@coopervision.com> wrote in message
> news:eD5v2erCEHA.2600@TK2MSFTNGP09.phx.gbl...
> > Ok, that could be the problem. let me give you the path that I was
looking
> > into:
> >
> >
>
\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\
> > Auto update
> > "Derek Melber [MVP]" <derekm@braincore.net> wrote in message
> > news:eUfrPWrCEHA.464@TK2MSFTNGP11.phx.gbl...
> > > Sarah,
> > >
> > > The SUS configuration in the interface that is showing the correct
> > > information gets this information from the Registry. So, I think you
are
> > > doing this correct, but maybe you are not looking in the correct
> location
> > in
> > > the Registry. Try cracking open the ADM template that configures this
> and
> > > make sure you are looking at the right Registry path.
> > >
> > > --
> > > Derek Melber
> > > BrainCore.Net
> > > derekm@braincore.net
> > > "Sarah G." <sguo@coopervision.com> wrote in message
> > > news:uO%23tmAqCEHA.1456@TK2MSFTNGP09.phx.gbl...
> > > > I'm doing SUS testing. Installed SUS on a windows 2000 server. Setup
a
> > OU
> > > on
> > > > AD called SUS, created a new GPO applied to this OU only, setup
> windows
> > > > update policy: auto update every day at 2:00am, ........ I added one
> > > windows
> > > > 2000 pro client into this OU. Then I checked client, the auto udpate
> > > > settings are changed by GPO. Then later on, I changed GPO time to
> every
> > > day
> > > > at 3:00am, checked client, auto udpate setting has been changed to
> > 3:00am,
> > > > but this time the registry settings are still old ones at every day
> > > 2:00am.
> > > > Even I reboot this computer a couple of times, it isn't changed. Can
> > > anyone
> > > > tell me the what could be causing this problem?
> > > >
> > > > Thanks,
> > > > Sarah
> > > >
> > > >
> > >
> > >
> >
> >
>
>

Relevant Pages

  • Re: Group polices not getting implemented on XP professional
    ... I have tried the things but still not getting policies on clients, ... Tahnks & Regards ... This setting should be found on the XP machine under the local policy. ... Upgrading Windows 2000 Group Policy for Windows XP ...
    (microsoft.public.win2000.active_directory)
  • Re: Windows XP remember GP when removed from domain
    ... > these policies remain in force and are locked on the local station. ... and disallowing local policy management of their values. ... Microsoft MVP (Windows Server System: ... What you're seeing on the Windows XP SP1 machines is what I'd ...
    (microsoft.public.windows.group_policy)
  • Re: applying polices additional languages support in GPO
    ... How can I do English names (in policies) acceptable by other language clients. ... I have multilanguage version of Win XP and the same situation is then I set Polish language as default. ... >>-->Gary Mudgett, MCSE, MCSA>Windows 2000/2003 Directory Services> ...
    (microsoft.public.win2000.group_policy)
  • RE: protect MS Windows 95/98/Me
    ... set restrcitive policies dependent on whatever ADM you use. ... Group Policies from within Windows components. ... There is no security features in win9x OS. ... there is no way of securing these operating systems. ...
    (Security-Basics)
  • Re: Adding XP group policy to W2K
    ... I followed the directions from ... Failed to Open the Group Policy Object. ... > When I attempt to add Group Policy to the MMC from a Windows ... First of all if you want the XP Policies, it is best to do it ...
    (microsoft.public.win2000.group_policy)