> Kevin Lee wrote:
> But we manually set the WSUS and the schedule on each server when we first
> launch WSUS. So, there is no domain GP set for all servers.
I must ask... WHY!? Why do you not make use of Group Policy to configure
> In this case, do you think registry should work on servers? or I need to
> modify the local policy?
Actually, you need to use GROUP POLICY.
But if you insist on not doing so, then your next *best* option is LOCAL
Never modify the registry directly when not required -- and it's not
required for WSUS -- and *especially* not on a production server!!!
And, let's keep your original question and its answer here as well. Your
general misunderstanding of how policy works flavors tremendously your
apparent decision to not use Group Policy. Note here that I'm not the first
person to tell you that you should be using Group Policy!
>>> We have installed a new WSUS server in replace of the old one. After we
>>> have change the registry entry for WUServer record, we found the setting
>>> on local GP is not reflecting the changes.
>> GPEdit.msc does not give you a new on the local registry. It is actually
>> a view on a file that gets incorporated into the registry on
>> of the machine.
>> The correct way to change the WSUS server's IP/name would
>> be doing that with Group Policy/AD-Group Policy as that is the central
>> place you'd do that. Modifications of the local registry get overwritten
>> by Group Policy.
>> Microsoft MVP - Group Policy
>>> Is this normal behavior? or the proper way is to change the new server
>>> via GP not registry?\
And to repeat everybody's point, since you did ask....
The *correct* way to change the server is using Group Policy.
Lawrence Garvin, M.S., MCITP:EA, MCDBA
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009)
MS WSUS Website: http://www.microsoft.com/wsus
My Websites: http://www.onsitechsolutions.com;
My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin