none
client.msi doesn't have a valid digital signature - Older version of ccmsetup.exe in the windows dir RRS feed

  • Question

  • I have found a lot of posts about this. At this point I think it's a cert or version issue but I am lost. I have a ton of machines with Client=No, about a quarter of the DRs. A majority do have the client installed that report No. I was looking at a couple, one of which has the client isntalled but isnt even reporting a DR. I mistakenly looked this machine (024) and found one with the client installed and the CCMsetup.log concurs but it doesn't report. Another (022) gives me the error of client.msi doesn't have a valid digital signature. I will post the log at the bottom.

    Right click and using psexec to push the client (022) fails. On the server, from where I also run psexec to manually install, the only versions of ccmsetup.exe are 4.0.6487.2000. On machine 022 in the ccmsetup folder, version 4.0.6221.1000 is there. If I delete the ccmsetup folder and try to install again, it still has the old 6221 version which I am assuming is the problem. Where does it get this old version from? On machne 024, I install using the same methods and version 6487 is there...

    Also, both ccmsetup.exe have expired certs. 6481 valid until 1-2010. Do I not have the most recent version?? How relevent is this?

    OK, so working on this as I write, I found an older version of ccmsetup.exe in the Windows dir of machine 022... I replaced it with the newer, and ran the same install script again via psexec again and it works now. Successful install! So, why or how did that older version show up in the Windows dir?? I have a feeling I am going to find alot of these... And why is the install using that file in the windows dir?

    Thoughts????

     

    This is the machine (022) getting the error:

    8/13/2010 10:52:35 AM ==========[ ccmsetup started in process 1104 ]==========
    8/13/2010 10:52:35 AM Version: 4.0.6221.1000
    8/13/2010 10:52:35 AM Command line parameters for ccmsetup have been specified.  No registry lookup for command line parameters is required.
    8/13/2010 10:52:35 AM Command line: "ccmsetup.exe" /mp:chisms01 smssitecode=FCO fsp=chisms02
    8/13/2010 10:52:35 AM User credentials are not required to access installation files. ccmsetup will be executed in service-only mode.
    8/13/2010 10:52:35 AM Updated security on object C:\WINDOWS\system32\ccmsetup\.
    8/13/2010 10:52:35 AM A Fallback Status Point has not been specified.  Message with STATEID='100' will not be sent.
    8/13/2010 10:52:35 AM ccmsetup service is stopped.
    8/13/2010 10:52:40 AM Successfully deleted the ccmsetup service
    8/13/2010 10:52:40 AM Ccmsetup is not registered in the Run key
    8/13/2010 10:52:41 AM Downloading file C:\WINDOWS\ccmsetup.exe
    8/13/2010 10:52:41 AM Downloading C:\WINDOWS\ccmsetup.exe to C:\WINDOWS\system32\ccmsetup\ccmsetup.exe
    8/13/2010 10:52:41 AM File download 10% complete (65536 of 611360 bytes).
    8/13/2010 10:52:41 AM File download 21% complete (131072 of 611360 bytes).
    8/13/2010 10:52:41 AM File download 32% complete (196608 of 611360 bytes).
    8/13/2010 10:52:41 AM File download 42% complete (262144 of 611360 bytes).
    8/13/2010 10:52:41 AM File download 53% complete (327680 of 611360 bytes).
    8/13/2010 10:52:41 AM File download 64% complete (393216 of 611360 bytes).
    8/13/2010 10:52:41 AM File download 75% complete (458752 of 611360 bytes).
    8/13/2010 10:52:41 AM File download 85% complete (524288 of 611360 bytes).
    8/13/2010 10:52:41 AM File download 96% complete (589824 of 611360 bytes).
    8/13/2010 10:52:41 AM File download 100% complete (611360 of 611360 bytes).
    8/13/2010 10:52:41 AM Download complete.
    8/13/2010 10:52:42 AM Successfully created the ccmsetup service
    8/13/2010 10:52:42 AM ==========[ ccmsetup started in process 4076 ]==========
    8/13/2010 10:52:42 AM Version: 4.0.6221.1000
    8/13/2010 10:52:42 AM Command line parameters for ccmsetup have been specified.  No registry lookup for command line parameters is required.
    8/13/2010 10:52:42 AM Command line: "C:\WINDOWS\system32\ccmsetup\ccmsetup.exe" /runservice  /mp:chisms01 smssitecode=FCO fsp=chisms02
    8/13/2010 10:52:42 AM CCMHTTPPORT:    80
    8/13/2010 10:52:42 AM CCMHTTPSPORT:    443
    8/13/2010 10:52:42 AM CCMHTTPSSTATE:    2147483648
    8/13/2010 10:52:42 AM CCMHTTPSCERTNAME:   
    8/13/2010 10:52:42 AM FSP:    chisms02
    8/13/2010 10:52:42 AM Config file:     
    8/13/2010 10:52:42 AM Retry time:       10 minute(s)
    8/13/2010 10:52:42 AM MSI log file:    
    8/13/2010 10:52:42 AM MSI properties:    SMSSITECODE="FCO" FSP="chisms02" CCMHTTPPORT="80" CCMHTTPSPORT="443"
    8/13/2010 10:52:42 AM Source List:
    8/13/2010 10:52:42 AM MPs:
    8/13/2010 10:52:42 AM                   chisms01
    8/13/2010 10:52:42 AM Updated security on object C:\WINDOWS\system32\ccmsetup\.
    8/13/2010 10:52:42 AM Sending Fallback Status Point message, STATEID='100'.
    8/13/2010 10:52:42 AM State message with TopicType 800 and TopicId {98BA0016-F32D-4D19-8310-0584AE1FB364} has been sent to the FSP
    8/13/2010 10:52:42 AM Running as user "SYSTEM"
    8/13/2010 10:52:42 AM Successfully started the ccmsetup service
    8/13/2010 10:52:42 AM Detected 65597 MB free disk space on system drive.
    8/13/2010 10:52:42 AM DetectWindowsEmbeddedFBWF() Detecting OS Version
    8/13/2010 10:52:42 AM Client OS is not Windows XP Embedded
    8/13/2010 10:52:42 AM Waiting for existing instances of ccmsetup to exit.
    8/13/2010 10:52:42 AM Deleted file C:\WINDOWS\system32\ccmsetup\ccmsetup.exe.download
    8/13/2010 10:52:42 AM All other instances of ccmsetup have completed.
    8/13/2010 10:52:42 AM Ccmsetup is being restarted due to an administrative action. Installation files will be reset and downloaded again.
    8/13/2010 10:52:42 AM Successfully ran BITS check.
    8/13/2010 10:52:42 AM SSL Registry key Software\Microsoft\CCM not found, assuming Client SSL is disabled.
    8/13/2010 10:52:42 AM Certificate doesn't have EKU, meaning good for all usages.
    8/13/2010 10:52:42 AM Verified file 'C:\WINDOWS\system32\ccmsetup\ccmsetup.cab' is MS signed.
    8/13/2010 10:52:42 AM Successfully extracted manifest file C:\WINDOWS\system32\ccmsetup\ccmsetup.xml from file C:\WINDOWS\system32\ccmsetup\ccmsetup.cab.
    8/13/2010 10:52:42 AM Loading manifest file: C:\WINDOWS\system32\ccmsetup\ccmsetup.xml
    8/13/2010 10:52:42 AM Successfully loaded ccmsetup manifest file.
    8/13/2010 10:52:43 AM Couldn't get directory list for directory 'http://chisms01/CCM_Client/ClientPatch'.  This directory may not exist.
    8/13/2010 10:52:43 AM Adding file 'http://chisms01:80/CCM_Client/i386/client.msi' to BITS job, saving as 'C:\WINDOWS\system32\ccmsetup\client.msi'.
    8/13/2010 10:52:43 AM Starting BITS download for client deployment files.
    8/13/2010 10:52:44 AM Download Update: 3311074 out of 17847296 bytes transferred.
    8/13/2010 10:52:46 AM Successfully completed BITS download for client deployment files.
    8/13/2010 10:52:46 AM Successfully downloaded client files via BITS.
    8/13/2010 10:52:46 AM Updated security on object C:\WINDOWS\system32\ccmsetup\.
    8/13/2010 10:52:46 AM An MP does not exist on this machine.
    8/13/2010 10:52:46 AM No client is currently installed.
    8/13/2010 10:52:47 AM Installing version 4.00.6487.2000 of the client with product code {2609EDF1-34C4-4B03-B634-55F3B3BC4931}
    8/13/2010 10:52:47 AM MSI PROPERTIES are  SMSSITECODE="FCO" FSP="chisms02" CCMHTTPPORT="80" CCMHTTPSPORT="443" INSTALL=ALL
    8/13/2010 10:52:47 AM There are no certificate(s) that meet the criteria.
    8/13/2010 10:52:47 AM Failed in GetCertificate(...): 0x80040281

    8/13/2010 10:52:47 AM File 'C:\WINDOWS\system32\ccmsetup\{4CD82FBB-0AFC-4864-A089-15364DF5F14B}\client.msi' doesn't have a valid digital signature.
    8/13/2010 10:52:47 AM Sending Fallback Status Point message, STATEID='316'.
    8/13/2010 10:52:47 AM State message with TopicType 800 and TopicId {19D15A37-1170-422D-806D-7057D35B333A} has been sent to the FSP

    Friday, August 13, 2010 4:17 PM

Answers

  • Hi,

    This issue could be caused by:

    1. The installed files was corrupted. Please check hash code on the problem computers.
    2. Wrong password on the SCCM Netowrk access account. Please check your account and password.
    3. Permission issue. Please try to add  SCCMADMIN account to "Allow this machine to access from network" under local security policy -> user rights assignment

    Hope it helps.


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    • Marked as answer by Robinson Zhang Friday, September 3, 2010 2:25 AM
    Friday, August 20, 2010 8:34 AM