none
Missing SCCM client after OSD

    Question

  • I have a fully working OSD PXE environment and when I complete the build i am left with a fully functional pc including the SCCM client.
    however when I rebuild an existing pc that features the SCCM client, when it finishes the SCCM client is not present.
    I have a domain based GPO to install the SCCM client and I believe this is causing the issue.
    I have no idea why this affects rebuilds and not new builds?

    any ideas?
    Wednesday, April 22, 2009 12:30 PM

All replies

  • I have a domain based GPO to install the SCCM client and I believe this is causing the issue.

    I have no idea why this affects rebuilds and not new builds?

    any ideas?

    This is probally because your refresh scenario does not contain the step " Setup windows & config Mgr " .We need more details on this scenario , because when it is a wim image , naybe you just need to send a package to it with the sccm client installed .

    Please define your "when I rebuild an existing pc that features the SCCM client" , because you could do many things to accomplish a refresh .
    Hope it helps , Kenny Buntinx www.scug.be/blogs/sccm/
    Wednesday, April 22, 2009 6:14 PM
  • Thanks for the reply Kenny,
    just to clarify what i meant is that the computer that I am rebuilding was originally created from a ghosted image. the SCCM client was then installed onto it as part of the GPO based deployment. for some reason the operating system has an issue and I have decided to rebuild it.
    I am rebuilding it using EXACTLY THE SAME Task sequence as I am using for new builds.
    this task sequence includes the step "Setup windows and ConfigMgr" and I am fairly certain that this works, if not why does it work on new builds?

    I think there must be some kind of issue in the way the GPO is applying on the rebuilds, is it possible that the SMS client Bootstrap that is deployed via GPO is uninstalling the existing SCCM client that was installed via "Setup windows and ConfigMgr" as part of the OSD. If so do you know where I would look to see if this is the case?

    Thanks
    Thursday, April 23, 2009 7:51 AM
  • Question 1: Is there any version difference in to the client in the image or been used via GPO ? 

    Question 2 : Do a quick test and deploy the machine into an seperate OU where client install isn't performed via GPO . See if that works ...


    Hope it helps , Kenny Buntinx www.scug.be/blogs/sccm/
    Thursday, April 23, 2009 6:39 PM
  • I have some more information for you.
    I believe that part of the issue is related the the GPO based deployment.
    I have noticed that a lot of newly ghosted clients are not fully installing the SCCM client, they are added to the domain and Group Policy installs the SCCM client bootstrap, but at this point it also installs some other software. because Group Policy is using the Windows Installer, the bootstrap cannot use it to install the SCCM client. the logs for ccmsetup say that it will retry in 10 minutes but this never happens.
    to resolve this I have written a vbs script to detect if the client is installed, and if not re run the ccmsetup.
    I believe this will solve the issue, however it does not answer why the rebuilds dont receive the SCCM client as part of the OSD "Setup windows and ConfigMgr"?

    guess I need to go through some logs etc.
    Monday, May 11, 2009 9:36 AM
  • I'm having the same exact problem.  I have a task sequence to install an image which doesn't have the client included and when the task sequence runs for a bare metal install the client and state restore actions operate correctly; however when I use the same task sequence to refresh and existing sccm client, the process does not run the setup windows and config manager action and then stops, leaving the system with no sccm client installed and none of the state restore actions are performed
    Tuesday, December 29, 2009 10:56 AM
  • Does a new build initially go into a designated OU that does not have the GPO applied, and then moved to a production after the build? Is a rebuilt machine left in a production OU during the build?

    Tuesday, December 29, 2009 12:03 PM
  • both new builds and rebuilds are accessing the Computers Folder (OU) and the gpo to install the SCCM client is not applied to this OU.
    Tuesday, December 29, 2009 1:44 PM
  • Did you add the option to "capture machine settings" prior to rebooting to PE to complete the image?
    Scott Gill
    SCCM Consultant
    Tuesday, December 29, 2009 5:43 PM
  • Where is the "capture machine settings"?  What phase of the task sequence?  I'm not seeing this option.  Would this option be included by default in the MDT 2010 / SP2 Task Sequence Wizard?
    Tuesday, December 29, 2009 8:33 PM
  • It's an option built into the TS engine in SCCM (MDT not necessary).  I don't remember exactly where its at in the the add menu, but it's in there.  It would need to be added to the TS prior to Reboot into PE.
    Scott Gill
    SCCM Consultant
    Tuesday, December 29, 2009 9:01 PM
  • Turns out the problem was due to KB974571 included in the Windows XP w/SP3 image.  Once I uninstalled this after Sysprep, the sccm client installs and continues on the process  I had to bite the bullet and call Microsoft on this one and the engineer worked with the USMT on the fix.  See his comments:

    """Can you check something for me? Do you know if you have KB974571 as part of the XP reference image? If so, this may be a known issue. If it’s in the image, would you remove the patch and recreate the image? You can then install 974571 as the very last step in the TS using for example an install software step. Apparently we’ve seen very similar symptoms a few times now and this resolves.

     

    974571  MS09-056: Vulnerabilities in CryptoAPI could allow spoofing

    http://support.microsoft.com/default.aspx?scid=kb;EN-US;974571

    """
    Thursday, January 07, 2010 2:55 AM
  • Ahh, interesting... I do seem to recall a patch conflicting with USMT (don't remember if this was it or not)... But I always try to avoid putting any patches on the base image and just use the update system to install the patches post-deployment (as the very last step in the TS).  That's just preference for me b/c patches are replaced by newer ones all the time so you never know when some patch captured in the base image will be obsolete and have no point being in the base image anymore.
    Scott Gill
    SCCM Consultant
    Thursday, January 07, 2010 4:48 PM
  • Try giving a Pause after the installation of SCCM, so that it has fair enough time to configure itself.
    Friday, October 29, 2010 7:57 AM