DannyBroadhurst Posted November 8, 2013 Posted November 8, 2013 Im starting to get annoyed now our old IT Manager has Left and its now down to me to learn how WSUS works and to get it working again. I thought it was all going well. Untill WSUS seemes to be pushing out every single update to every PC connected to it. This means Windows 7 Updates are going to Windows Servers ETC. This is causing no end of problems on the PC's
sted Posted November 8, 2013 Posted November 8, 2013 you need to create groups and have gpo assign pcs to those groups then alter your automatic approval rules. when it works at all its actually quite a simple bit of software when it breaks move it to another server lol
DannyBroadhurst Posted November 8, 2013 Author Posted November 8, 2013 I have Simple groups Laptops, Desktops, Workstations and Servers. I dont narrow it down by OS Etc. I was hoping it was clever enough to know the PC has Windows 7 so clearly doesnt need the Windows 2008 R2 update..
sted Posted November 8, 2013 Posted November 8, 2013 I have Simple groups Laptops, Desktops, Workstations and Servers. I dont narrow it down by OS Etc. I was hoping it was clever enough to know the PC has Windows 7 so clearly doesnt need the Windows 2008 R2 update.. it shouldnt install updates that arnt for the os the client is running BUT some updates are worded such that it says server 2008r2 / win7 but sometimes depending on screen res etc you dont see that bit or some updates are just badly named
DannyBroadhurst Posted November 8, 2013 Author Posted November 8, 2013 Something isnt right then. Because i have an XP update that is installed on 230+ Machines we only have 250... And i would say about 10 are XP...
AngryTechnician Posted November 8, 2013 Posted November 8, 2013 I was hoping it was clever enough to know the PC has Windows 7 so clearly doesnt need the Windows 2008 R2 update.. Even if you approve a server update to a workstation machine, the workstation itself will recognise it's not applicable and won't install it. If it actually is installing them anyway, something is very seriously wrong.
sted Posted November 8, 2013 Posted November 8, 2013 Something isnt right then. Because i have an XP update that is installed on 230+ Machines we only have 250... And i would say about 10 are XP... when was cleanup last run? it might be an old update on old pcs long gone/rebuilt but wsus still reports it
AngryTechnician Posted November 8, 2013 Posted November 8, 2013 What is the actual status reported by those non-XP machines when you run a status report for that update? Some of the summary views combine Installed & Not Applicable into the same column.
DannyBroadhurst Posted November 8, 2013 Author Posted November 8, 2013 Ill have another look now. I declined all the updates till i could get a grip on what was happening. Also it may be un related but i get Unexpected error and i have to reset the server node quite often.
sted Posted November 8, 2013 Posted November 8, 2013 Ill have another look now. I declined all the updates till i could get a grip on what was happening. Also it may be un related but i get Unexpected error and i have to reset the server node quite often. yes you do it usually means that you need to run cleanup until it stops erroring at a guess you have gbs of updates it can get silly i cleaned one in the alst few dasy that had 170gb of updates now down to <70gb
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now