Hi everyone,
Can anyone help me regarding WSUS
1. Where can I download WSUS?
2. How do I install WSUS? and
3. Whats thew best form of practice?
any help would be great
Hi everyone,
Can anyone help me regarding WSUS
1. Where can I download WSUS?
2. How do I install WSUS? and
3. Whats thew best form of practice?
any help would be great
Our LEA provide us with their own WSUS which works like a dream so i might be worth a phone call to see if yours does the same.
DL it from:
http://www.microsoft.com/technet/win...ools/WSUS.mspx
DL and read the Operations Guide - [ all the documentation is on that link ]
I have it syncing up everyday at 03:30am, clients do checking at 12 noon, they will DL the updates and wait till the next day before installing them. They DO NOT automatically reboot - [ a setting in the group policy ]
Forgot to add - ver 3 link:
http://www.microsoft.com/technet/win...0/default.mspx
See attached. This is set in the machine OU.
lionsl2005 (1st February 2011), quietriot1983 (14th January 2011)
Have you made sure that IIS is running and that the WSUS site is started? That was a mistake I made.
go to one of the clients and type wuauclt /resetauthorization /detectnow at the command line. That will force the client to show in WSUS
Ant (14th January 2011)
Thanks, it is synchronising at the minute, so will investigate once it's done, I suspect I'm being stupid and this is because this is the first sync.
Ok, it doesn't seem to matter whether I use the Update Services console or GPO to assign computers to groups, no computers appear in the list...even after hefty amounts of GPupdate-ing.
Am I missing something really obvious?
have a look at the WSUS Client Diagnostics Tool here. might throw some light on the situation.
quietriot1983 (17th January 2011)
Haha, this is brilliant!
I've somehow managed to get one classroom's machines appearing, and one of the ICT Suite machines. But the Suite machine changes as I go round and force gpupdate...!
Do you clone the machines?
pop that into a batch file and run on a computer. see if it makes a difference.rem Fixes problem with client machines not showing up on the server due to imaging method
reg delete HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Win dowsUpdate /v AccountDomainSid /f
reg delete HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Win dowsUpdate /v PingID /f
reg delete HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Win dowsUpdate /v SusClientId /f
cls
@echo Triggering detection after resetting WSUS client identity
net stop wuauserv
net start wuauserv
wuauclt /resetauthorization /detectnow
3s-gtech (18th January 2011)
Yes, try that script, got a few connecting for me last week when I found it. Would there be any mileage putting this as a startup script to make sure all computers are connecting as not sure how to check which PC's are not connecting from all our PC's on the network (other than manually going through a prinrted list).
I ran the batch file on two machines (Ict-09 and ICT-10) and the same thing happened, 10 appeared in the list, and then after running it on 9, 10 disappeared and 9 appeared!

id use newsid and check the suite pcs dont have the same sid as i believe thats how wsus differentiates pcs
Was just going to suggest - NewSID (Windows XP only). That sounds very much like the issue. You'll need to run it on every machine that's been cloned (or sysprep them if you haven't already, but that's another debate).
There are currently 1 users browsing this thread. (0 members and 1 guests)