I'm guessing there's no direct download for the Win10 1709 update?

YeOldeStonecat said:
As I referred to earlier, with service packs or other major OS updates...we used to download a dedicated patch (executable) JUST FOR THAT UPDATE. Never needed to download the whole OS
Click to expand...
You only need to download it once every 6 months, make it into a bootable USB and you can use it hundreds of times for upgrades and clean installs. This is way better than needing to run a service pack update after installing an old Windows build.
 
Yep, and new builds get a fresh already up to date install? No slip streaming... just download an ISO and use Rufus to stuff it on a USB stick?

Yeah... this is much better.
 
I have monthly updated images and for those that I nuke. For those I don't nuke I keep the latest cumulative update on a stick. No waiting for download.
 
It's a "time thing"...for 20 years, unbuckling and shoving in one big update manually (and quickly)...and then especially in the past 10 years..doing that one big service pack and then letting your RMM finish the job of the remaining updates once you get the rigs onsite at the client.

While this full image update may be nice for the stand along rigs for residential...we don't do residential, and Win10 is still being a little unpredictable with patch managers in RMMs. I just have to get used to giving upcoming projects a HUUUUUUGGGEEEE time window now...and jack up our prices quite a bit for prepping Win10 rigs. I had to reschedule our cutover week because we won't be ready due to how much time this takes.
 
YeOldeStonecat said:
It's a "time thing"...for 20 years, unbuckling and shoving in one big update manually (and quickly)...and then especially in the past 10 years..doing that one big service pack and then letting your RMM finish the job of the remaining updates once you get the rigs onsite at the client.

While this full image update may be nice for the stand along rigs for residential...we don't do residential, and Win10 is still being a little unpredictable with patch managers in RMMs. I just have to get used to giving upcoming projects a HUUUUUUGGGEEEE time window now...and jack up our prices quite a bit for prepping Win10 rigs. I had to reschedule our cutover week because we won't be ready due to how much time this takes.
Click to expand...
I'm still not sure I see the problem. Why do you say having the installer on-site take so much longer than downloading the update on every machine from M$ like you used to (even before this recent issue with a couple machines crippling your 'net)?

It should be saving you a ton of time not having to download it from Microsoft for each machine. It should seriously take like 15 minutes per machine, and you should be able to kick off as many machines at the same time as you want. If I had to download the update then it would take 45-60 minutes. And god forbid you're on 1511 or the original releae, because then you have to download two updates from MS to get to 1709 (it downloads and installs 1607 first, then will do 1709 after that)

Example: At my day job we support almost exclusively windows 10 users with a mix of Pro and Enterprise licenses. I have on the network a folder that I named "1709" which is literally just a copy/paste job out of the ISO file I got from the media creation tool. If I need to update a user, I pull the folder onto their desktop over the network, double click Setup.exe and I'm off to the races. No need for MS to get in the mix, hell no need for internet connectivity. After the upgrade, then I'll do a Windows Update and put them on Patch Management.
 
Krynn72 said:
I'm still not sure I see the problem. Why do you say having the installer on-site take so much longer than downloading the update on every machine from M$ like you used to (even before this recent issue with a couple machines crippling your 'net)?
Click to expand...

We've had mass deployment down pretty good...from doing it a lot. As I mentioned before...manually doing the latest service pack for the OS...and then doing the rest onsite via the RMM patch updater...worked like a champ. We don't have to sit there and babysit with N-Ables patcher, once the profile is pushed out ...select 'em all in the portal..."patch now!" Walk way. Minimal "time per rig" for our tech. I had 2.5 hours setup per rig quoted because I assumed similar setup/deploy time/labor to Win7. We lost out on this one, I'll be at least 4 hours per on the next quote.

This 1709 update is no 15 minutes. At least based on the ~35x brand new out of the box rigs I have here with i5's, 8 gigs, and 256 SSDs. Perhaps one of my higher end clients that does i7's with 16 gigs...it may be closer to 15 minutes. But this client could only afford i5s and 8 gigs and 256 SSDs.
 
Yes the solution is to let stations already deployed to update themselves on a delay configured via GPO, new stations get the current release based on a deployment image you can make with ye old CTRL+SHIFT+F3 method, yes that means you have to make a new deployment image for all those Dells and push it to each station... and sometimes you have to use a keyviewer to pull the key from the BIOS and manually stuff it in to get the machine to activate, but that process is still quicker than 30min per station to preinstall the most recent release.

The other option is to deploy with whatever the thing has and let the unit upgrade itself, which while annoying isn't wrong either. It's not like users aren't going to have to deal with this little semiannual chore going forward.

Most shops I know are simply doing what MikeRoq suggests, blowing away what the OEM shipped and replacing it with a fresh MS stock install and going from there. Nuke the bloat, and solve the update issue all at once.

Oh, and if you havne't already, no new machines without SSDs... if you think 30-45min is bad, try installing that update on a platter disk and sitting there for 1.5-2 HOURS.
 
Sky-Knight said:
Most shops I know are simply doing what MikeRoq suggests, blowing away what the OEM shipped and replacing it with a fresh MS stock install and going from there. Nuke the bloat, and solve the update issue all at once.
Click to expand...
I do that 99% of the time. Donthave to worry about a 20+ gig windows.old file that way.
 
Winkey + r, cleanmgr <enter>
Click Cleanup System files Button
Tick the box next to Previous Windows Installations
Click OK...

Or...

Just wait two weeks, it'll remove itself.
 
Well then you'll want to run the cleanup anyway because there is a ton of leftover win updates cached you can nuke too. Though, that means that station cannot provide them to the LAN, which really saves a bucket of bandwidth.

I'm the same way regarding disk space, especially on small SSDs... but sometimes you have to stop and think about what is worth it when it comes to time investment.
 
True, but once the thing is deployed it's sharing with other stations where it lives. And it's not like it won't, because it'll get updates as it goes and share those.

Just saying that if you have a box in office and it's going back to a place that has older Win10 stations that haven't updated yet, you can save them some bandwidth by leaving it.

But you have to leave this "bloat" behind, and it makes your eye twitch... I get it!
 
People live in single computer homes? Here they outnumber us... if they ever get smart enough to take over we're boned.
 
You must log in or register to reply here.

Similar threads

HCHTech
Windows 11 - Outlook display issue after latest office update?
2
Replies
22
Views
2K
NETWizz
NETWizz
HCHTech
XPS13 not respecting "Do Nothing" setting for "Choose what closing the lid does"
Replies
5
Views
843
Markverhyden
Markverhyden
Sky-Knight
Arista Edge Threat Management v17 Release Candidate (Untangle)
Replies
9
Views
972
Sky-Knight
Sky-Knight
thecomputerguy
Relatively new laptop no boot (possible bad NVme), can't install W11 on new NVme.
Replies
8
Views
887
thecomputerguy
thecomputerguy
thecomputerguy
Story Time. Simple install went to hell in a handbasket REAL quick! Learned some things!
Replies
16
Views
2K
Sky-Knight
Sky-Knight
Back
Top