I want to building a new SCCM server from scratch and the old SCCM Server should be removed

SSE@TUE 360 Reputation points
2026-05-28T16:10:38.43+00:00

Hi,

my SCCM Server does not work fine like before many years. I want to building a new SCCM server from scratch

can I still use the old container (called System Management) and delegate control by adding the new server without necessarily extending the AD schema?

Could I let running it the old SCCM server and install a new one fresh instillation of SCCM Server?

What is the best praxis?

Regards

Microsoft Security | Intune | Configuration Manager | Other
0 comments No comments

1 answer

Sort by: Most helpful
  1. Marcin Policht 105.3K Reputation points MVP Volunteer Moderator
    2026-05-28T16:26:32.5+00:00

    Yep - you can reuse the existing Active Directory container “System Management” and even keep the old SCCM environment running while you build a new one, but there are some important constraints and what you are proposing is only partially valid depending on how “clean” and supportable you want the result to be.

    First, about the “System Management” container - you can reuse it for a new SCCM site, but only if you correctly reset or extend permissions so the new site server computer account has full control over that container and its objects. SCCM publishes site data (management points, boundaries, etc.) into that container. If the old server still has active write access, you can end up with conflicts or stale data. In practice, most rebuilds either reuse the container with a cleaned ACL or delete and recreate it, but deleting is usually avoided in large environments because of dependencies and lingering objects.

    Regarding AD schema extension, in modern Configuration Manager (current branch), extending the schema is still strongly recommended and in most real deployments effectively assumed. While the product can function in limited scenarios without full schema extensions, you lose reliable publishing of site data to AD, and many enterprise features and clean client auto-discovery behaviors depend on it. So the idea of avoiding schema extension entirely is not considered best practice anymore. If the schema was already extended years ago for the old SCCM, you do not need to extend it again; schema extension is forest-wide and one-time.

    You can run the old SCCM server and a new SCCM server in parallel, but they must be in separate sites (different site codes). They are independent hierarchies unless you explicitly use migration features. Coexistence is supported during migration phases, but you need to carefully separate boundaries, discovery scopes, and client assignment rules to avoid clients flipping between sites.

    What you are describing is essentially a side-by-side migration scenario. The supported “best practice” approach is not to manually rebuild and hope AD objects cooperate, but to either perform a proper migration using the Configuration Manager migration feature (from old hierarchy to new hierarchy), or do a clean new primary site deployment and then migrate content, boundaries, packages, applications, task sequences, and clients in a controlled way.

    If your current SCCM is “not working fine like before many years”, the decision point is important. I the database and hierarchy are still salvageable, fixing and upgrading in place is often significantly safer than rebuilding. If it is truly unstable or undocumented, then a fresh current branch installation is reasonable, but you should treat it as a migration project, not just a reinstall.

    So the short answer is: yes, you can reuse the “System Management” container, but only with correct permissions and ideally after confirming schema is already extended in the forest. And yes, you can run old and new SCCM in parallel, but the proper method is side-by-side migration or a controlled cutover, not just installing a second server and hoping AD publishing and clients will behave automatically.


    If the above response helps answer your question, remember to "Accept Answer" so that others in the community facing similar issues can easily find the solution. Your contribution is highly appreciated.

    hth

    Marcin

    Was this answer helpful?


Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.