Windows 10 October 2018 Update

Description

This agent procedure will upgrade Windows 10 to October 2018 update (Build 1809.)
This will perform an entire Operating System upgrade, it is recommended to perform a backup and/or system restore point before proceeding with the OS upgrade.
The workstation will be restarted as part of the procedure.
The whole process takes between 45 minutes and 2 hours until the workstation can be used again.
It is recommended to have at least 20GB free on the endpoint before running the procedure, otherwise the procedure could fail without giving any error message.
This listing does not require to upload any files. It will download a file directly form Microsoft to perform the upgrade.
We suggest researching the potential impacts of these update(s) to your systems prior to deployment as 1809 has been known to cause BSOD in some environments.

Here is a Webinar we made about how to help the upgrade process and what to watch for before hand.

Summary

Reviews

Discussion

Is there a way to have Reboot prompts implemented during this process? So far it just reboots the pc when needed, but i would like to have some reboot notifications prompts.

Thanks

David Bennett
11 days ago

You can change the command line to add a /NoReboot so you can better control the reboot (i.e. prompt the user what's going to happen). Note this only affects the first reboot. That makes sense, as the user has no idea something is going on prior to the first reboot. After the first reboot, the system is going through setup so it's obvious what's happening, and the subsequent reboots don't impact a user as they can't work.

Microsoft docs say:

/NoReboot

Instructs Windows Setup not to restart the computer after the down-level phase of Windows Setup completes. The /noreboot option enables you to execute additional commands before Windows restarts. This option suppresses only the first reboot. The option does not suppress subsequent reboots. For example:Setup /noreboot

Mikhail
11 days ago

David,

Thank you very much for the reply and yes I meant the first reboot. Just want to make sure I get this right, do I add it between /skipeula and /auto upgrade :

between /skipeula and /auto upgrade should be fine... it needs to be on that command line

You'll have to add some checking to determine when the reboot needs to occur, then trigger the reboot warning to your user. Of course, you could "assume" the initial process will take X minutes and just do the reboot after. That's uglier than heck.

I haven't looked to determine what to parse out of the log, or if there is an errorlevel status returned that would be your trigger for doing the reboot. Shouldn't be hard to determine.

Course you could turn this on it's head and just run thru the process if the machine does NOT have a logged in user, and if it does, just pop up a message asking the user to logoff when they are done so you can run the update. Then schedule the update to run again in 30 minutes. It'll keep looping and rescheduling every 30 minutes if a user is logged in, and if not then the update will fire off. Let it reboot as it wants to since no one is logged in, no one will care.

Andy Begeman
about 9 hours ago

Hi, What would I need to add to this script for it to pull from a UNC path as opposed to downloading it from the internet?

Douglas Sanchez
about 8 hours ago

Hey @Andy.

I would recommend taking a look at the discussions in these 2 listings as a lot of customers shared the way they modified the procedures for their network/environment.