chekmate1984 Posted November 29, 2018 Posted November 29, 2018 hi all Joined here recently at a school and noticed windows updates have not been done since 2017!! I can see version is 1709 for windows 10 Even servers have not been updated for sometime. We use SCCM but thinking to use WSUS for this Whats best way you would do this? would you just approve all and let it do it thing or stagger the updates?
ShellfishClive Posted November 29, 2018 Posted November 29, 2018 I wouldn't update them all at the same time, I'd probably wait until Christmas and do some manual updating on a batch of machines to gauge the time it will take and roll the updates out daily while the staff are out. Probably better to just make a new build on the latest version of Windows and re-image though because you'll get this problem every time you re-image a machine with the old build after updating.
chazzy2501 Posted November 29, 2018 Posted November 29, 2018 if you use SCCM then that has taken place of your wsus, or should I say don't try an use wsus directly. I gave ip on SCCM as I couldn't phantom how you SCCM to distribute updates. etc. The product is too large and complex to just start using.
3s-gtech Posted November 29, 2018 Posted November 29, 2018 Are you sure updates haven't been applied, or are the machines just on 1709? If the latter, 1709 is still a supported release and will be for a while yet. If the former, with the update roll-ups now used, it shouldn't take too long to catch them all up. Try to push out later updates, rather than approving everything and therefore downloading masses of superseded stuff. I always leave a bit of time after deploying the latest updates, especially with MS's recent track record with update quality.
Mujja Posted December 3, 2018 Posted December 3, 2018 I wouldn't update them all at the same time, I'd probably wait until Christmas and do some manual updating on a batch of machines to gauge the time it will take and roll the updates out daily while the staff are out. Probably better to just make a new build on the latest version of Windows and re-image though because you'll get this problem every time you re-image a machine with the old build after updating. If you're talking about a patched reference image unless you create a new image every month with the latest Cumulative update it'll be out of date the following month. With the release of Windows 10 we deploy the WIM from the ISO and add everything else during the SCCM task sequence etc.
Mujja Posted December 3, 2018 Posted December 3, 2018 Are you checking in Settings or Control Panel and Installed Updates? If the updates have been deployed using SCCM they won't show in the Settings app. Check what your SCCM Software Update point is downloading and deploying, is an ADR (Automatic Deployment Rule) configured? Is the ADR deployed to a blank to test collection? For feature updates (1709>1803) check if Windows 10 Servicing has been configured.
Sonic007 Posted December 4, 2018 Posted December 4, 2018 I can beat that. I joined a new job and servers hadnt been updated since 2015! It will take along time to update and with that amount of updates expect something to go wrong so make sure you backup first.
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