[Last Call] Learn how to a build a cloud-first strategyRegister Now


SCCM SP2 Client

Posted on 2010-01-06
Medium Priority
Last Modified: 2013-11-21
Still can not install SCCM SP2 client with Right Click tools, even after the client on the machine that is running the SCCM console has been updated.  I found that I needed to publish the client to the SUP but it doesn't seem to be publishing

SMS trace error:

Download complete.      ccmsetup      1/6/2010 4:41:55 PM      3540 (0x0DD4)
Successfully created the ccmsetup service      ccmsetup      1/6/2010 4:41:55 PM      3540 (0x0DD4)
==========[ ccmsetup started in process 3256 ]==========      ccmsetup      1/6/2010 4:41:56 PM      4048 (0x0FD0)
Version: 4.0.5931.0000      ccmsetup      1/6/2010 4:41:56 PM      4048 (0x0FD0)
Command line parameters for ccmsetup have been specified.  No registry lookup for command line parameters is required.      ccmsetup      1/6/2010 4:41:56 PM      4048 (0x0FD0)
Command line: "C:\WINDOWS\system32\ccmsetup\ccmsetup.exe" /runservice  /mp:SCCMA01  SMSSITECODE=A01      ccmsetup      1/6/2010 4:41:56 PM      4048 (0x0FD0)
CCMHTTPPORT:    80      ccmsetup      1/6/2010 4:41:56 PM      4048 (0x0FD0)
CCMHTTPSPORT:    443      ccmsetup      1/6/2010 4:41:56 PM      4048 (0x0FD0)
CCMHTTPSSTATE:    2147483648      ccmsetup      1/6/2010 4:41:56 PM      4048 (0x0FD0)
CCMHTTPSCERTNAME:          ccmsetup      1/6/2010 4:41:56 PM      4048 (0x0FD0)
FSP:          ccmsetup      1/6/2010 4:41:56 PM      4048 (0x0FD0)
Config file:            ccmsetup      1/6/2010 4:41:56 PM      4048 (0x0FD0)
Retry time:       10 minute(s)      ccmsetup      1/6/2010 4:41:56 PM      4048 (0x0FD0)
MSI log file:           ccmsetup      1/6/2010 4:41:56 PM      4048 (0x0FD0)
MSI properties:    SMSSITECODE="A01" CCMHTTPPORT="80" CCMHTTPSPORT="443"      ccmsetup      1/6/2010 4:41:56 PM      4048 (0x0FD0)
Source List:      ccmsetup      1/6/2010 4:41:56 PM      4048 (0x0FD0)
MPs:      ccmsetup      1/6/2010 4:41:56 PM      4048 (0x0FD0)
                  SCCMA01      ccmsetup      1/6/2010 4:41:56 PM      4048 (0x0FD0)
