Allow OS Upgrade and Custom Task Sequences to queue status messages during offline execution
When OS Upgrade and Custom task sequences are running offline (such as following a reboot while on VPN) all task sequence manager status messages are discarded. While this is expected in WindowsPE, it would be beneficial for troubleshooting/reporting if OS Upgrade and Custom task sequences would queue status messages locally just like Executive Manager does with software installation status.
Cory Bailey
shared this idea
6 comments
-
Joe Novo
commented
Add me as another vote for this idea. With WFH scenarios so prevalent it would be nice to have a TS variable to control whether or not the queue status messages for later upload when system is able to reach the MP again.
-
SCCM 2020
commented
Hello,
I had this idea today...because of the vpn interferes after reboot i created an IPU ts that has 70 hardware models drivers with query and a deployment of download when needed..in the end user will only have 2gb of drivers installed, after the drivers step i have a new option to copy all the necessary IPu files to local computer, after rebooting ts will continue to install 1909 regardless off VPN.
What donyou think? 😎? -
Anoni
commented
That would be great
-
Tobias Abele
commented
Would be very helpful for InPlace Upgrade TS, we have a high percentage of Deployments reporting as "In Progress", reason turned out to be VPN Scenario, wehre dring the "Upgrade Operating System" Step the reboot disconnects VPN. and after that all Status is lost.
-
Rick
commented
Add me as another up vote for this one. Half of our work force is work from home. It's tough to get any accurate results when all our remote user are sitting as "In Progress" when doing feature updates using a task sequence. I have to rely on queries to see what machines have upgraded or failed.
-
kedia990
commented
This is a great idea! We're relying on OS upgrade task sequences to deploy Win10 feature updates to users with laptops in the field, and are currently losing all feedback from the update process. "Monitoring for free" was one of the key reasons based on which I was able to "sell" the idea of using upgrade task sequences to management (as opposed to just writing a script), so I'd say this is pretty important.