mdrabble Posted June 30, 2016 Posted June 30, 2016 I'm having a bit of an issue why SCCM where I found my WSUS update folder missing as I wondered why updates not being appliedd. No idea how long it had been missing as it not on backups going back 30 day..... I recreated the folder and removed and added the WSUS role and all seemed fine again or so I thought. Rebuild a station and checked for updates and none being applied I've noticed that my OS partition (500GB) has become full so I'm thinking I've not point WSUS to the correct drive... so I've checked and I have. The other puzzling thing is that SCCM content is showing on drive C even though I have the nosms file on the root of drive C: So do I spend time trying to unpick my SCCM or do I reinstall on a new VM using the original SCCM details including Site Code. (and possible restore the database) What do the SCCM gurus think?
sparkeh Posted June 30, 2016 Posted June 30, 2016 I would spend some time trying to fix it. What do the 'Site Status' and 'Component Status' nodes report?
Steve21 Posted June 30, 2016 Posted June 30, 2016 Is this WSUS or SCCM? As you seem to mention both. "Checking for updates" via WU wouldn't show any from SCCM etc. Steve
Jawloms Posted June 30, 2016 Posted June 30, 2016 I'm having a bit of an issue why SCCM where I found my WSUS update folder missing as I wondered why updates not being appliedd. No idea how long it had been missing as it not on backups going back 30 day..... Unlikely I know, but previous versions?
sparkeh Posted June 30, 2016 Posted June 30, 2016 Is this WSUS or SCCM? As you seem to mention both. "Checking for updates" via WU wouldn't show any from SCCM etc. Steve Its is both. SCCM sits on top of WSUS to control updates and clients use WU to get and install updates as directed by SCCM.
Steve21 Posted June 30, 2016 Posted June 30, 2016 (edited) Its is both. SCCM sits on top of WSUS to control updates and clients use WU to get and install updates as directed by SCCM. Nope, SCCM replaces WU as it goes through Config Manager as a piece of software. You can't see updates in WU if you're using SCCM for updates :s (Unless I'm missing something?) Steve Edited June 30, 2016 by Steve21
sparkeh Posted June 30, 2016 Posted June 30, 2016 Nope, SCCM replaces WU as it goes through Config Manager as a piece of software. You can't see updates in WU if you're using SCCM for updates :s (Unless I'm missing something?) Steve Of course you are right. However its still to do with SCCM and WSUS. The OP didn't say he was using WU, just checking for updates (which I assume meant checking from the sccm client actions tab though I could be wrong). And the status nodes would be a good place to start troubleshooting.
mdrabble Posted June 30, 2016 Author Posted June 30, 2016 (edited) Is this WSUS or SCCM? As you seem to mention both. "Checking for updates" via WU wouldn't show any from SCCM etc. Steve It the WSUS role running from SCCM (Think SCCM install parts or all of WSUS to managed downloads - although I could be wrong) - I'm using SCCM to manage all updates I would spend some time trying to fix it. What do the 'Site Status' and 'Component Status' nodes report? At the moment - showing issues but that down to the lack of space on Drive C (got about 4GB free when should be at least 100GB) Need to see how and where the space has gone and try and free some up..... Edited June 30, 2016 by mdrabble
Steve21 Posted June 30, 2016 Posted June 30, 2016 Of course you are right. However its still to do with SCCM and WSUS. The OP didn't say he was using WU, just checking for updates (which I assume meant checking from the sccm client actions tab though I could be wrong). And the status nodes would be a good place to start troubleshooting. Aye, but my point was along the lines of "Rebuild a station and checked for updates and none being applied" if it's an SCCM deployment it might take a week to rediscover the machine/groups/is it a computer etc and work out what groups it is etc if you have a slow discovery cycle set. If it's WU it "should" be instant but wouldn't if it's from SCCM etc But in terms of the drive space etc, again it depends what you're setting. WU can still be set to save updates locally © even if SCCM has been set to hold it's deployment packages elsewhere, which could cause the issues etc Steve 2
Steve21 Posted June 30, 2016 Posted June 30, 2016 Few things to check space wise. Did you set both the (assuming) D drive for WSUS when you set the role, and the deployment packages within SCCM? As both spots could have the updates downloading to otherwise. no_sms doesn't block things like WU downloading locally. It just stops the clients etc installing, so would need setting to install somewhere else. Does C:\Windows\SoftwareDistribution\Download have a lot of updates in? What's HKLM\Software\Microsoft\Update Services\Server\Setup settings say it's installing to? (ContentDir etc) Steve
mdrabble Posted June 30, 2016 Author Posted June 30, 2016 Aye, but my point was along the lines of "Rebuild a station and checked for updates and none being applied" if it's an SCCM deployment it might take a week to rediscover the machine/groups/is it a computer etc and work out what groups it is etc if you have a slow discovery cycle set. If it's WU it "should" be instant but wouldn't if it's from SCCM etc But in terms of the drive space etc, again it depends what you're setting. WU can still be set to save updates locally © even if SCCM has been set to hold it's deployment packages elsewhere, which could cause the issues etc Steve yep me being impatient - SCCM handled everything so the update puzzle is solved..... Just need to figure out the lack of space issue.
Steve21 Posted June 30, 2016 Posted June 30, 2016 yep me being impatient - SCCM handled everything so the update puzzle is solved..... Just need to figure out the lack of space issue. Haha patience is a killer for SCCM ain't it! Check my above one in regards to spaces, might have missed it as you posted while I was writing I guess Steve
sparkeh Posted June 30, 2016 Posted June 30, 2016 Haha patience is a killer for SCCM ain't it! So, is it just me or do you find that sometimes nothing seems to happen for ages (ie you can see that software updates have been identified and added to the list to install) and then suddenly it all springs into life without much rhyme or reason?
Steve21 Posted June 30, 2016 Posted June 30, 2016 So, is it just me or do you find that sometimes nothing seems to happen for ages (ie you can see that software updates have been identified and added to the list to install) and then suddenly it all springs into life without much rhyme or reason? It's all in the background the set timers for it all. You have the software discovery cycle, (not install) Then the scan cycle to see what needs installing from the set list Then the actual install And if your timings are mucked up (or random wise has a funny moment) can end up waiting ages for things unless you manually kick the process off (and in the right order). For example if your discovery is 15 minutes, and scan 15 minutes. You might have your scan hit at 14 minutes, then discovery, so need to wait another 15 minutes for scan again Steve
sparkeh Posted June 30, 2016 Posted June 30, 2016 It's all in the background the set timers for it all. You have the software discovery cycle, (not install) Then the scan cycle to see what needs installing from the set list Then the actual install And if your timings are mucked up (or random wise has a funny moment) can end up waiting ages for things unless you manually kick the process off (and in the right order). For example if your discovery is 15 minutes, and scan 15 minutes. You might have your scan hit at 14 minutes, then discovery, so need to wait another 15 minutes for scan again Steve Do you know what actually triggers the update installation though? I was actually looking at an issue today where PCs were identifying that they needed an update, downloading it then just sitting there. Then, seemingly randomly, a PC would start to install. All done now but left me wondering what actually kicked the PC into launching the installation.
Steve21 Posted June 30, 2016 Posted June 30, 2016 Do you know what actually triggers the update installation though? I was actually looking at an issue today where PCs were identifying that they needed an update, downloading it then just sitting there. Then, seemingly randomly, a PC would start to install. All done now but left me wondering what actually kicked the PC into launching the installation. Machine Policy Retrevial -> Software Updates Scan Cycle -> Software Update Deployment Cycle is the way it does it, so depends what timings you got set on all those. e.g. You might have scan every 15 minutes, but install only every 2 hours in the client settings. (Software update scan schedule, deployment re-evaluation, schedule re-evaluation schedule etc ) Then based on your maintenance window and random off-set for install to stagger add that into the list Steve 1
sparkeh Posted June 30, 2016 Posted June 30, 2016 client settings Thanks, just discovered that I haven't specified anything in the client settings so it must be using defaults (whatever they are).
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