locked
Sporadic/Unreliable Client Installs RRS feed

  • Question

  • Hello,

    We have roughly 1800 machines.  Just about everything has been imaged but I only have 1200 clients in my console.  I've noticed that when a machine is imaged the chance of the client installing after the deployment varies greatly.  I have the client deployment to also target a variety of systems and it just looks like it doesn't install.  Just yesterday I imaged two machines at the same time - same model, same specs, same image..........one got the client, one did not.  Tried re-imaging that one machine and it continued to not get the client.  It may eventually be successful but not necessarily.  If I look at the ccmsetup log on that machine where it failed I see:

    ==========[ ccmsetup started in process 4448 ]========== ccmsetup 7/16/2012 5:42:16 PM 4452 (0x1164)
    CcmSetup version: 5.0.7711.0000 ccmsetup 7/16/2012 5:42:16 PM 4452 (0x1164)
    Running on OS (6.1.7601). Service Pack (1.0). SuiteMask = 256. Product Type = 1 ccmsetup 7/16/2012 5:42:16 PM 4452 (0x1164)
    Ccmsetup command line: "C:\Windows\ccmcache\2n\ccmsetup.exe" /AutoUpgrade /UpgradePackageVersion:1 ccmsetup 7/16/2012 5:42:16 PM 4452 (0x1164)
    Upgrade code '{252DA259-82CA-4177-B8D0-49C78937BA3E}': product = '{4EE4C49A-BE74-4A04-946A-B1E1248707BD}', installed = 1, version = 5.00.7711.0000 ccmsetup 7/16/2012 5:42:16 PM 4452 (0x1164)
    Loaded command line: "C:\Windows\ccmcache\2n\ccmsetup.exe" /AutoUpgrade /UpgradePackageVersion:1 "/status:632" ccmsetup 7/16/2012 5:42:16 PM 4452 (0x1164)
    Invalid ccmsetup command line: ccmsetup 7/16/2012 5:42:16 PM 4452 (0x1164)
    A Fallback Status Point has not been specified.  Message with STATEID='100' will not be sent. ccmsetup 7/16/2012 5:42:16 PM 4452 (0x1164)
    A Fallback Status Point has not been specified.  Message with STATEID='307' will not be sent. ccmsetup 7/16/2012 5:42:16 PM 4452 (0x1164)
    CcmSetup failed with error code 0x80070006 ccmsetup 7/16/2012 5:42:16 PM 4452 (0x1164)
    ==========[ ccmsetup started in process 6076 ]========== ccmsetup 7/17/2012 11:10:00 AM 2808 (0x0AF8)
    CcmSetup version: 5.0.7711.0000 ccmsetup 7/17/2012 11:10:00 AM 2808 (0x0AF8)
    Running on OS (6.1.7601). Service Pack (1.0). SuiteMask = 256. Product Type = 1 ccmsetup 7/17/2012 11:10:00 AM 2808 (0x0AF8)
    Ccmsetup command line: "C:\Windows\ccmcache\2n\ccmsetup.exe" /AutoUpgrade /UpgradePackageVersion:1 ccmsetup 7/17/2012 11:10:00 AM 2808 (0x0AF8)
    Upgrade code '{252DA259-82CA-4177-B8D0-49C78937BA3E}': product = '{4EE4C49A-BE74-4A04-946A-B1E1248707BD}', installed = 1, version = 5.00.7711.0000 ccmsetup 7/17/2012 11:10:00 AM 2808 (0x0AF8)
    Loaded command line: "C:\Windows\ccmcache\2n\ccmsetup.exe" /AutoUpgrade /UpgradePackageVersion:1 "/status:632" ccmsetup 7/17/2012 11:10:00 AM 2808 (0x0AF8)
    Invalid ccmsetup command line: ccmsetup 7/17/2012 11:10:00 AM 2808 (0x0AF8)
    A Fallback Status Point has not been specified.  Message with STATEID='100' will not be sent. ccmsetup 7/17/2012 11:10:00 AM 2808 (0x0AF8)
    A Fallback Status Point has not been specified.  Message with STATEID='307' will not be sent. ccmsetup 7/17/2012 11:10:00 AM 2808 (0x0AF8)
    CcmSetup failed with error code 0x80070006 ccmsetup 7/17/2012 11:10:00 AM 2808 (0x0AF8)

    When I noticed this over a month ago I was told to re-create the Client Deployment and delete the one we were using.  That seemed to help for a bit but now I'm noticing the issue still exists.  I'm at a loss here.  Is there a way to push it out using the Application method?  I was a bit confused why it was setup utilizing the Package method which I'm told is antiquated and lame.

    Wednesday, August 29, 2012 7:29 PM

