SCCM Application Deployment - /norestart but returns PendingSoftReboot


I have two applications that I am pushing out using SCCM 2012 - .Net Framework 4.5, and Visio 2016

Both of these run a setup.exe with a parameter of "/norestart".

In the first few days of using these they were working correctly, with no reboot being requested.  However something has changed and now whenever I deploy these applications they return a "PendingSoftReboot" and Software Centre notifies the user that a reboot is required.

This is frustrating as often these applications are part of a deployment task, and a reboot stops the remaining tasks from completing.

Nothing in the SCCM environment has changed and I can't figure out whats causing this.  Any ideas?

Attached is a screenshot of the log file when deploying .Net Framework 4.5

Thanks in advance
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

David Johnson, CD, MVPOwnerCommented:
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.
WolfAuthor Commented:
Hi, yeah I did see that, but I can't understand why all my application deployments have been fine up until 2 days ago when they are now all prompting for a soft reboot
Mike TLeading EngineerCommented:

I think the answer of why you are getting reboots is that it depends what the target machine was doing when it got the deployment. If there any files open that it needs to replace then it will require a reboot.

The way to mitigate this is to control the reboots yourself. I guess there are two wats to do this:

create a script wrapper
use a TS

The TS is easiest. Just create a custom TS, add a reboot before the install and one after. This is the cleanest way to install but clearly has impact on your user-base.
You could avoid the first reboot by still using a TS and setting the deployment to launch at logon. This will pretty much avoid files being open.

For the wrapper lookup "deployment bunny", Mike Niehaus. He's got a script for MDT that you can use.
Note, your command line is fine, so that's not the issue at all.


Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.