locked
Exit Code 3010 and forced reboots RRS feed

  • Question

  • Hi,

    As part of our App-V 5 deployment we install Visual C++ redists as dependencies.  These are installed with norestart e.g.

    vcredist_x64.exe /q /norestart

    However these sometimes exit with a code of 3010 (soft-reboot).  One would assume that a soft reboot can be deffered but in this case SCCM forces a reboot with the default countdown as set in the client settings.  This means the PC will reboot and the user cannot defer it (bad).

    Why is SCCM treating a 3010 in this way?  Is it because it is a dependency?

    AppEnforce.log

        Performing detection of app deployment type Microsoft Visual C++ 2005 Redistributable (x86)(ScopeId_C9B67C50-C96A-40F2-BC8F-D804B15217FD/DeploymentType_ae1eb76f-803d-4571-a11a-a7f08d99dbfd, revision 7) for system.	AppEnforce	02/07/2013 09:24:02	2720 (0x0AA0)
    +++ Application not discovered. [AppDT Id: ScopeId_C9B67C50-C96A-40F2-BC8F-D804B15217FD/DeploymentType_ae1eb76f-803d-4571-a11a-a7f08d99dbfd, Revision: 7]	AppEnforce	02/07/2013 09:24:02	2720 (0x0AA0)
        App enforcement environment: 
    	Context: Machine
    	Command line: msiexec /i "vcredist.msi" /qn /norestart
    	Allow user interaction: No
    	UI mode: 1
    	User token: null
    	Session Id: 4294967295
    	Content path: C:\Windows\ccmcache\f
    	Working directory: 	AppEnforce	02/07/2013 09:24:02	2720 (0x0AA0)
        Prepared working directory: C:\Windows\ccmcache\f	AppEnforce	02/07/2013 09:24:02	2720 (0x0AA0)
    Found executable file msiexec with complete path C:\Windows\system32\msiexec.exe	AppEnforce	02/07/2013 09:24:02	2720 (0x0AA0)
        Prepared command line: "C:\Windows\system32\msiexec.exe" /i "vcredist.msi" /qn /norestart /qn	AppEnforce	02/07/2013 09:24:02	2720 (0x0AA0)
    Valid MSI Package path = C:\Windows\ccmcache\f\vcredist.msi	AppEnforce	02/07/2013 09:24:02	2720 (0x0AA0)
        Advertising MSI package [C:\Windows\ccmcache\f\vcredist.msi] to the system.	AppEnforce	02/07/2013 09:24:02	2720 (0x0AA0)
        Executing Command line: "C:\Windows\system32\msiexec.exe" /i "vcredist.msi" /qn /norestart /qn with system context	AppEnforce	02/07/2013 09:24:02	2720 (0x0AA0)
        Working directory C:\Windows\ccmcache\f	AppEnforce	02/07/2013 09:24:02	2720 (0x0AA0)
        Post install behavior is BasedOnExitCode	AppEnforce	02/07/2013 09:24:02	2720 (0x0AA0)
        Waiting for process 3288 to finish.  Timeout = 15 minutes.	AppEnforce	02/07/2013 09:24:02	2720 (0x0AA0)
        Process 3288 terminated with exitcode: 3010	AppEnforce	02/07/2013 09:24:35	2720 (0x0AA0)
        Looking for exit code 3010 in exit codes table...	AppEnforce	02/07/2013 09:24:35	2720 (0x0AA0)
        Matched exit code 3010 to a PendingSoftReboot entry in exit codes table.	AppEnforce	02/07/2013 09:24:35	2720 (0x0AA0)
    

    I could change the behavior so SCCM does nothing when this finishes but I don't see what I should need to when 3010 should not enforce a reboot.

    This link refernces similar behaviour but I am curious as to why the reboot is forced...

    http://www.1e.com/blogs/2013/05/07/sccm-2012-agent-reboots-when-msiexec-uses-reallysuppress-switch/

    Thanks


    Friday, July 5, 2013 10:05 AM

Answers

  • The best way to install the App-V client is to use the exe and let it install the requirements instead of doing it yourself.

    Jason | http://blog.configmgrftw.com

    Friday, July 5, 2013 4:34 PM

All replies

  • I think that this is caused by the dependency, but I am not aware that this is documented somewhere.

    Torsten Meringer | http://www.mssccmfaq.de

    Friday, July 5, 2013 10:22 AM
  • Indeed, seems like a rather grey area.  For the time being I can change the behavior so the reboot does not happen but would be nice to see this acknowledged by MS. 
    Friday, July 5, 2013 11:00 AM
  • hi ,

    which installtion file you are using  

    vcredist_x64.exe  OR   vcredist.msi  (log files says vcredist.msi)

    if use msi file use  below commandline

    msiexec /i "vcredist.msi" /qn /REBOOT=ReallySuppress   otherwise it will throw the Reboot error

    thanks


    shinu

    Friday, July 5, 2013 11:42 AM
  • If you want the countdown to work, you can configure the application so that "Configuration Manager forces reboot", then the client settings for countdown are taken care of..

    • Proposed as answer by Narcoticoo Friday, July 5, 2013 12:09 PM
    Friday, July 5, 2013 12:09 PM
  • Does this return a different return code to using the .exe with /norestart?  This article suggests not...

    http://www.1e.com/blogs/2013/05/07/sccm-2012-agent-reboots-when-msiexec-uses-reallysuppress-switch/

    Friday, July 5, 2013 12:40 PM
  • The best way to install the App-V client is to use the exe and let it install the requirements instead of doing it yourself.

    Jason | http://blog.configmgrftw.com

    Friday, July 5, 2013 4:34 PM
  • The best way to install the App-V client is to use the exe and let it install the requirements instead of doing it yourself.

    Jason | http://blog.configmgrftw.com

    Whilst this may be true, there are other flavours of the Visual C++ redists which also need to be installed on client machines to ensure that the sequenced apps will run and that your clients have the same redists as the sequencing stations.  These flavours which are not installed by the App-V client setup also show this behaviour.
    Monday, July 8, 2013 8:06 AM
  • Without the reboot, you may as well not even install the application though -- it's requesting a reboot for a reason: to make it functional.

    Also, ConfigMgr does not offer reboot deferment, never did. ConfigMgr is about enforcing deadlines in general. Thus, you can raise your reboot timeout from the default 90 minutes to something much higher (I think 8 or 12 hours is the maximum though). That is roughly equivalent to the user deferring the reboot.


    Jason | http://blog.configmgrftw.com

    Monday, July 8, 2013 12:57 PM
  • Without the reboot, you may as well not even install the application though -- it's requesting a reboot for a reason: to make it functional.

    Also, ConfigMgr does not offer reboot deferment, never did. ConfigMgr is about enforcing deadlines in general. Thus, you can raise your reboot timeout from the default 90 minutes to something much higher (I think 8 or 12 hours is the maximum though). That is roughly equivalent to the user deferring the reboot.


    Jason | http://blog.configmgrftw.com

    Indeed, I've upped it to 8 hours.  Unfortunately for us we manage a research environment where forcing reboots is simply a no-no as machines are often left running complex tasks which may take hours/days to complete.  I have switched to the .exe installer though and then pushed the other redists out to the machine as individual applications and in this case the return codes are treated correctly and the forceful reboots do not occur.
    Monday, July 8, 2013 1:07 PM
  • The switch your deployments to available instead of required. As mentioned, no reboot, no functionality anyway.

    Jason | http://blog.configmgrftw.com

    Monday, July 8, 2013 1:25 PM