Timothy Else
asked on
SCCM - New CAS and Primary Site Migration
Hi,
I'm wondering if anyone has experience with migrating multiple primary sites from multiple CAS's to a single CAS.
I've a scenario whereby I will need to take a number of existing Primary Sites that are associated to several different CAS sites currently and migrating these so they all sit under a single CAS.
From what I have read it is not possible to disassociated a primary site from an existing CAS, I'm thinking that I will need to do the following:
1. Create new Primary Site
2. Backup and migrate existing Primary site to new Primary Site
3. Create CAS, specify new Primary Site at install to bring it into the CAS pool.
4. Repeat steps 1 and 2 for all other Primary Sites
5. Add new Primary Sites as Child sites to new CAS
I know there's going to be a lot more to it than the above but I wanted to make a start. I'm not certain this is the best way to do it so I'm open to any suggestions or ideas.
Thanks.
I'm wondering if anyone has experience with migrating multiple primary sites from multiple CAS's to a single CAS.
I've a scenario whereby I will need to take a number of existing Primary Sites that are associated to several different CAS sites currently and migrating these so they all sit under a single CAS.
From what I have read it is not possible to disassociated a primary site from an existing CAS, I'm thinking that I will need to do the following:
1. Create new Primary Site
2. Backup and migrate existing Primary site to new Primary Site
3. Create CAS, specify new Primary Site at install to bring it into the CAS pool.
4. Repeat steps 1 and 2 for all other Primary Sites
5. Add new Primary Sites as Child sites to new CAS
I know there's going to be a lot more to it than the above but I wanted to make a start. I'm not certain this is the best way to do it so I'm open to any suggestions or ideas.
Thanks.
This question needs an answer!
Become an EE member today
7 DAY FREE TRIALMembers can start a 7-Day Free trial then enjoy unlimited access to the platform.
View membership options
or
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
Hi,
I don't know why you've already got multiple CASes but I can guess it's overkill. From the Product docs, the design is simple or complex. The key thing (forget the whole CAS thing) is "how many devices you have". That is *the* key deciding factor.
Hierarchy topology
Hierarchy topologies range from:
The key driver of the type and count of sites that you use in a hierarchy is usually the number and type of devices you must support.
SOURCE:
https://docs.microsoft.com/en-us/configmgr/core/plan-design/hierarchy/design-a-hierarchy-of-sites
If I were you, unless there's a real, genuine business reason (that could simply be politically driven) for a CAS, I would go he a Primary Site with a hierarchy of other Primaries. Current Branch has changed the rules, since 2012 even. Have a good read of that link and read it through.
Then read this:
https://www.systemcenterdudes.com/sccm-best-practices/
If you don't have 175,000 machines (used to be 150000) OR don't need 250 DPs, you do NOT need a CAS.
If the reason is partitioning : by that I mean securing different countries or depts from accessing certain things, you still don't need a CAS: use Role Based Access (RBAC) instead. I work for a large corporate with USA, France, India and Netherlands. There's no CAS. They separate collections etc, using RBAC.
I hope I've convinced you. It is a lot simpler. Just create a primary and backup and restore only the things you want to keep. If you're installing fresh MEMCM (the new version) it's a good time to start afresh and get things organised, and be selective about things you import back. Don't just copy and paste the old bits. Keep your new instance clean and controlled tightly with RBAC.
Mike