WSUS and Windows 7 SP1?

neil_g

neil_g

neil_g

Soldato
Joined
9 Dec 2007
Posts
10,492
Location
Hants
has anyone had any sucess rolling out W7 SP1 from WSUS?

trialled a couple of machines and so far its failed with a "timeout" error one one and its given a fatal error on the other (see this MS article
 
Sorry to say this dude but WSUS is absolutely rubbish for enterprise use!

We've got it at the moment - and use our Landesk management software instead to rollout patches and things like SP1 and IE8.

thats my next project - Microsoft System Centre instead :(
 
the thing is the file gets pushed out to the client machine okay, it appears in the softwaredistribution folder.. thats why its really confusing because then there is no network traffic to timeout.
 
In the grand scheme of things (1,000's of pc's) its not ideal - something to do with its ip address based i think. Doesnt link in very well with AD either.

It also has crap reporting - What microsoft deems to be 100% up to date is not neccessarily what we as IT administrators would deem to be 100% (look into it - if all patches aren't applied it doesnt report back 100% completion - bearing in mind we as IT administrators will not want to roll out certain patches).

I'm going to be looking into it more this week when my SCCM project kicks off (just been leaving my colleague to struggle with WSUS lol!) ;)
 
OK here goes the list my colleague gave me:

A)- It sux (IGNORE lol)
B)- Poor Reporting (basically what I alluded to on my previous post)
C)- not AD aware
D)- No scheduling facility.

As its not AD aware the only way to group computers together is by geographical location (i.e. IP subnets) which is really quite poor!

But then again - what can we expect for free? ;)
 
zoomee said:
OK here goes the list my colleague gave me:

A)- It sux (IGNORE lol)
B)- Poor Reporting (basically what I alluded to on my previous post)
C)- not AD aware
D)- No scheduling facility.

As its not AD aware the only way to group computers together is by geographical location (i.e. IP subnets) which is really quite poor!

But then again - what can we expect for free? ;)
Click to expand...

A) Ignored :p
B) I disagree, I find the reporting to be rather good. It's completely customisable so you can have it report say only failed updates on a particular server, or all required updates on a number of servers. It also does a nice export to pdf which is great for keeping management happy.
C) In what way? Whilst not integrated into AD, it's completely customisable and controllable through Group Policy (Computer Config/Policies/Admin Templates/Windows Components/Windows Update)
D) You can schedule installations via Group Policy with no issues :confused: The particular setting is called 'Configure Automatic Updates' in the above mentioned area of the GPO

Also, computers can be grouped however you like, again through Group Policy. You could have a different group for each OS, or a Dev and a Prod group, or any other setup you'd like. Again in the Windows Update section of the GPO, the setting is called 'Enable client-side targeting'.

It sounds like the only problems you guys have with WSUS is that you don't know how to use it :p

neil_g said:
so no one else has seen this issue then..?
Click to expand...

Unfortunately not, sorry. We're still on XP in the office :o
 
neil_g said:
so no one else has seen this issue then..?
Click to expand...

One day last week I had an early morning phone call from an accountants I do some occasional support for. They have WSUS running as a part of SBS 2008, and because of how WSUS was configured it had authorised SP1 for all of their PCs.

They had to leave their PCs running overnight because SP1 started to install itself when they tried to shutdown at the end of the day. The next morning they had 10 out of 12 PCs stopped with the same fatal error.
 
Yup, we've had a customer with a couple of Sony laptops get goosed by SP1 :rolleyes:

Cue a quick scrabble to change WSUS on SBS 2008 which is set to auto-approve SPs.
 
I've not had huge issues with WSUS. Though it doesn't push IE8 well due to issues with the accelerators needing choosing etc on first run which it's proving a real turd to predefine.
But sometimes I do find it easier to use our software delivery solution to push out major updates like service packs and IE installs. Purely because we can kick off a custom script and do more cleverness with the install packages.
 
Trojan said:
A) Ignored :p
B) I disagree, I find the reporting to be rather good. It's completely customisable so you can have it report say only failed updates on a particular server, or all required updates on a number of servers. It also does a nice export to pdf which is great for keeping management happy.
C) In what way? Whilst not integrated into AD, it's completely customisable and controllable through Group Policy (Computer Config/Policies/Admin Templates/Windows Components/Windows Update)
D) You can schedule installations via Group Policy with no issues :confused: The particular setting is called 'Configure Automatic Updates' in the above mentioned area of the GPO

Also, computers can be grouped however you like, again through Group Policy. You could have a different group for each OS, or a Dev and a Prod group, or any other setup you'd like. Again in the Windows Update section of the GPO, the setting is called 'Enable client-side targeting'.

It sounds like the only problems you guys have with WSUS is that you don't know how to use it :p



Unfortunately not, sorry. We're still on XP in the office :o
Click to expand...

Thanks dude - I'll look into myself this time instead of relying on a numpty :rolleyes:

I don't think there was any problems with deploying it for servers, the problem was for PC's of which I have approx 7,000+ to look after :(
 
You must log in or register to reply here.
Back
Top Bottom