locked
Move SCCM Site from one CAS to another? RRS feed

  • Question

  • Fairly new to SCCM.

    My organization is splitting off from a parent organization.  Currently we're responsible for a single site server that is linked to the other organization's CAS.

    This is my first post as I try and figure out how we're going to do this.  We will need our own CAS but can we move our Site from their CAS to a new one?

    First question - is there a procedure for moving a Site from one CAS to  another?  Is it possible?

    Second - if anyone could point me to documentation on how to resolve this issue it would be helpful.

    Any solid leads will help.

    Thanks!

    Monday, September 17, 2018 7:30 PM

All replies

  • Firstly, Unless you have over 150,000 computer you don't need a CAS, a single primary site will do. 

    Secondly, there is no way to move a Primary site to another CAS or standalone. At best you can migrate details from the existing site server to a New primary site. 


    Garth Jones

    Blog: https://www.enhansoft.com/blog Old Blog: https://sccmug.ca/

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

    Monday, September 17, 2018 7:39 PM
  • BTW, this is the CM12 forum, if you are going to create a new site server, you are better off moving to the latest version CMCB.

    Garth Jones

    Blog: https://www.enhansoft.com/blog Old Blog: https://sccmug.ca/

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

    Monday, September 17, 2018 7:40 PM
  • > We will need our own CAS

    Why? A CAS is only explicitly necessary if you are managing more than 150,000 systems. There are a few other corner cases, but these are overcomeable in other ways. And, to be clear here, site servers do not provide any type of technical or logical separation whatsoever. Using a CAS when you don't need one introduces a lot of unnecessary overhead, latency, and points of failure.

    > is there a procedure for moving a Site from one CAS

    Nope, there is no such thing as pruning and grafting site servers as site servers do not in any way provide any type of separation or isolation -- all configuration is shared in a hierarchy. And as noted above, because site servers are meant only for client scalability, this simply isn't part of the design.

    Today, I would recommend that you set up your new primary site (no CAS) and use the migration tools to migrate what you need to migrate to the new site from the old hierarchy.


    Jason | https://home.configmgrftw.com | @jasonsandys

    Monday, September 17, 2018 7:47 PM
  • Sorry - pulled away from this project for a while. 

    I understand we will not be needing a CAS and that is why we're attempting to pull out from under one.

    I wasn't part of the decision making process as far as the CAS.  Two state organizations merged and the 150k was a fast approaching number I'm guessing.  Both organizations have a large number of field ops spread out across the state that carry around three devices at times.

    The organizations are now separating.  The other organization has the CAS and we take care of our single site server.  We basically need to pull our site server out of their organization.

    I've been looking for documentation specific to this - separating a site server out from a CAS using migration tools available.  I'm still looking but any assistance in locating an overview of the migration process that would be similar to our situation would be great.

    Thank you.

    Monday, October 1, 2018 5:01 PM
  • There is no option to pull your site server out. 

    You need to migrate to a new site server(s). aka new hardware or new VM with new site code, etc. Then let the old site server "die on the vine" as the saying goes. This does assume that you content from your old site server. If not, then remove it your the old CAS, format it and start over with a new primary site server. 


    Garth Jones

    Blog: https://www.enhansoft.com/blog Old Blog: https://sccmug.ca/

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

    Monday, October 1, 2018 5:08 PM
  • > I understand we will not be needing a CAS and that is why we're attempting to pull out from under one.

    Your original question stated that you wanted a CAS though and that's why both Garth and I were quick to call out that you don't need one and really shouldn't have one either.

    > We basically need to pull our site server out of their organization.

    As noted, this is not possible and thus my recommendation for using the built-in migration tools to migrate to a new site.

    There's nothing specific or unique about this scenario. It's a "simple" migration covered by the official documentation: https://docs.microsoft.com/en-us/sccm/core/migration/migrate-data-between-hierarchies (simply only in terms that it's a built-in feature set). There are things that won't migrate though like client settings, EndPoint Protection policies and basically anything that didn't exist in ConfigMgr 2007 as the tools were originally designed to migrate folks from 2007 but unfortunately haven't been updated to include any new features. If you want an example walk-through, there are many to be had by performing a web search using your favorite search engine.


    Jason | https://home.configmgrftw.com | @jasonsandys



    Monday, October 1, 2018 5:13 PM
  • At the time I wrote the question I thought that our org had the bulk of the field personnel.  Found out later we do not and therefore do not need a CAS.

    From what you've said about things that won't migrate...this is going to be painful.  The links are great and I'll keep digging to see if I can find a blog etc. by someone who has walked through it and found some gotchas.

    Moving to the most current version was also a great suggestion - this will be the perfect time to do so and the subject had not been brought up in meetings.

    Thanks!

    Monday, October 1, 2018 5:38 PM
  • > "this is going to be painful."

    Yes. It can be done though.


    Jason | https://home.configmgrftw.com | @jasonsandys

    Monday, October 1, 2018 6:05 PM