locked
Moving clients between sites RRS feed

  • Question

  • We currently have 5 primary sites with a CAS. Recently the decision was made to logically move the office computers at one location and have them report into a different primary site. 

    The boundary and boundary group where moved from the former site to the new site and the computers where assigned to new OUs in AD. After the move I cannot get the computers to update the SCCM Client to point to the new site. They keep updating to the old site.

    Even when I use CCMclean to manually remove the client from the machines and then try to force them to install to the new site, they fail the install with a "No DP found with the client software" type of error and then reinstall back into the old site.

    They are being discovered in AD with System Discovery but the DDM shows an error: CDiscoverDataManager::ObsoleteOldRecords - Client's SMSID and Previous SMSID are same which will result in self obsoleting. Therefore Skipped obsoleting. SMS_DISCOVERY_DATA_MANAGER 12/27/2016 1:17:04 PM 17656 (0x44F8)

    There is no Discovery record created for these machines.

    Brand new computers being built are discovered and installed correctly, the problem is with the old machines moved from the former site.

    Has anyone else seen this type of problem and can suggest a solution?

    Tuesday, December 27, 2016 6:36 PM

Answers

  • Did you use a GPO to install the client originally? if so this tattoo the registry and will need to clean that up first before moving the clients.

    Garth Jones

    Blog: http://www.enhansoft.com/blog Old Blog: http://smsug.ca/blogs/garth_jones/default.aspx

    Twitter: @GarthMJ Book: System Center Configuration Manager Reporting Unleased

    • Marked as answer by KenRumble Wednesday, December 28, 2016 7:22 PM
    Tuesday, December 27, 2016 8:56 PM
  • After the client is assigned to a site, it remains assigned to that site even if you changed the boundary/boundary group. Clean and re-install CM agent should be able to re-assign client agent to new sites. However, there are exceptions:

    The client is not windows embedded device with write filter enabled; see

    https://docs.microsoft.com/en-us/sccm/core/clients/deploy/assign-clients-to-a-site

    You're using GP to assign clients to a specific site, see below link:

    http://blog.coretech.dk/heh/new-agents-will-not-re-assign-to-configmgr-2012-site/


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    • Marked as answer by KenRumble Wednesday, December 28, 2016 7:23 PM
    Wednesday, December 28, 2016 6:29 AM

All replies

  • Did you use a GPO to install the client originally? if so this tattoo the registry and will need to clean that up first before moving the clients.

    Garth Jones

    Blog: http://www.enhansoft.com/blog Old Blog: http://smsug.ca/blogs/garth_jones/default.aspx

    Twitter: @GarthMJ Book: System Center Configuration Manager Reporting Unleased

    • Marked as answer by KenRumble Wednesday, December 28, 2016 7:22 PM
    Tuesday, December 27, 2016 8:56 PM
  • Not sure actually, will have to ask the site administrator for that site to see if they did, thanks or the tip
    Tuesday, December 27, 2016 9:05 PM
  • After the client is assigned to a site, it remains assigned to that site even if you changed the boundary/boundary group. Clean and re-install CM agent should be able to re-assign client agent to new sites. However, there are exceptions:

    The client is not windows embedded device with write filter enabled; see

    https://docs.microsoft.com/en-us/sccm/core/clients/deploy/assign-clients-to-a-site

    You're using GP to assign clients to a specific site, see below link:

    http://blog.coretech.dk/heh/new-agents-will-not-re-assign-to-configmgr-2012-site/


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    • Marked as answer by KenRumble Wednesday, December 28, 2016 7:23 PM
    Wednesday, December 28, 2016 6:29 AM
  • Clean and re-install CM agent should be able to re-assign client agent to new sites. .


    This is not needed although it would work. Just re-assign it using a script is also sufficient.

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

    Wednesday, December 28, 2016 7:45 AM