Asked by:
Client upgrade package deployment error (yet successfull)

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
-
Are you just running CCMSETUP.exe with no switches?
Wednesday, January 15, 2014 4:10 PM -
Yes I am. No switches
The IT guys from LukOIL
- Edited by Jiri S Wednesday, January 15, 2014 4:12 PM info
Wednesday, January 15, 2014 4:11 PM -
the answer from the below thread will answer your question
Kindly mark as answer/Vote as helpful if a reply from anybody helped you in this forum. Delphin
Wednesday, January 15, 2014 4:17 PM -
the answer from the below thread will answer your question
Kindly mark as answer/Vote as helpful if a reply from anybody helped you in this forum. Delphin
Now I understand!
Thank you all for your time!
The IT guys from LukOIL
Thursday, January 16, 2014 8:01 AM -
Ran into the same problem in our environment while upgrading the clients to SCCM 2012 R2 SP1 CU1 the clients would upgrade successfully, but the site would report that the clients failed with an error ID10021 as well. We ended up running a simple batch file with the CCMSETUP.EXE command line followed by a "powershell start-sleep 300" command did the trick and the clients reported in as successful.
CCMSETUP.EXE /noservice /source:.\ SMSSITECODE=XYZ SMSMP=MP01.testlab.loc FSP=FSP01.testlab.loc DISABLESITEOPT=TRUE DISABLECACHEOPT=TRUE
powershell start-sleep 300
- Dave
Friday, October 2, 2015 5:29 PM