ccm.log, ccmsetup.log, client.msi.log: which one has the truth?

Solvedclientconfigmgrsccm3 replies 路 212 views 路 started

Accepted solution

by Arjun E.Jump to the reply

For internet-based or workgroup devices, client push wont work at all. Use a manual install with teh correct parameters, and for HTTPS or Enhanced HTTP, make suree the device trusts the site certificates. fingers crossed 馃

lol

  1. ok so odd one. software update-based installation reports success on the site server, but the devices never show a client:

    Log viewer - C:\Windows\ccmsetup\Logs\ccmsetup.log

    Log viewer - C:\Windows\ccmsetup\Logs\ccmsetup.log
    Running as user "SYSTEM"
    Detected 120318 MB free disk space on system drive.
    Checking Write Filter Status.
    Downloading file client.msi
    Download complete.
    Running installation package
      Package:     C:\WINDOWS\ccmsetup\client.msi
      Log:         C:\WINDOWS\ccmsetup\Logs\client.msi.log
    MSI: Setup was unable to compile the file DiscoveryStatus.mof.
    MSI: The error code is 80041002
    Installation failed with error code 1603
    A Fallback Status Point has not been specified.
    

    on one machine i found ccmsetup.log ending with 0x87d00227. is there a checklist Im missing?

    im not even sure whether teh push really happened or whether the device just ignored it. id love some pointers on which logs to correlate between the site server and the clinet, and in what order. seriously need help here 馃槶

    1
  2. hmmm what does ccm.log on teh site server show for one of the failed devices? ?

    1 0 helpful
  3. For internet-based or workgroup devices, client push wont work at all. Use a manual install with teh correct parameters, and for HTTPS or Enhanced HTTP, make suree the device trusts the site certificates. fingers crossed 馃

    lol

    0 8 helpful

Reply to this topic

Sign in or create an account to reply.