A few WSUS questions..

bledd

bledd

bledd

Don
Joined
21 Oct 2002
Posts
46,786
Location
Parts Unknown
I work in a small company that doesn't have a domain, there are 8 XP Sp3 machines, a few 2003 servers, a vista machine and two windows 7 machines

We have one central file server (which also serves nod32 updates via http to the other machines)

Can I simply install WSUS on this server, and then run some sort of tool to configure the machines to look for the WSUS for their updates, and in the event they can't find it (ie a laptop removed from the office), then they'll revert to normal windows update.

Do I need to pick and choose which updates WSUS is to download?

I've never used it before, and want something to fiddle with :)

Thanks in advance
 
Yes, you can use WSUS in a workgroup, but you will need to configure each machine to use the WSUS server. More information on how to do this can be found here.

WSUS itself is quite straightfoward to set up, but ensure you have enough space on the drive you want to store the updates before you begin. It's not impossible to move the updates later, but it's tedious. Once you've installed the server, you will be asked which updates you want to download, and it allows you to select the languages, products and classifications (i.e. critical, security, service patch etc) you want to synchronise.
 
Last edited:
If you configure the machines to use your WSUS server, I dont think you can make them goto Windows Update again if they cant find it automatically, you have to make sure they all can find it...
 
Lanz said:
If you configure the machines to use your WSUS server, I dont think you can make them goto Windows Update again if they cant find it automatically, you have to make sure they all can find it...
Click to expand...

Of course you can, you just take out the registry information that points the machine to the local WSUS.

Code: 
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\windows\WindowsUpdate]
"WUServer"="http://LOCAL.WSUS.SERVER:8530"
"WUStatusServer"="http://LOCAL.WSUS.SERVER:8530"
"ElevateNonAdmins"=dword:00000001

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\windows\WindowsUpdate\AU]
"NoAutoUpdate"=dword:00000000
"AUOptions"=dword:00000004
"ScheduledInstallDay"=dword:00000000
"ScheduledInstallTime"=dword:00000007
"UseWUServer"=dword:00000001
"NoAutoRebootWithLoggedOnUsers"=dword:00000001
"DetectionFrequencyEnabled"=dword:00000001
"DetectionFrequency"=dword:00000016
"AutoInstallMinorUpdates"=dword:00000001
"RebootRelaunchTimeoutEnabled"=dword:00000000
"IncludeRecommendedUpdates"=dword:00000001
 
Ok, so it's locked to either WSUS or Windows update (pending registry changes)

I'll leave the laptop do it's own thing and get all the XP machines at least on the WSUS
 
bledd. said:
Ok, so it's locked to either WSUS or Windows update (pending registry changes)

I'll leave the laptop do it's own thing and get all the XP machines at least on the WSUS
Click to expand...

Probably the best thing mate, just make sure the user doesn't get the choice of updates and make sure when it's back in the office you give it the once over :)
 
Just about to install WSUS on a new server now actually, its in formatting process. Going to have OS and backup DC on primary C: and WSUS and updates on D: Both are 160gb drives to enough storage (me or my boss couldnt find the raid drivers or the server and it was a right ball ache last time getting raid to work, an hp engineer came out then didnt know so had to ring tech support!)

The WSUS deployment and operation guides are pretty straightforward...cue monday me asking how to fix something!
 
typically what sort of size hard drive should I set aside for this? (I guess it grows and grows..)
 
According to WSUS Wiki

Server Disk Space Requirements

WUS Server disk space requirements fall into three categories: the WUS service, WUS updates and the WUS data base.

Microsoft recommend that you have at leaast 6GB free disk space to store WUS content. At present, typical usage is around 1-2GB/language, although this does depend on what updates you specify and is likely to grow over time.

The WSUS service installs (by default) into C:\Program Files\Update Services\. This folder takes up 365MB (371MB on disk) after the initial installation.

The WSUS Database is managed by MDSE, and is installed by default into C:\WSUS\MSSQL$WSUS. This folder takes up 216 MB after the initial install, synchronise and with only 2 clients. The size of the DB grows as you add more computers, and as you manage more updates.
Click to expand...

So not terribly much at all. :)
 
I have selected Critial Updates, Definition Updates, Security Updates and Service Packs as the classifications to synchronise, for Exchange 2k7, ISA 2k6, Office 2k7, Silverlight, SQL 2k8, SCVMM 2k8, SCCM 2k7, Windows Live, Windows 7, Defender, IE 7, IE8, Server 2k3, Server 2k8 R2, Server 2k8 Server Manager, Server 2k8, Windows Server Manager, Windows Ultimate Extras, Windows Vista Dynamic Installer, Windows Vista Ultimate Language Packs, Windows Vista, Windows XP x64 Edition and Windows XP - a pretty typical selection, I would imagine. My WSUSDB folder is 1.7GB and my WSUS folder is 42.1GB.
 
PAz said:
Is anyone else currently using SCCM for Windows Updates?
Ev0 said:
Yes
Click to expand...
Click to expand...


Does the automatic updates service need to be enabled on machines for this? Reason I ask is we get complaints that wuauclt.exe and the associated svchost causes the machine to slow down. We do run SCCM but we don't use it for updates. Just wondering if the SCCM method uses it's native software deployment method as opposed to the wuauclt method?
 
You must log in or register to reply here.
Back
Top Bottom