After Upgrading to System Center 2012 R2 - Service Manager

  • Article

Applies To: System Center 2012 R2 Service Manager, System Center 2012 SP1 - Service Manager

This topic describes the actions you need to take after you upgrade to System Center 2012 R2 Service Manager, including the following sections:

  1. How to restart the System Center Data Access Service service if it fails to start after upgrading

  2. How to start the Service Manager workflows and restart the data warehouse jobs

  3. How to stop and then start Microsoft SQL Server Reporting Services after an upgrade

  4. How to prepare for chargeback reports after upgrading

Restart the Data Access Service service and Service Manager workflows on the data warehouse management server

If necessary, use the following procedures to restart the service and workflows.

To restart the Data Access Service service

  1. On the computer that hosts the data warehouse management server, on the Windows desktop, click Start, and then click Run.

  2. In the Run dialog box, in Open, type services.msc, and then click OK.

  3. In the Services window, in the Services (Local) pane, right-click System Center Data Access Service, and then click Start.

To start Service Manager workflows

  1. On the computer that hosts the Service Manager management server, on the Windows desktop, click Start, and then click Run.

  2. In the Run dialog box, in Open, type services.msc, and then click OK.

  3. In the Services window, in the Services (Local) pane, right-click System Center Management, and then click Start.

    Note

    For System Center 2012 R2 Service Manager, the System Center Management service was renamed to Microsoft Monitoring Agent.

Restart data warehouse jobs

After you upgrade the data warehouse management server, you might need to restart the data warehouse (extraction, transformation, and loading [ETL]) jobs. You can use the following procedure to restart the data warehouse jobs. In this procedure, you enable data warehouse job schedules by using Windows PowerShell® cmdlets.

To restart data warehouse jobs

  1. On the computer that hosts the data warehouse management server, click Start, point to Programs, point to Accessories, click Windows PowerShell, right-click Windows PowerShell, and then click Run as administrator.

  2. Type the following commands, and then press Enter after each command.

    Note

    The following command examples assume that Service Manager was installed in its default location on the C: drive. If necessary, change directories to the location where you installed Service Manager.

    cd 'C:\Program Files\Microsoft System Center 2012\Service Manager'

import-module $PWD/Microsoft.EnterpriseManagement.Warehouse.Cmdlets.psd1

Get-SCDWJob

Enable-SCDWJobSchedule –JobName Extract_<data warehouse management group name>

Enable-SCDWJobSchedule –JobName Extract_<Service Manager management group name>

Enable-SCDWJobSchedule –JobName Transform.Common

Enable-SCDWJobSchedule –JobName Load.Common

Enable-SCDWJobSchedule –JobName DWMaintenance

Enable-SCDWJobSchedule –JobName MPSyncJob

Start-SCDWJob –JobName MPSyncJob

    The last command, Start-SCDWJob – JobName MPSyncJob, enables the ETL jobs to run.

Stop and then start SQL Server Reporting Services

After you perform an upgrade to Service Manager in System Center 2012 R2, use the following procedure to stop and then start SQL Server Reporting Services.

To stop and then start SQL Server Reporting Services

  1. On the computer that hosts SQL Server Reporting Services, on the Windows desktop, click Start, and then click Run.

  2. In the Run dialog box, type services.msc, and then click OK.

  3. In the Services window, in the Services (Local) pane, right-click SQL Server Reporting Services, and then click Stop.

  4. In the Services window, in the Services (Local) pane, right-click SQL Server Reporting Services, and then click Start.

Prepare for chargeback reports

When you try to use chargeback after you have upgraded to Service Manager, your Operations Manager CI connector might stop synchronizing new Virtual Machine Manager objects, such as VMM clouds, if the VMM Server was upgraded to System Center 2012 R2 Virtual Machine Manager. This occurs because Service Manager does not have the correct version of the VMM management packs.

Additionally, installing chargeback report files to the System Center 2012 R2 Operations Manager management server might fail after you upgrade System Center 2012 R2 Service Manager because the Dependencies folder does not contain the required management pack files.

Use the following procedures to prepare for chargeback reports.

To prepare Service Manager for chargeback reports

  1. On the server running System Center 2012 R2 Virtual Machine Manager, copy the following management packs from their installed location, by default InstallationDrive:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\ManagementPacks, to a folder on the server running the Service Manager management server.

    • Microsoft.SystemCenter.VirtualMachineManager.PRO.Library

    • Microsoft.SystemCenter.VirtualMachineManager.PRO.V2.Library

    • Microsoft.SystemCenter.VirtualMachineManager.Pro.2008.Library

    • Microsoft.SystemCenter.VirtualMachineManager.Library

    • Microsoft.SystemCenter.VirtualMachineManager.2012.Discovery

  2. Start the Service Manager console and navigate to Administration, Management Packs.

  3. Import the management packs that you copied to the Service Manager management server.

To prepare Operations Manager for chargeback reports

  1. On the server running System Center 2012 R2 Virtual Machine Manager, copy the following management packs from their installed location, by default InstallationDrive:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\ManagementPacks, to a folder on the Operations Manager management server.

    • Microsoft.SystemCenter.VirtualMachineManager.PRO.Library

    • Microsoft.SystemCenter.VirtualMachineManager.PRO.V2.Library

    • Microsoft.SystemCenter.VirtualMachineManager.Pro.2008.Library

    • Microsoft.SystemCenter.VirtualMachineManager.Library

    • Microsoft.SystemCenter.VirtualMachineManager.2012.Discovery

  2. Start the Operations Manager console and navigate to Administration, Management Packs.

  3. Import the management packs that you copied to the Service Manager management server and then in the Online Catalog Connection dialog box, click Yes to search the catalog for dependencies that might not be available locally.

-----
For additional resources, see Information and Support for System Center 2012.

Tip: Use this query to find online documentation in the TechNet Library for System Center 2012. For instructions and examples, see Search the System Center 2012 Documentation Library.
-----