locked
Client upgrade package deployment error (yet successfull) RRS feed

  • General discussion

  • Hello,

    I've been deploying my-self created package of a upgrade installation file I have found in the installation directory of SCCM 2012.

    I have run a test deployment on a test collection on my two colleagues and the deployment showed 100% compilance with no error and installation went great.

    So, I thought that it's ok to deploy it on more populated collection (Office computers only) and see what happens.

    What actually happened is that after one day later there was 0% compilance on that deployment and every installation seem to have failed with ID 10021 stating "Program failed (unexpected restart)" so I assumed the installation failed and the upgrade wasn't installed. Yet, I have checked some of the workstations and the client version number and it matched the R2 version. (which we are using)

    Can anyone explain this to me?

    The file used for the test upgrade and the pilot upgrade is located here:

    ...\ConfigMgr\ClientUpgrade\ccmsetup.exe (1,577 KB)

    it does the trick when launched manualy and on a small collection, but on the large one, it "fails" the way I have described above.

    I don't get it...


    The IT guys from LukOIL


    • Edited by Jiri S Wednesday, January 15, 2014 4:09 PM grammar
    Wednesday, January 15, 2014 4:06 PM

All replies