What version LDMS are you using? It would be great and we had the same idea but not sure if it's just LDMS 9.6 SP2 or other versions too but it doesn't appear they've updated the scheduled task properties when it comes to scheduling OS Prov templates (along with multiple other features). They are still using delivery methods instead of agent settings and it's greyed out and cannot be changed from policy-supported push.
I'd imagine if this is fixed to use agent settings then you could create an in-place Windows 10 upgrade provisioning template like we have done and then schedule the task as a policy set to optional which will publish in the portal manager / workspaces.
Alternatively, and rather not recommended, option is to add everyone into user management and give public OSD perms and then put the locked template into public area and advise everyone how to PXE boot and select the in-place upgrade template.
The thing about the OS provisioning process is that it's very much overblown for an In-Place windows 10 upgrade. The installer can be sent triggers to initialize itself along with an unattend.xml file.
I think running setup.exe with switches might just do the trick....
I think that running setup as a standard application deployment may work for me. This is only for an in-place upgrade where I want all the user documents and applications to remain. For clarity.
I will respond with more once I've tested this thoroughly.
Yeah so I actually decided to refresh my memory and yes you could just use a package and then that would use proper agent settings which would allow it to be advertised to the portal. The problem I foresee, since I haven't tested, would be the reporting back to the task as successful / failed.
If it helps we have the following command-line:
setup.exe /auto upgrade /showoobe none /DynamicUpdate disable /copylogs %%SYSTEMDRIVE%%\sd\log\LD_W10Install
Prior to that our template does map preferred server, create required dirs., copy the source files locally, run pre-req scripts (basically just cleans the OS and removes AV)
We're very much in the early stages and testing / tweaking everything though.
1 of 1 people found this helpful
Thanks for the help.
I was able to test this last night. It reported back a successful install and did succeed. Here's the command line I used (it's similar):
setup.exe /auto upgrade /quiet /PKey <commented out> /migratedrivers all /DynamicUpdate disable /Telemetry Disable /uninstall disable /ResizeRecoveryPartition enable
This worked and resulted in a succeeded installation. My thought on upgrading to Windows 10 is to not have just one way to do it, but many. I'd like a self service item for those who are wanting to install it soon. A clean wipe option for re-images and an option that backs up user data and then performs a complete re-image and restores the user data. (the last option would be for technicians to baby where the computer should be wiped because its in a poor state)
I think this will work pretty well for an in-place upgrade option. It's super simple.
Above answer works very nicely. Setup.exe takes care of this. Microsoft has come a long with with this, lovely.
"The problem I foresee, since I haven't tested, would be the reporting back to the task as successful / failed."
That is exactly what happens. The task never reports back as either successful or failed. It remains active even though the client has finished running the task.
I'd also like to force a reboot before the actual grade but all attempts to force this to happen, either reboots and does not upgrade or does not reboot and does upgrade.
We have also tried running additional template actions after the Win10 upgrade completes, only to have the client appear stalled and the provisioning GUI remaining open and unable to close, even through no work is being done. I'm not sure how to resolve these but if I find answers, I'll let everyone know.
Veryrich. We still haven't fully migrated to Windows 10. What's that say about the OS?
I'm afraid Microsoft has a lot of work to do here still.
We plan on starting our migration fourth quarter of this year. I'll update this note as we find things out. Stay tuned.