Menu
This week I will do a small post about working with the restart behavior of installations in combination with the Application Model in ConfigMgr 2012. In previous versions there was sometimes a need to use a batch file to catch some weird installation return codes. The nice thing about ConfigMgr 2012 is that it gives us a possibility to specify those return codes and to react on it. In the rest of this post I will show in three steps how to configure ConfigMgr 2012 to work with return (restart) codes.
Find the Status of an SCCM Application on a Client Sometimes I don't want to fool around with the SCCM deployment reports. They're either too slow, I'm too lazy to open the console or I'm already in my Powershell console so I just want to do it there. Sccm 2012 Deployment Waiting For Another Program On Your Computer. 1/12/2018 0 Comments. Working with the restart behavior of Applications in ConfigMgr 2012. Then SCCM will reboot if program. Understand why the computer restarted until I read your.
Step 1: Return codes The first thing I always do is running the installation of an application a few times and see which return codes it gives me. Based on those experiences I create, if needed, some extra entries in the Return Codes –tab of the Properties of the Deployment Type. By default the following return codes are pre-defined:.
0 – Success (no reboot). 1707 – Success (no reboot). 3010 – Soft Reboot. 1641 – Hard Reboot. 1618 – Fast Retry Step 2: Enforce specific behavior The second thing I do is determining how I think the client should react on the return codes. This can be configured, on the User Experience –tab of the Properties of the Deployment Type, by selecting one of values under Should Configuration Manager enforce specific behavior regardless of the application’s intended behavior?
The following options are available (including small explanation):. Determine behavior based on return codes – (Default) The client will perform any action needed based on the return code of the application. Note: In this case a good configuration in the first step is very important. No specific action – The client won’t perform any action.
Note: In this case it is possible to completely suppress a restart. The software install program might force a device restart – The client is told that the installation will force a restart. Configuration Manager client will force a mandatory device restart – The client will always perform a restart. Step 3: Restart behavior The third, and last, thing I do is more a general client setting. From the moment we decide to restart the device we should think about the configuration of the Computer Restart –settings in the Client Settings.
The following Device Settings can be configured:. Display a temporary notification to the user that indicates the interval before the user is logged of or the computer restarts (minutes) – Default is 90 minutes. Display a dialog box that the user cannot close, which displays the countdown interval before the user is logged of or the computer restarts (minutes) – Default is 15 minutes. Conclusion The combination of these three steps gives us a lot of options to work with the restart behavior of installations. In most cases the default configuration is perfect, but in some case some tuning is needed.
For example, the installation of an application is not allowed at any time. This can be achieved by either configuring a custom return code in the first step, or by specifying No specific action in the second step. Note: There are also Maintenance Windows and/ or Business Hours, that can influence the restart behavior. I didn’t mention them here, because, yes they can exist, but there should always be a moment that we “touch” a users’ device and this is about that moment.
The following note about “No specific action” is somewhat unclear:.Note: In this case it is possible to completely suppress a restart Does this mean that No specific action merely tells ConfigMgr to ignore a restart request by an application installer, or does it have some kind of super-power whereby it can suppress ANY attempt by an application to reboot the system? The note above would seem to indicate that it has the supreme power of suppression, but I think it may be just be inaccurately worded. I’m just trying to get a definitive answer on this. Hi Peter, I use a vbscript to run an application with all the return codes you have mentioned set in the return codes tab and Determine behavior based on return codes selected. This script has dependencies which reboots and then the execution of the vbscript starts. It has two commands with noreboot command but while it succesfully runs the first one without any problems it reboots before the installation gets completed for the second command. So could it be a diffcode that i need to put in the return code tab or if i use a cmd that wrap the vbscript with whatever return codes to be presented as success to SCCM that would fix this?
This was super informative. Do you know of any reason why a return code of 3010 (pendingsoftreboot) would cause devices ignore the reboot behavior set in Client Settings? My Client Settings are set to 300 minutes initial notification and then 30 minutes of cannot close on the dialog. But, I have one application deployment that returns 3010 (as it should, it needs a reboot), but then does the default of 90 minutes notification and 15 minutes of cannot close. I have the restart settings on the Default Client Settings – and that setting is not specified in any other client setting.
Hi Peter Great article I have a question I have deployed dotnet4.7.1 with the following command in my application NDP471-KB4033342-x86-x64-AllOS-ENU.exe /q /norestart /ChainingPackage ADMINDEPLOYMENT if I look at the client logs it’s return code is 3010 The computer still seems to reboot as per the client defaults (in our case 15 minutes) I have also set the the user experience to “no specific action” with the same results. Is this normal behaviour? My understanding is that it should not reboot if a return code is 3010 and/or you set the user experience to “no specific action” thanks in advance.