Question Locked

Is it possible to use WSUS 3.0 on a peer-to-peer network?

0 helpful
10 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I am currently running a peer-to-peer network with 9 nodes. The OS's are Windows 7 Home Premium x64, Windows XP Professional SP3 x86 and Windows Server 2003 Enterprise SP2 x86. All computers are currently receiving ongoing updates directly from Microsoft Update at present. Can I introduce a WSUS server into the topology or will I need to build a DC-based network?

10 replies

by john.jentzema

Thanks OH smeg. As I have never editted the registry before,I am wondering if:
- Do the " marks need to be removed from the lines of text?
- Do the 2 line breaks in the body of the text need to be removed?
- Can this file be run on Windows XP, Server 2003 and Windows 7 based computers?

At the moment no machines are running in a domain. All PCs are simply connected to the peer-to-peer network.

by churdoo

You can certainly deploy a WSUS 3 server in your scenario as WSUS clients to not need to be part of a same domain or even part of any domain.

The only difference between non-domain clients and domain clients is that in a domain, you can centrally configure clients of the WSUS server via GPO. In a peer environment you need to manipulate the local group policy or registry of each client.

by john.jentzema

I have looked at the text file that Oh smeg pointed me to and I want to know if it is safe to run on all of my computers, being a mix of XP, Server 2003 and Windows 7? I am also a little hesitant to run it since I'm not sure if it is a correctly written script. Do I need to remove the " marks, the two blank line? Is there anything missing from the script?

by 93961

It should be a .REG file not .TXT file. Run that by double clicking it after modifying your WSUS Server Settings in the file.

by john.jentzema

Hi MehuiBhai. Can you please let me know if the following text is now correct? My WSUS server is "Server-WSUS". Do I need to include the names of all of the workstations in place of the word "workstations"? If so, how should the workstation names be separated or should just the workstation that the ".reg" file is going to be run on be there? Here is the text for the file:
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate]
"WUServer"="Server-WSUS"
"WUStatusServer"="Server-WSUS"
"ElevateNonAdmins"=dword:00000001
"TargetGroupEnabled"=dword:00000001
"TargetGroup"="Workstations"

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU]
"NoAUShutdownOption"=dword:00000000
"AutoInstallMinorUpdates"=dword:00000001
"NoAUAsDefaultShutdownOption"=dword:00000001
"NoAutoRebootWithLoggedOnUsers"=dword:00000001
"RescheduleWaitTimeEnabled"=dword:00000001
"RescheduleWaitTime"=dword:00000001
"UseWUServer"=dword:00000001
"NoAutoUpdate"=dword:00000000
"AUOptions"=dword:00000004
"ScheduledInstallDay"=dword:00000000
"ScheduledInstallTime"=dword:00000010
"DetectionFrequencyEnabled"=dword:00000001
"DetectionFrequency"=dword:00000016
"RebootWarningTimeoutEnabled"=dword:00000001
"RebootWarningTimeout"=dword:00000005
"RebootRelaunchTimeoutEnabled"=dword:00000001
"RebootRelaunchTimeout"=dword:0000000a

by tobif

If the internal DNS will resolve "Server-WSUS" to the address of your WSUS server, then this should work.
(If you're not sure about what DNS settings the computers have, then you could try to simply insert the IP address of your server.)

So, paste this text into a text file, which you name "WSUS-Proxy.reg" and then you need to run this file on each machine (with admin rights)

Beware, though: After you do this change, the computers may fail getting updates the normal way, should they happen to be outside of your network!

by seanferd

No, don't change "Workstations".

Run this file on each workstation.

This discussion is closed to new replies.