Setting Up a Service Manager 2010 Lab Environment with Production Data
Updated: May 13, 2016
Applies To: System Center 2012 - Service Manager, System Center 2012 R2 Service Manager
This section explains how to create a lab environment and populate it with production data so that upgrades can be performed and tested before an actual upgrade in the production environment. The procedures in this section show you how to configure System Center Service Manager 2010 Service Pack 1 (SP1) Cumulative Update 3 (CU3) in a lab environment with production data. You then perform an in-place upgrade to System Center 2012 – Service Manager. It is important to follow the steps in this section in sequence.
Install any cumulative updates that you installed on the Primary Management server on the Secondary Management Server.
Disable all workflows in the production environment that you do not want to be running in the lab environment.
Enable all workflows in the Production Service Manager environment that you disabled in step 6.
If possible, block communications to SQL from the Secondary Management server to the Production ServiceManager Database server.
Verify that the lab environment works. Try to open the console on the Secondary Management server and see if you can connect to the console. Confirm that the Data Warehouse and Reporting do not appear. After you confirm that this works, complete the rest of the steps.
Do not enable or delete the Operations Manager alert connector in the lab environment. This will cause the alert connector in the production environment to fail.
If you want to test the email notification and incoming email functionality, use a separate SMTP instance to send emails to eliminate flooding the inboxes of users with test emails. To test the incoming email feature, you can point to a test share and drop the eml files into this share when you are ready to test.
Back up this lab environment; for example, back up the database and encryption keys and VM Snapshots This gives you the ability to recover in case the upgrade fails.
If you are able to successfully complete all the previous steps, you are ready to attempt the in-place upgrade.
Test everything. Document any discrepancies and fixes. Send feedback through the MS Connect web site.
Backup this Service Manager lab environment; for example, back up the database and encryption keys and VM Snapshots This gives you the ability to recover in case the upgrade fails.
The lab environment is now ready for System Center 2012 – Service Manager in-place upgrade.