Move a SCSM environment to new server

Question

Is it feasible and officially endorsed to migrate a SCSM setup to new server within a different domain name?

If not, is there a method for exporting SCSM data and then transferring it to the new server?

Appreciate your assistance in advance.

Answer 1

Migrating a SCSM environment to a new server in a different domain can be a complex task.

Here's a general outline of the steps you might need to take:

Preparation and Planning:

• Understand your current SCSM environment, including its components, configurations, and dependencies.

Set Up the New Server:

• Install a fresh instance of SCSM on the new server in the target domain. Make sure to choose the same version and update level as your existing SCSM setup.

Database Migration:

Back up your existing SCSM databases (ServiceManager and DWDataMart, for example) from the old server.

• Restore these databases on the new server.
• Update connection strings in SCSM configuration to point to the new databases.

Management Server Migration:

• Export management packs from the old server.
• Import these management packs into the new server.
• Configure connectors, workflows, and customizations on the new server to match the old environment.

Data Migration:

If you need to migrate existing data (work items, incidents, etc.), you may need to use PowerShell scripts to export data from the old server and import it into the new one. This can be a complex process, and you might need to handle data transformation due to differences in domains.

Testing:

Thoroughly test the new environment to ensure that all workflows, customizations, and data are working as expected. This is crucial to identify and address any issues before going live.

User and Permissions Migration:

Recreate user accounts and permissions in the new domain, and grant them appropriate access within SCSM.

DNS and Network Configuration:

Ensure that DNS and network settings are properly configured to allow communication between servers in different domains.

Update Configurations:

Update any configuration settings that might have changed due to the new environment.