none
SCCM 1602 OSD Win 10 1602 - CcmSetup is exiting with return code 7

    Question

  • Hi all,

             SCCM 1602, deploying Windows 10 education 1602.

    Reference build captured, no issue.

    Production build is failing while installing the SCCM client ver 5.0.8355.1003.

    This is a new OSD build, not an upgrade of existing clients. The issue is, it causes the task sequence to stop and leaves the client in provisioning mode.

    ccmsetup.log (last few lines)

    <![LOG[MSI: Action 9:19:15: RemoveExistingProducts. Removing applications]LOG]!><time="09:19:15.176-570" date="04-18-2016" component="ccmsetup" context="" type="0" thread="420" file="msiutil.cpp:316">
    <![LOG[File C:\WINDOWS\ccmsetup\{6241CB95-11E9-4108-92B3-06AABA463A4E}\client.msi installation succeeded. Windows Installer has requested a reboot.]LOG]!><time="09:19:15.286-570" date="04-18-2016" component="ccmsetup" context="" type="1" thread="420" file="msiutil.cpp:835">
    <![LOG[No client language or update changes are detected per current client.msi.]LOG]!><time="09:19:15.286-570" date="04-18-2016" component="ccmsetup" context="" type="0" thread="420" file="ccmsetup.cpp:8685">
    <![LOG[Params to send '5.0.8355.1003 Deployment Error: 0x0, ']LOG]!><time="09:19:15.286-570" date="04-18-2016" component="ccmsetup" context="" type="0" thread="420" file="state.cpp:208">
    <![LOG[Sending message with STATEID='401' via the existing client.]LOG]!><time="09:19:15.286-570" date="04-18-2016" component="ccmsetup" context="" type="1" thread="420" file="state.cpp:356">
    <![LOG[<ClientDeploymentMessage ErrorCode="0"><Client Baseline="1" Platform="2"/></ClientDeploymentMessage>]LOG]!><time="09:19:15.364-570" date="04-18-2016" component="ccmsetup" context="" type="1" thread="420" file="statedetails.cpp:108">
    <![LOG[Deleted file C:\WINDOWS\ccmsetup\ccmsetup.cab.download]LOG]!><time="09:19:15.379-570" date="04-18-2016" component="ccmsetup" context="" type="1" thread="420" file="ccmsetup.cpp:9708">
    <![LOG[Deleted file C:\WINDOWS\ccmsetup\ccmsetup.xml]LOG]!><time="09:19:15.379-570" date="04-18-2016" component="ccmsetup" context="" type="1" thread="420" file="ccmsetup.cpp:9708">
    <![LOG[Task 'Configuration Manager Client Upgrade Task' does not exist]LOG]!><time="09:19:15.379-570" date="04-18-2016" component="ccmsetup" context="" type="0" thread="420" file="wintask.cpp:661">
    <![LOG[CcmSetup is exiting with return code 7]LOG]!><time="09:19:15.379-570" date="04-18-2016" component="ccmsetup" context="" type="1" thread="420" file="ccmsetup.cpp:10850">

    smsts.log

    <![LOG[Process completed with exit code 7]LOG]!><time="09:19:15.426-570" date="04-18-2016" component="OSDSetupHook" context="" type="1" thread="1812" file="commandline.cpp:1124">
    <![LOG[Client installation failed, code 7]LOG]!><time="09:19:15.426-570" date="04-18-2016" component="OSDSetupHook" context="" type="3" thread="1812" file="installclient.cpp:1151">
    <![LOG[Set authenticator in transport]LOG]!><time="09:19:15.442-570" date="04-18-2016" component="OSDSetupHook" context="" type="0" thread="1812" file="libsmsmessaging.cpp:7908">

    ![LOG[Command line: "C:\WINDOWS\system32\_SMSOSDSetup\TsProgressUI.exe" /Unregister]LOG]!><time="09:19:16.661-570" date="04-18-2016" component="TsProgressUI" context="" type="0" thread="4080" file="winmain.cpp:332">
    <![LOG[Unregistering COM classes]LOG]!><time="09:19:16.661-570" date="04-18-2016" component="TsProgressUI" context="" type="1" thread="4080" file="winmain.cpp:204">
    <![LOG[Unregistering class objects]LOG]!><time="09:19:16.661-570" date="04-18-2016" component="TsProgressUI" context="" type="1" thread="4080" file="winmain.cpp:495">
    <![LOG[Shutdown complete.]LOG]!><time="09:19:16.661-570" date="04-18-2016" component="TsProgressUI" context="" type="1" thread="4080" file="winmain.cpp:512">
    <![LOG[Process completed with exit code 0]LOG]!><time="09:19:16.661-570" date="04-18-2016" component="OSDSetupHook" context="" type="1" thread="1812" file="commandline.cpp:1124">
    <![LOG[Successfully unregistered TS Progress UI.]LOG]!><time="09:19:16.661-570" date="04-18-2016" component="OSDSetupHook" context="" type="1" thread="1812" file="utils.cpp:3087">
    <![LOG[Failed to install SMS Client (0x80004005)]LOG]!><time="09:19:16.661-570" date="04-18-2016" component="OSDSetupHook" context="" type="3" thread="1812" file="basesetuphook.cpp:1517">

    The new client requesting a reboot is fine - but having the OSD process accept this would have been good.
    Anyone got a current work-around ?

    Monday, April 18, 2016 4:03 AM

