Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Thursday, April 10, 2014 5:12 PM
This is a difficult thing to search for due to its granularity, so I apologize if this is a repeat topic.
I am deploying an application with a dependency that returns the '3010' code to tell client to perform a Soft Reboot. The outcome I intended was for SCCM to install the dependency, wait for a reboot (as is the nature of the Soft Reboot to my knowledge) and then continue with the installation of the primary application after the user reboots.
However, in practice this is not what SCCM does. Instead, it seems that the notice for a Soft Reboot is acknowledged by the client, noted by the expected popup the user sees as well as the 'restart required' message in Software Center, but the deployment process continues on in the background with the installation of the primary application being deployed. It almost seems like a bug, but maybe this is the intended behavior of SCCM 2012. I just can't find any documentation anywhere that speaks to this.
All replies (5)
Thursday, April 10, 2014 6:10 PM âś…Answered
OK according to this page (which actually references Config Man 2007), a hard reboot is what I am looking for:
Here's the text:
"Soft Reboot (Reboot requested but we can still install other patches)
Hard Reboot (Reboot requested, we cannot install anything else until this is completed, not even other MSI installs)"
So I will simply change my dependent application to return code 1641 in place of 3010.
I'll mark this as my answer for now since I expect the behavior is the same for Config Man 2012. Thank you anyway, Narcoticoo.
Thursday, April 10, 2014 5:26 PM
Have you tried configuring the dependency app so that "Configuration Manager client will force a device restart", does this change the behavior?
Thursday, April 10, 2014 5:35 PM
I think this may have been a misunderstanding on my part about the specific definitions of "Hard Reboot" vs "Soft Reboot". I thought the former would immediately restart the computer, but perhaps it only halts other installations until a restart is performed by the user? And then a "Soft Reboot" basically would just act as a passive notification to the user that they should restart at some point, but the client itself would not actually take any action?
It was just confusing to me that Software Center displayed the 'restart required' status yet continued with the next part of the deployment.
To actually answer your question, I have not tried configuring the app deployment type to "Configuration Manager client will force a device restart" because to me that sounded like the client would immediately force a reboot regardless of the return code, but I only wanted the computer to reboot if the application installation returned the '3010' code (it can return others), and thus the default of "Determine behavior based on return codes" seemed the most appropriate option.
Thursday, April 10, 2014 5:53 PM
You can also configure 3010 to do something else than soft reboot, if you want to check does that change the behavior.
Thursday, April 10, 2014 5:58 PM
Yep. I guess my main goal right now is to figure out how to get the client to halt the deployment after it gets a specific return code from the dependency and wait for a restart before continuing with the rest of the deployment. If that behavior describes a "Hard Reboot" then I will simply change the code returned by my application to match. But I'm still having difficulty finding out how SCCM treats "Hard Reboots" vs "Soft Reboots".