locked
Moving old clients to new ConfigMgr site RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    We have old ConfigMgr 2012 environment (we aquired another company while ago). We need to start managing all the client with our ConfigMgr 1702 and get rid of everyhing in that old ConfigMgr 2012 environment. What is the best method for taking over the clients? Should we just reinstall all clients with 1702 client version? 

    Tuesday, May 9, 2017 4:06 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    http://blogs.technet.com/b/configmgrteam/archive/2009/04/09/reassigning-a-configuration-manager-client-across-hierarchies.aspx is old and no longer applicable. It's also not the scenario here either as the clients need to be upgraded also.

    A simple (re-)push of the clients from the new 1702 site will work fine.

    You should delete all of the boundary groups from the old site as well to avoid any conflicts or confusion.

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

    Tuesday, May 9, 2017 5:45 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote
    Hello

    You'd have to ensure that the active directory sites are configured correctly across the forests/domains
    you'd have to ensure that the boundaries are configured correctly on both SCCM environments and do not overlap
    You can use a script to force the change of an SCCM Clients site and server
    An example of this is here:
    http://gallery.technet.microsoft.com/scriptcenter/Change-sccm-configmgr-cf6e0327

    However you would also need to move the client into a boundary that belongs to the new SCCM site, or move the boundary from the old SCCM site into the new one. The complexity is that you still have the old SCCM infrastructure in the old domain, which complicates boundary assignment and site discovery, as any SCCM clients in the old domain will automatically discover the old Infrastructure.

    Because its a new SCCM infrastructure I don't really understand the resistance in reinstalling the client, everything will be new in any case.

    The clients needs to be assigned to the new SCCM infrastructure. Take a look at the following technet blog:

    http://blogs.technet.com/b/configmgrteam/archive/2009/04/09/reassigning-a-configuration-manager-client-across-hierarchies.aspx



    • Edited by ReginRavi Tuesday, May 9, 2017 5:23 PM
    Tuesday, May 9, 2017 5:19 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    http://blogs.technet.com/b/configmgrteam/archive/2009/04/09/reassigning-a-configuration-manager-client-across-hierarchies.aspx is old and no longer applicable. It's also not the scenario here either as the clients need to be upgraded also.

    A simple (re-)push of the clients from the new 1702 site will work fine.

    You should delete all of the boundary groups from the old site as well to avoid any conflicts or confusion.

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

    Tuesday, May 9, 2017 5:45 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Thanks Jason and ReginRavi! 
    Wednesday, May 10, 2017 6:06 PM