locked
Alternating Obsolete / Not Obsolete RRS feed

  • Question

  • We are currently working through the process of building some new images which have the SCCM 2012 client inside of them. We had previously done this without issue using SCCM 2007 utilizing the procedure of stopping the SMS Agent Host, deleting SMSCFG.ini and running ccmdelcert prior to sysprepping and sealing.

    The issue I am encountering at the moment is that of the first two devices that have been imaged via this method, they appear to fight back and forth, forcing one to be obsolete. If I delete them out of the admin console and force a re-discover they typically reappear with the one which was not previously obsolete now showing as obsolete. In 2007 it was indicative of a duplicate GUID, however they have two unique GUIDs between the two.

    Any thoughts on what else could be causing this? Is this process no longer valid with 2012?

    Thanks in advance.

    Wednesday, August 27, 2014 7:28 PM

Answers

  • You need to contact Microsoft CSS on this. They may ultimately identify the problem being with the hardware, but that's the place to start.

    Jason | http://blog.configmgrftw.com | @jasonsandys

    • Proposed as answer by Garth JonesMVP Monday, March 23, 2015 2:05 AM
    • Marked as answer by Garth JonesMVP Wednesday, February 3, 2016 5:44 PM
    Friday, August 29, 2014 2:20 PM

All replies

  • Here's how to prepare the computer for imaging: http://technet.microsoft.com/en-us/library/gg712298.aspx

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

    Wednesday, August 27, 2014 7:31 PM
  • Torsten,

    That actually states to do exactly what I said our process already involves (stop service, del cert).

    Any thoughts on what else could be making it think these devices are one in the same?

    Wednesday, August 27, 2014 7:47 PM
  • I don't have an answer but I do have a solution: don't put the agent in your image or use a build and capture task sequence in ConfigMgr and this will be automatically done for you and you'll save lots of time by having a repeatable and fully automated image build process instead of wasting your time clicking the OK button to build and image.

    Jason | http://blog.configmgrftw.com | @jasonsandys

    Wednesday, August 27, 2014 8:30 PM
  • We're in a unique situation where this is being done for point of sale equipment at remote locations around the country. Unfortunately the circuits are not of any caliber where we can do any sort of OSD via SCCM.

    Thursday, August 28, 2014 11:57 AM
  • It's looking as though this may be the result of identical Hardware IDs, which doesn't seem like it should be possible on different devices?

    2:69FBDC33ACE8C9106EA68AAAECF635093982811E

    Although I can't find a specific way of how this is calculated, http://support.microsoft.com/kb/837374 states that it is a combination of 10 computer properties (converted to hash values), and subsequently turned in to a unique identifier.

    I see no possible way of being able to regenerate this ID. It seems that as a function/security feature of SCCM it assumes that if that if a new device checks in with the same hardware ID, the assumption is that the old device is gone, marking it as obsolete.

    Not sure if the way to go is to contact Microsoft, or contact the hardware vendor.

    Friday, August 29, 2014 2:17 PM
  • You need to contact Microsoft CSS on this. They may ultimately identify the problem being with the hardware, but that's the place to start.

    Jason | http://blog.configmgrftw.com | @jasonsandys

    • Proposed as answer by Garth JonesMVP Monday, March 23, 2015 2:05 AM
    • Marked as answer by Garth JonesMVP Wednesday, February 3, 2016 5:44 PM
    Friday, August 29, 2014 2:20 PM