Hi All, I was wondering how you all are managing your windows 10 in-place upgrades? Currently I am using the task sequence from this<http://blogs.technet.com/b/configmgrteam/archive/2015/06/16/revised-content-for-the-win10-in-place-upgrade-via-task-sequence-for-configmgr.aspx> site as a reference. It will use the setup.exe from the windows 10 media to launch the upgrade and keep all files/programs and settings. I have made some adjustments in the task sequence to take care of the following:
- Run a command line dpinst.exe with driver packages to install windows 10 drivers based on wmi hardware query after the restart - Install applications like office 2016. - Run a powershell script to refresh the update compliance state. I have done this so that after the upgrade the end user will nog get prompted to install old updates of windows 8.1 or office 2013. - Force a software update scan cycle. - Run a command line which basically runs the disk cleanup utility (cleanmgr) to clean out the windows.old folder. This is something I coded in auto-it since there are 2 prompts which needs a click on "yes". (Yes I know that it can also be done in powershell) :) - Run a command to disable the hibernation file. Thanks basically it. What I'm looking for is to get this upgrade process a little bit more user friendly. Currently after the upgrade, windows will come in the upgrade screen with the circle and will stay at showing 100% for quite some time since a lot of tasks are running in the background. I would like it to actually show something like the normal task sequence message box like in a normal UDI based deployment. Now, if an application requires a reboot it will reboot and come back to the normal logon screen and will continue the task sequence after the user logs in. I would like to avoid that. My other task sequence with UDI will actually logon automatically using the sytem account and continue the task sequence. Does anyone know how I can achieve that? Thanks! Best regards, Sander
