Clients removed from collections after client registers with server RRS feed

  • Question

  • Currently using Config manager 2012 and clients are running windows 7 enterprise 64bit. 

    I am imaging 140 new computers for the teachers at a school. The new computers have been created in AD via a powershell script and imported into config manager. Staff computers have been allocated into collections to specify their software. Within these collections there are collection variables assigned that are used within the task sequence to determine if software in installed or not. 

    when we start imaging we enter the computer name that matches the name within Config manager.

    Problem: Whenever the new computers are imaged they do not recognize the collection variables set so the software does not install. Then once the client registers with the config manager server it removes it is removed from all collection that it was previously allocated.  

    Can clients that do not have an active status hold a collection variable?

    Why are they being removed from collections when the Config manager client registers with the server?

    How can this problem be resolved without imaging the same computer twice and forcing a refresh of the collection memberships??

    Can you force a client heartbeat discovery during a task sequence before software is installed??

    Wednesday, October 17, 2012 4:18 AM


All replies

  • How did you import the machines into SCCM - AD machine discovery?

    I assume you are using Unknown computer support and specifying the name of the machine at the beginning of the task sequence?

    Wednesday, October 17, 2012 10:54 AM
  • That's right,

    Machine discovery was used to pull them From AD into Config Manager.

    Unknown computer support has been turned on for all distribution points. 

    The machines will image fine they just don't pick up the collection variables.

    Current process is:

    1. Image the machines with a blank windows

    2. Check to see if the client has registered with SCCM.

    3. Refresh the collections so the computer account will return to the collection.

    4. Image the machine with the full image. 

    This i just way to much manual handling and way too slow.


    Clinton Mohoupt

    Wednesday, October 17, 2012 11:01 PM
  • New systems identify themselves during the OSD process using either (or both) their MAC Address or SMBIOS GUID. AD knows nothing about either of these so a simple discovery to create them as resources in ConfigMgr creates resource without either of these identifiers either. Thus, when the new systems its OSD process, there is no way for it to find and use the resource created from an AD Discovery.

    There are a handful of things you can do including using a GUI to prompt for these values at the beginning of the TS or importing the computers directly into ConfigMgr using the Import Computer feature which requires that you supply the MAC Address or SMSBIOS GUID.

    Jason | http://blog.configmgrftw.com

    Thursday, October 18, 2012 1:23 AM
  • As Jason says, when the computer account is discovered from AD you won't have the unique identifier required for OSD (MAC or SMSBIOS GUID). So if I understand correctly when you build a machine you will actually create another device record which will contain the details obtained from the physical machine. This will co-exist with the AD discovered record as there are no details in the AD discovered record which tie it to the physical machine.

    When you perform the build you are automatically creating a new device record so your machine won't pick up the collection variables as it won't actually be in that collection, so the behaviour you are seeing is correct.

    As Jason says above, I think you would be best to gather the MAC addresses (or SMS BIOS GUIDs) and import them in a file (Right click Devices, Import Computer Information). Then you can move them to the relevant collections and they will pick up the variables.

    Thursday, October 18, 2012 10:42 AM
  • This problem has been resolved. 

    The method i was trying to use to fix this problem was not the correct way to go about it. To get around this issue i had to change my approach so that instead of relying on Config manager to provide the Collection Variables, i needed a script to contact AD directly and return the collection variable to the task sequence.

    To do this i followed this guide.


    No need to update collections. The software retrieved straight from the source. 

    If anyone has any questions about this process i would be happy to help.

    Thanks to peter and Jason for your help.

    Clinton Mohoupt

    • Marked as answer by mopey85 Sunday, October 21, 2012 9:55 AM
    Sunday, October 21, 2012 9:55 AM