Updated security on object C:\WINDOWS\system32\ccmsetup\.      ccmsetup      1/6/2010 4:41:56 PM      4048 (0x0FD0)
A Fallback Status Point has not been specified.  Message with STATEID='100' will not be sent.      ccmsetup      1/6/2010 4:41:56 PM      4048 (0x0FD0)
Successfully started the ccmsetup service      ccmsetup      1/6/2010 4:41:56 PM      3540 (0x0DD4)
Deleted file C:\WINDOWS\system32\ccmsetup\ccmsetup.exe.download      ccmsetup      1/6/2010 4:41:56 PM      3540 (0x0DD4)
Running as user "SYSTEM"      ccmsetup      1/6/2010 4:41:56 PM      3156 (0x0C54)
Detected 7067 MB free disk space on system drive.      ccmsetup      1/6/2010 4:41:56 PM      3156 (0x0C54)
DetectWindowsEmbeddedFBWF() Detecting OS Version      ccmsetup      1/6/2010 4:41:56 PM      3156 (0x0C54)
Client OS is not Windows XP Embedded      ccmsetup      1/6/2010 4:41:56 PM      3156 (0x0C54)
Waiting for existing instances of ccmsetup to exit.      ccmsetup      1/6/2010 4:41:56 PM      3156 (0x0C54)
All other instances of ccmsetup have completed.      ccmsetup      1/6/2010 4:41:56 PM      3156 (0x0C54)
Ccmsetup is being restarted due to an administrative action. Installation files will be reset and downloaded again.      ccmsetup      1/6/2010 4:41:56 PM      3156 (0x0C54)
Deleted file C:\WINDOWS\system32\ccmsetup\client.msi      ccmsetup      1/6/2010 4:41:56 PM      3156 (0x0C54)
Successfully ran BITS check.      ccmsetup      1/6/2010 4:41:56 PM      3156 (0x0C54)
SSL Registry key Software\Microsoft\CCM not found, assuming Client SSL is disabled.      ccmsetup      1/6/2010 4:41:56 PM      3156 (0x0C54)
Certificate doesn't have EKU, meaning good for all usages.      ccmsetup      1/6/2010 4:41:56 PM      3156 (0x0C54)
Select first cert flag is set, choosing the first certificate valid for ConfigMgr usage.      ccmsetup      1/6/2010 4:41:56 PM      3156 (0x0C54)
Verified file 'C:\WINDOWS\system32\ccmsetup\ccmsetup.cab' is MS signed.      ccmsetup      1/6/2010 4:41:56 PM      3156 (0x0C54)
Successfully extracted manifest file C:\WINDOWS\system32\ccmsetup\ccmsetup.xml from file C:\WINDOWS\system32\ccmsetup\ccmsetup.cab.      ccmsetup      1/6/2010 4:41:56 PM      3156 (0x0C54)
Loading manifest file: C:\WINDOWS\system32\ccmsetup\ccmsetup.xml      ccmsetup      1/6/2010 4:41:56 PM      3156 (0x0C54)
Successfully loaded ccmsetup manifest file.      ccmsetup      1/6/2010 4:41:56 PM      3156 (0x0C54)
Couldn't get directory list for directory 'http://SCCMA01/CCM_Client/ClientPatch'.  This directory may not exist.      ccmsetup      1/6/2010 4:41:56 PM      3156 (0x0C54)
Adding file 'http://SCCMA01:80/CCM_Client/i386/client.msi' to BITS job, saving as 'C:\WINDOWS\system32\ccmsetup\client.msi'.      ccmsetup      1/6/2010 4:41:56 PM      3156 (0x0C54)
Couldn't get directory list for directory 'http://SCCMA01/CCM_Client/i386/00000409'.  This directory may not exist.      ccmsetup      1/6/2010 4:41:56 PM      3156 (0x0C54)
Starting BITS download for client deployment files.      ccmsetup      1/6/2010 4:41:56 PM      3156 (0x0C54)
Download Update: Connecting to the server.      ccmsetup      1/6/2010 4:41:57 PM      3156 (0x0C54)
Successfully completed BITS download for client deployment files.      ccmsetup      1/6/2010 4:42:01 PM      3156 (0x0C54)
Successfully downloaded client files via BITS.      ccmsetup      1/6/2010 4:42:02 PM      3156 (0x0C54)
Updated security on object C:\WINDOWS\system32\ccmsetup\.      ccmsetup      1/6/2010 4:42:02 PM      3156 (0x0C54)
An MP does not exist on this machine.      ccmsetup      1/6/2010 4:42:02 PM      3156 (0x0C54)
No client is currently installed.      ccmsetup      1/6/2010 4:42:02 PM      3156 (0x0C54)
Installing version 4.00.6487.2000 of the client with product code {2609EDF1-34C4-4B03-B634-55F3B3BC4931}      ccmsetup      1/6/2010 4:42:02 PM      3156 (0x0C54)
MSI PROPERTIES are  SMSSITECODE="A01" CCMHTTPPORT="80" CCMHTTPSPORT="443" INSTALL=ALL      ccmsetup      1/6/2010 4:42:02 PM      3156 (0x0C54)
There are no certificate(s) that meet the criteria.      ccmsetup      1/6/2010 4:42:02 PM      3156 (0x0C54)
Failed in GetCertificate(...): 0x80040281
      ccmsetup      1/6/2010 4:42:02 PM      3156 (0x0C54)
File 'C:\WINDOWS\system32\ccmsetup\{4CD82FBB-0AFC-4864-A089-15364DF5F14B}\client.msi' doesn't have a valid digital signature.      ccmsetup      1/6/2010 4:42:02 PM      3156 (0x0C54)

Question by:m1721c
LVL 10

Accepted Solution

JonLambert earned 2000 total points
ID: 26195226
The right click tools utilise a local copy of ccmsetup that isn't updated when you update to SP2 (In C:\Windows, c:\Windows\System32 or another subdirectory under Windows, depending on which right click tools, and what version of those tools).  Try locating that CCMSETUP and replacing it with the one from the SP2 client.

Author Comment

ID: 26195638
I think I found it with your help.  I am using Client Tools that I found on MYITFORUM, I had to replace the CCMsetup with the newer one.  It was located at C:\WINDOWS\SCCMTools.  I will try this on another SCCM admins machine to verify it is working

Featured Post

Free Tool: IP Lookup

Get more info about an IP address or domain name, such as organization, abuse contacts and geolocation.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

The question has been asked on multiple occasions as to how best to do printing in a remote desktop or terminal services environment.   It seems that this particular question has plagued several people and most especially as Terminal Services, as…
Issue: One Windows 2008 R2 64bit server on the network unable to connect to a buffalo Device (Linkstation) with firmware version 1.56. There are a total of four servers on the network this being one of them. Troubleshooting Steps: Connect via h…
This lesson discusses how to use a Mainform + Subforms in Microsoft Access to find and enter data for payments on orders. The sample data comes from a custom shop that builds and sells movable storage structures that are delivered to your property. …
Whether it be Exchange Server Crash Issues, Dirty Shutdown Errors or Failed to mount error, Stellar Phoenix Mailbox Exchange Recovery has always got your back. With the help of its easy to understand user interface and 3 simple steps recovery proced…
Suggested Courses

829 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question