Answers

  • Hello there,

    Have you attempted the following?

    Option Steps A - Force Reboot Client Switch

    1. Open ConfigMgr Console

    2. Navigate to Software Library \ Operating Systems \ Task Sequences

    3. Select the task sequence in question

    4. Select it, right click and select Edit

    5. Select the Setup Windows and ConfigMgr step

    6. Add the /forcereboot switch to the Installation Properties

    7. Click Apply and then Ok

    8. Perform deployment

    Another option would be to place a Reboot right after the Setup Windows and ConfigMgr step, but I do not think it will be as effective or clean.

    Option Steps B – Add Reboot after Setup Windows and ConfigMgr

    1. Open ConfigMgr Console

    2. Navigate to Software Library \ Operating Systems \ Task Sequences

    3. Select the task sequence in question

    4. Select it, right click and select Edit

    5. Select the Setup Windows and ConfigMgr step

    6. Select Add \ General \ Restart Computer

    7. Select Restart Computer

    Thursday, June 23, 2016 9:22 PM

All replies

  • Jason wrote a blog post about this and a possible cause of an Exit Code 7: http://blog.configmgrftw.com/ugh-ccmsetup-error-codes/


    Simon Dettling | msitproblog.com | @SimonDettling

    Monday, April 18, 2016 5:40 AM
  • Thanks for that - that explains what is happening....

    Given that the client package is part of the "setup windows and configmgr" step... we cant define custom error codes

    and having .net framework 4.6 for windows 10 already installed as part of the reference build doesn't seem to get around this....

    Have just run a build, with "Continue on error" ticked for that step - and that doesn't seem to help either....

    So while Jason's article does indeed point out the cause, im unfortunately still not sure how to get around it.

    Monday, April 18, 2016 6:49 AM
  • Maybe some other Component like Silverlight or Visual C++ is requiring a Reboot. Have you checked all the (Prereq) Logs at "C:\Windows\ccmsetup\Logs"?

    Simon Dettling | msitproblog.com | @SimonDettling

    Monday, April 18, 2016 6:54 AM
  • I've not run into this issue myself, but have you included the required Visual C++ in your image? I've seen ccmsetup.exe exiting with error code 7 when the Visual C++ installer returned with 3010 (installation successful, reboot required).

    Nickolaj Andersen | www.scconfigmgr.com | @NickolajA

    Monday, April 18, 2016 6:56 AM
  • this is part of a production build guys, so the SCCM client has already been installed as part of the reference build - so the prereqs are already installed,

    Interestingly, ive also been unable to replicate this in a test environment.

    Im going to re-capture and see if the issue persists.

    Wednesday, April 20, 2016 9:14 AM
  • Were you able to find a resolution to this?  I am having the exact same issue after adding the cumulative update to our Windows 10 Enterprise build.  The ccmsetup exits with a return code 7 and then the image bombs out.

    I did not have this until I included the cumulative update for Windows 10 1511 - which I need to resolve an issue with AppLocker causing BSODs.

    Tuesday, June 21, 2016 11:13 AM
  • Hello there,

    Have you attempted the following?

    Option Steps A - Force Reboot Client Switch

    1. Open ConfigMgr Console

    2. Navigate to Software Library \ Operating Systems \ Task Sequences

    3. Select the task sequence in question

    4. Select it, right click and select Edit

    5. Select the Setup Windows and ConfigMgr step

    6. Add the /forcereboot switch to the Installation Properties

    7. Click Apply and then Ok

    8. Perform deployment

    Another option would be to place a Reboot right after the Setup Windows and ConfigMgr step, but I do not think it will be as effective or clean.

    Option Steps B – Add Reboot after Setup Windows and ConfigMgr

    1. Open ConfigMgr Console

    2. Navigate to Software Library \ Operating Systems \ Task Sequences

    3. Select the task sequence in question

    4. Select it, right click and select Edit

    5. Select the Setup Windows and ConfigMgr step

    6. Select Add \ General \ Restart Computer

    7. Select Restart Computer

    Thursday, June 23, 2016 9:22 PM
  • We were facing the same issue. However, /forcereboot did not work. On contradictory /noreboot worked for us.. Strange :)

    Tuesday, May 16, 2017 2:21 PM