Start ProgressUI after reboot in Task Sequence at logon screen (non OS TS)
When you use Task Sequences (TS) to deploy software (non OS TS) and there is a reboot inside of the TS there will be no ProgressUI at the logon Screen after the reboot. So you can't see the Progress of the running TS or there is a TS running.
If You logon, after a short time the ProgressUI will start.
We started a MS Case (REG:116092814729429): This is a expected behavior because it's not planned for out of WinPE stage.
Please implement the start of the ProgressUI after the reboot inside of the TS, so we can see the Progress at the logon Screen.
Florian H. commented
I think MS will not implement an solution for this issue.
We helped us out with following workaround.
Here are my TS steps:
1. "Run Command Line" (Enable Upgrade Message)
cmd /c reg add "HKLM\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Policies\System" /v legalnoticecaption /t REG_SZ /d "Windows 10 Upgrade in Progress" /f
reg add "HKLM\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Policies\System" /v legalnoticetext /t REG_SZ /d "Your PC is upgrading to Windows 10, this might take a while. Don't turn off your PC." /f
2. -> Normal TS Steps <-
3. "Run Command Line" (Disable Upgrade Message)
cmd /c reg add "HKLM\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Policies\System" /v legalnoticecaption /t REG_SZ /d "" /f
reg add "HKLM\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Policies\System" /v legalnoticetext /t REG_SZ /d "" /f
Do you know any workarounds for informing the user about a running task sequence on the logon screen and lockscreen? We're having problems with Windows 10 1803 Upgrade failures because of users interfering with the upgrade process.
What I know of so far (all very ugly, incomplete and inconvenient solutions):
- Legalnoticecaption and legalnoticetext registry keys
- MSG.exe to show an ugly MessageBox
- Change the lockscreen
I know about some third party client management software that has an information window on the lockscreen (Empirum for example). Maybe I could have a look how they do it.
Btw. it's a shame how Microsoft keeps ignoring popular feature requests on this platform.
That would be really helpful to avoid user reboots or app starts.
We have faced the same issue when we are upgrading the Office from 2013 to O365 with TS. There is a reboot step after you uninstall the Office 2013 and after restart step Office 365 get install. Many user reported that are not sure if the upgrade is still running or not.
There are several 3rd party workarounds for notifying user of progress during an in-place OS upgrade but a supported native solution would be best.
Wade Atkinson commented
You state that the ProgressUI will return after the user logs in. This is only the case if they log in before the TS starts back up again. If not they will never see a progress bar.
Another aye for this one. Also having to reboot into PE to change ui language to en-us to proceed with multi language upgrade from 1607 to 1709. Comes back to typical login screen with the user having no idea that the upgrade is still in progress.
Marc-André Chartrand commented
exactly what we need for out Windows10 Upgrade TS, which has a first step to go in WinPE to change base language to english, updates BIOS' then goes back to OS to start the upgrade, but users land at the logon screen and no TS Progress is shown... So they login and start working, then Upgrade OS Step kicks in and reboots in their face. Having the progress on the LockScreen, or even better, preventing the users to login until the TS is complete, would be perfect.
Florian H. commented
We need this too for Inplace Upgrade to Windows 10.
Please provide a workaround!
Customers are looking for this feature..It is important since we are moving to windows as a service model
Levi Stevens commented
This would be huge. We use TS for our Office 365 and CRM rollouts, and don't really want users logging back on until it is finished.
Yes please! This would be massively useful. we often get users logging on to a system that is in progress of running an update task sequence. so we have to try and block logon at the start and undo it at the end.