Share via

Requirements for new infrastructure

Sergi Díaz Ruiz 240 Reputation points
2024-10-03T10:56:38.9333333+00:00

Good afternoon!

I need migrate my primary server to a new infrastructure in order to update the OS and SQL.

First of all.... I think is better split the different roles of primary site.

Is better install the roles in another server?

Is this viable when I have all roles (SQL,SUP,DP,MP...) inside primary site?

How can dimension my new primary site? I always copy the specifications of the last server and ... It's ok... But I want to know how can I dimension it goodm with a solid base.

TIA!!

Microsoft Security | Intune | Configuration Manager | Other
0 comments
Accepted answer
  1. Simon Ren-MSFT 40,346 Reputation points Microsoft External Staff
    2024-10-04T05:59:39.12+00:00

    Hi,

    Thank you for posting in Microsoft Q&A forum.

    1,To migrate the primary server to a new infrastructure in order to update the OS and SQL, we can use site Backup and Restore method and use the FQDN and IP address of the new server are the same as the old one. Helpful articles for your reference:

    ConfigMgr Site Backup and Restore

    MIGRATE YOUR SCCM SERVER TO A NEWER SERVER

    ConfigMgr SCCM Server Hardware Migration Step by Step Guide to Perform

    Administrator checklists for migration planning in Configuration Manager

    2,You can refer to the official article to determine the site size and scale:

    Size and scale numbers for Configuration Manager

    Thanks for your time. Have a nice day!

    Best regards,

    Simon

    If the response is helpful, please click "Accept Answer" and upvote it.

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    0 comments

1 additional answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Sherry Kissinger 5,526 Reputation points
    2024-10-03T14:16:49.49+00:00

    "best" is always a very subjective term when it comes to design.

    My opinion, which could be wrong, is very subjective, and is likely wildly speculative:

    If you have less than say, 2000 clients, keeping everything on 1 single server is probably just fine.

    If you have any number of clients, but you want to split out roles into "just 2" servers, then I would put "anything that needs IIS" onto one server, and everything else onto the other server. So 1 server for SQL/Primary itself (aka, where the inboxes are), SMS Provider, Reporting Point, other doesn't-need-iis roles you might have.

    For 'roles that need IIS', that would be (for example) the SUP, Management Point, DP.

    If you have more than say... 30,000 clients, then you might need (or want) to start thinking about how to split out more roles to more servers. Maybe you want SQL offbox, because you want to have Active and Passive Primary sites. Or maybe you feel you want/need more DPs, or more MPs. That's on you to determine what makes sense.

    Again, just my opinion, I could be wrong and likely am. Note I do NOT consult for a living nor advise people on "what is best". This is just a completely subjective opinion based on almost no information and wild guesses.

    2 people found this answer helpful.

Your answer

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