locked
Migrating SCOM 2012 R2 Servers from one Datacenter to Another with different hostnames. RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi All,

    We have approx. 2300+ servers in monitoring. And our infra consists of 1 Management Group, 5 MS and 12 GW servers and also 1 Certificate authority server.

    Now we have been asked by the customer to migrate our SCOM servers to a new datacenter using different hostname. I would like to know what should be our approach for the migration as the hostname of the servers will be changed and how we are going to manage agent failover.

    Please let me know what all I need to take care before we migrate the servers. If there is any TechNet link available then pls do share that as well.

    Thanks in advance.

    Monday, July 13, 2020 2:47 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    Unfortunately you cannot rename a management server or any other "core component", you'll need to re-build the servers.

    So in short:
    Install the new SCOM management & gateway servers, then move across agents that are reporting in to the old management server and then decommission the old MS.

    In this case you could consider a side-by-side migration, and if you're running an older SCOM version (2012 R2, 1801, 1807 or 2016) then this is the perfect  opportunity to upgrade it to SCOM 2019 by installing a new SCOM management group, get newer Windows Server and SQL Server versions.

    Best regards,
    Leon

    Blog: https://thesystemcenterblog.com LinkedIn:

    • Marked as answer by Anchal.G Thursday, July 16, 2020 7:37 AM
    Monday, July 13, 2020 3:27 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    Unfortunately you cannot rename a management server or any other "core component", you'll need to re-build the servers.

    So in short:
    Install the new SCOM management & gateway servers, then move across agents that are reporting in to the old management server and then decommission the old MS.

    In this case you could consider a side-by-side migration, and if you're running an older SCOM version (2012 R2, 1801, 1807 or 2016) then this is the perfect  opportunity to upgrade it to SCOM 2019 by installing a new SCOM management group, get newer Windows Server and SQL Server versions.

    Best regards,
    Leon

    Blog: https://thesystemcenterblog.com LinkedIn:

    • Marked as answer by Anchal.G Thursday, July 16, 2020 7:37 AM
    Monday, July 13, 2020 3:27 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Thanks Leon for your quick response.
    Thursday, July 16, 2020 7:37 AM