Intune/Autopilot Windows Updates
When deploying a device with Autopilot, they come shipped with older versions of Windows (1703). Some policies are only compatible with later versions of Windows. It would be great if Intune/Autopilot could initiate that OS update as part of the deployment.
Happy to announce this is completed. Here’s a link to the docs
Thanks for your feedback!
Tom Plant commented
Agree with the other comments, this isn't completed.
We received a batch of ~180 Surface Pros running 1803, which all required manual upgrades because they didn't support Autopilot White Glove. A solution is needed other than shipping everything back to the vendor.
I absolutely agree with Tobias Renström.
"It would be great if Intune/Autopilot could initiate that OS update as part of the deployment", meaning during the Autopilot process.
Tobias Renström commented
To me this is not solved? The docs says: ”Windows 10 feature update policies cannot be applied during the Autopilot out of box experience (OOBE) and will only apply at the first Windows Update scan after a device has finished provisioning (which is typically a day).”
This option would benefit everyone a great deal
Definitely required. You can break into the command prompt (Shift+F10) then run the Settings app (start ms-settings:) then run updates. But that is very cumbersome. All it requires is an option to update, yes/no.
Matt Engoglia commented
I think this is important as new features come (with windows and/or intune) and require you to be on a newer version of windows. This is especially important when you want to upgrade and vendors have stocks of devices with the previous version.
Urs Rieser commented
1703 is ancient - must work automatically
This will really help in deployments and would solve so many issues with configurations, not present in older versions but needed on our customers site.
Matias Hohl commented
This is really critical for us as we want to use hybrid join and this is only supported with 1809 or newer.
We need to set a required base version of the Windows OS to start AutoPilot with. So if the desired OS level is not installed, the necessary updates have to be installed and only then the AutoPilot process kicks off.
Stefan Winiger commented
it is critical for us to have this !
Patrick Morandi commented
This is a very important feature because we can't ensure which version the hardware vendor ships with. It would be best if we could specify in the autopilot configuration which version the client has to update to before the autopilot phase starts.
Kevin Kaminski commented
This problem is becoming more critical as bugs with autopilot enrollment require a newer version of Windows for resolution. Right now people have to re-image their machine with a newer version of Windows to fix enrollment problems.
Ben Hos commented
This, I currently wish to use 1809 features and as of this comment Lenovo are currently only shipping devices with 1803.