Ccmsetup.exe Error Code 1
MayJanuary 15, 20132 0 0 0 Today I’ve been playing with my System Center Configuration Manager SP1 lab and came across a very painful little bug. A little searching and I came across this thread on the TechNet forums. Essentially the problem I suddenly started having today, after it sccm 2012 ccmsetup failed with error code 0x80004005 was working fine last week, was that my Config Manager client wasn’t installing through Windows failed to get assigned site from ad. error 0x80004005 Update. It started by giving me a Code 1 message, as below: That 1 update is the Config Man client being deployed through kb2801987 WSUS. So the next thing I did was ran the ccmsetup.exe install from my Primary Site Server. Nothing. So I checked out the ccmsetup.log file that’s in c:\windows\ccmsetup\logs and low and behold spotted the following: That line that says Couldn’t verify ‘c:\windows\ccmsetup\MicrosoftPolicyPlatformSetup.msi’ authenticode signature is a bit of a problem. It turns out that there’s a bit of a bug luckily there is already a hotfix for it and there are some updates on Windows Update already to solve the issue…that said there is still work to do… In order to now install the Config Manager client on a new device we first need a patch in place on that client machine: KB2749655 for anything other than Windows 8 or Server 2012 and KB2756827 for Windows 8 or Server 2012. I tested this on my Windows 8 client by manually running the MSU, then installing the update and the Config Manager client installed like a champ! Now however I need to be able to do OSD on a regular basis, so I just offline serviced my Windows 8 image with DISM to get the job done quickly…here’s what you need to do: Make a directory (I use c:\test) to mount into. Open a command prompt and type dism /mount-wim /wimfile:C:\sources\os\Win8\Sources\install.wim (obviously pointing to the right source wim). Then Dism /Image:C:\test /Add-Package /PackagePath:C:\packages\package1.cab where dism is the name of the msu file for the OS And finally Dism /Unmount-WIM /MountDir:C:\test\offline /Commit Then I updated my distribution points and jobs a good-un. I did the same to my Windows 7 OS image too. Tags Client cm12 config manager configuration manager system center SystemCenter Comments (2) Cancel reply Name * Email * Website Ronnie Calvin says: July 1, 2014 at 10:52 am For Windows8 Tech Support contact on 1-800-935-0537 http://www.computertechsupport.us/ Reply showbox says: January 19, 2016 at 8:35 am Thanks for the great info. I really loved this. I would like to apprentice at the same time as you amend your web site, how could i subscribe for a blog site? For more info on showbox please r
Mode psexec and ccmsetup Author Message levans809 Total Posts : 117 Scores: 4 Reward points : 2580 Joined: 5/4/2005 Status: offline psexec and ccmsetup Wednesday, November 08, 2006 2:13 PM (permalink) 0 i've read a lot of post concerning psexec but has anyone been able to have it return a valid error code when trying to install the sms client. i'm working on a script that will let me know if it actually launched ccmsetup correctly or not and all i get is what looks like the process id. thanks #1 swatret Total Posts : 113 Scores: 2 Reward points : 10230 Joined: 2/26/2002Location: Isle of https://blogs.technet.microsoft.com/simonmay/2013/01/15/error-code1-in-windows-update-0x80004005-in-ccmsetup-log/ Man, UK Status: offline RE: psexec and ccmsetup Wednesday, November 08, 2006 2:25 PM (permalink) 0 Hi, Not quite sure about the "valid error code" you mention - why not just check if ccmsetup is running? strComputer = "." Set objWMIService = GetObject("winmgmts:" _ & "{impersonationLevel=impersonate}!\\" & strComputer & "\root\cimv2") Set colProcesses = objWMIService.ExecQuery _ ("SELECT * FROM Win32_Process WHERE Name = 'ccmsetup.exe'") If colProcesses.Count = 0 Then Wscript.Echo "ccmsetup.exe is not running." http://www.myitforum.com/forums/psexec-and-ccmsetup-m145744.aspx Else Wscript.Echo "ccmsetup.exe is running." End IfHope this helps. Stuart Watret SMS/Packaging Articles SMS Console Additions http://stuartwatret.spaces.live.com #2 levans809 Total Posts : 117 Scores: 4 Reward points : 2580 Joined: 5/4/2005 Status: offline RE: psexec and ccmsetup Wednesday, November 08, 2006 4:23 PM (permalink) 0 swatret... i was thinking about that so thanks for confirming it... i think i'll try that #3 swipe Total Posts : 195 Scores: 2 Reward points : 38420 Joined: 2/17/2006 Status: offline RE: psexec and ccmsetup Thursday, November 09, 2006 10:08 AM (permalink) 0 psexec successfully returns an error code of 1 or 0 for me everytime when I use it to execute ccmsetup. I use it in a small sms installer client tool I created. #4 mwilligenvan670 Total Posts : 4 Scores: 0 Reward points : 0 Joined: 2/7/2006 Status: offline RE: psexec and ccmsetup Friday, November 10, 2006 3:31 AM (permalink) 0 hi, try this strComputer = "." Set objWMIService = GetObject("winmgmts:" _ & "{impersonationLevel=impersonate}!\\" & strComputer & "\root\cimv2") Set colProcesses = objWMIService.ExecQuery _ ("select state from win32_service where name='ccmsetup.exe'") If colProcesses.Count = 0 Then Wscript.Echo "ccmsetup.exe is not running." WScript.Quit(0) Else Wscript.Echo "ccmsetup.exe is running." WScript.Quit(1603) End If psexec successfully returns an error code of1603--> CCMsetup.e
PKI Rants Security USMT Windows KMS Group Policy 3rd Party Tools Conferences External Articles Contact Client Startup Script Version 1.7.5 (Sep 6, 2015)Download What is a startup script? A startup script runs during a system’s initial boot up; it is applied http://blog.configmgrftw.com/configmgr-client-startup-script/ to a system using a group policy. Startup scripts run under the context of the local computer’s SYSTEM account. Why use a Startup Script for ConfigMgr? To check configuration settings and the state of services that the ConfigMgr client agent depends on for successful operation as well as install the client agent if it is not install or functioning properly. Why use a Startup Script instead one of the built-in error code methods to install the client agent? A startup script avoids most common DNS issues, firewall issues, and other connectivity issues that are common when a central system attempts to touch all of the clients. It also adds the health/configuration checks mentioned above to check for (and correct some) dependencies as well as report on systems still having issues. Some FAQs Does this script work with ConfigMgr 2012? Yes. The ccmsetup.exe error code set up process between 2007 and 2012 is nearly identical. Make sure you are aware of the different public properties available though as there are a few changes; e.g., SMSLP is no longer valid in 2012 because there is no formal SLP role anymore. Does this script fix WMI? No. WMI can break in so many different ways that there's no way to build a complete script to fix WMI. Instead, version 1.53 includes the ability to call an external script to do this for you. There are a handful of WMI check/fix scripts available including the one I tested with: WMIDiag (see the included documentation for more info on that). Is this a comprehensive client *health* script? Comprehensive? No way. I would consider it part of an overall client health strategy, but similar to WMI, there are so many different things that can go wrong with clients that it wouldn't be impossible to keep up. This script is flexible enough to add many checks and fixes for things that are often root client health issues. There's no real reporting or data summarization either. Does this replace ccmeval in ConfigMgr 2012 or does ccmeval in ConfigMgr 2012 replace the need for this script? No. ccmeval is intended only