All replies

  • How are you deploying ("imaging") the clients then? Using ConfigMgr? If so: the client will be installed automatically during the deployment process (and not after it has finished). The deployment itself would fail if the client wasn't installed during that process ...

    Torsten Meringer | http://www.mssccmfaq.de

    Wednesday, August 29, 2012 8:11 PM
  • I am using SCCM to image.  I have machines that image, are joined to the domain, but do not have the client.
    Wednesday, August 29, 2012 8:38 PM
  • Then they are not finishing the task sequence properly or are stuck in provisioning mode: http://blogs.technet.com/b/configurationmgr/archive/2010/09/13/solution-after-a-configmgr-2007-osd-task-sequence-completes-the-client-may-not-automatically-pull-down-policy.aspx

    Either way, something else is causing an issue annd there is no need to push the client agent.


    Jason | http://blog.configmgrftw.com

    Wednesday, August 29, 2012 8:47 PM
  • Then they are not finishing the task sequence properly or are stuck in provisioning mode: http://blogs.technet.com/b/configurationmgr/archive/2010/09/13/solution-after-a-configmgr-2007-osd-task-sequence-completes-the-client-may-not-automatically-pull-down-policy.aspx

    Either way, something else is causing an issue annd there is no need to push the client agent.


    Jason | http://blog.configmgrftw.com

    It sounds like it is in that mode but the causes given there do not affect my scenario.  I can have the same OSD TS pushed to a handful of machines that are the same model, some get the client, others do not.
    Wednesday, August 29, 2012 8:53 PM
  • I've seen either drivers or hotfixes/updates causing that clients remain stuck in provisioning mode. It's easy if the clients have something in common (and that's up to you to find that out) ... otherwise you have to troubleshoot it yourself: disable all task sequence steps that are not 100% needed and add them back one by one ... it's very time consuming but I am not aware of a better way to find that out.

    Torsten Meringer | http://www.mssccmfaq.de

    Wednesday, August 29, 2012 9:26 PM
  • Noticing another weird thing here.....

    Earlier in the Summer we had a Client Install that wasn't very successful.  I think one of us missed a step on it.  Anyways, we re-did it correctly after that.  When I look at CCMSetup on machines were the client is half-installed, I see time-stamps for activity from July, as well as time-stamps for the recent deployment.  Isn't the OSD TS supposed to do a format of the machine as it's first step?  How could it append onto that log?  Worse yet, why would the install continue to fail because of the old failed client install which is long gone?

    Friday, August 31, 2012 8:34 PM
  • Well, it appears that 7/16 is when I created that image.....so the TS is appending the log that already existed in the image.  On the devices that image correctly with the full client, however, do not append the log but instead appear to completely replace it.  I'm confused...
    Friday, August 31, 2012 9:18 PM
  • I'm going to disable the 'Install Updates' Task from the OSD TS and see if that makes a difference.  It's weird that applying that TS to 30 machines at the same time, same model, I'll get a handful that don't have a full client install and still have the '_SMSTaskSquence' under the C:.

    Some additional Warnings/Errors from the smsts.log time-stamped during this issue:

    Unable to read SMS client cert from environment. Not restoring SMS client cert. OSDSetupHook 9/6/2012 4:50:11 PM 2576 (0x0A10)
    Active request handle is empty, registering with new active request handle. This is expected if the TS was started from a media/PXE. OSDSetupHook 9/6/2012 4:52:25 PM 2576 (0x0A10)
    Error getting system isolation info. Code 8027000C TSManager 9/6/2012 4:53:00 PM 572 (0x023C)
    Remediation failed. Code 8027000C TSManager 9/6/2012 4:53:00 PM 572 (0x023C)
    Remediation failed with error code 8027000C TSManager 9/6/2012 4:53:00 PM 572 (0x023C)


    Thursday, September 6, 2012 10:35 PM
  • Those messages can most likely be safely ignored and also should appear on each client.

    Torsten Meringer | http://www.mssccmfaq.de

    Friday, September 7, 2012 7:48 AM