Importing and Configuring System Center 2012 Service Manager MP

The System Center 2012 Service Manager MP has some pitfalls during importing and configuration that you may stumble upon. So I will describe the steps needed to be made in case the MP guide is not clear enough.

1. First you need to install the MP so you can get the following MPs extracted:

  • Microsoft.SystemCenter.ServiceManager.Discovery
  • Microsoft.SystemCenter.ServiceManager.Library
  • Microsoft.SystemCenter.ServiceManager.Monitoring

2. After you have these 3 MPs extracted you have to import only Microsoft.SystemCenter.ServiceManager.Library

3. After the MP above is imported successfully you have to create Run As account. You can use the default action account or a separate account for tighter security. Just make sure that the account you will use has the needed permissions. You can find description of the needed permissions here on page 17. I basically make the account local administrator on Service Manager Management Servers, Service Manager DW and give db_datareader permissions to the Service Manager database and to the staging and configuration database.

4. So you create that Run As account as Windows type. Secure the account to the Service Manager Management Servers, Service Manager DW server, Service Manager database server and Service Manager DW databases servers.

5. Next you need to add the account to the Service Manager Database Account profile. Distribute it to all objects.

6. Next step is to import Microsoft.SystemCenter.ServiceManager.Discovery MP.

7. After it is imported successfully discovery of Service Manager will start. And here is the tricky part you have to wait until full discovery is performed before importing Microsoft.SystemCenter.ServiceManager.Monitoring MP. Basically you have to wait at least 24 hours to make sure discovery of Service Manager has passed fully. Trough OpsMgr console you can check if full discovery has passed.

8. Open OpsMgr console and go to Discovered Inventory view. Target it to System Center DataWarehouse 2012 Server. You should see your Service Manager DW server and if all properties are filled with values that means your Service Manager DW server is fully discovered.

image

9. Next Target to SCSM 2012 Management Server. You should see all your Service Manager management servers. If all properties have values for all your Service Manager Management servers that means they are fully discovered. In my case I have only one Management Server:

image

10. To fully verify if Service Manager was discovered you can go to Distributed Applications and open the diagram for Service Manager:

image

11. All Service Manager servers and database should be visible with their properties in Detail View.

12. The last step is to import Microsoft.SystemCenter.ServiceManager.Monitoring MP so the monitoring of Service Manager can start.

The software I’ve used:

  • Windows Server 2012
  • SCSM 2012 SP1 UR2
  • SCOM 2012 SP1 UR2
  • System Center 2012 Service Manager 7.5.1561.0 MP

Note: System Center 2012 Service Manager 7.5.1561.0 MP does not state that System Center 2012 Service Manager SP1 is supported but so far I haven’t discovered something that is not working properly.

Installing and Importing Microsoft Exchange Server 2013 Management Pack 15.00.0620.030

After yesterday’s release of Exchange Server 2013 Management Pack I’ve managed to install it in a development environment. Here are the steps I’ve went trough:

1. Start installation and Accept License Agreement:

image

2. Choose installation location:

image

3. Import the installed MP into SCOM:

image

image

image

4. After the successful import you will start see you exchange servers appear in the default views:

image

image

5. After 5-10 minutes you will see all services appear as monitored:

image

image

image

So these are the steps. Pretty easy and simple. There are no special requirements or configurations. The MP uses the default action account for the monitoring and discovery.

Here are some of the bad news about this MP:

  • I’ve received an error a couple of hours after the deployment. The error wasn’t very descriptive. It had only the error description and a link (to Technet Library) that you can visit to find more information. I couldn’t opened the link  as the page still does not exists. I guess Microsoft still hasn’t uploaded all information about the MP in TechNet.
  • The MP does not collect performance data for Exchange 2013.
  • The MP does not contain any reports.

Here is what I’ve used in the environment:

  • SCOM 2012 SP1 UR2;
  • Microsoft Exchange Server 2013 Management Pack 15.00.0620.030;
  • Windows Server 2012 with latest updates;
  • Exchange 2013 CU1 in multitenant mode;

Installing Windows Server Operating System version 6.0.7026.0 MP

I’ve deployed the latest version of Windows Server OS MP without any issues. It was quite easy so I will just share my experience for those who are interested.

1. Install the new version of the MP. Tip 1: I always install all MPs to one folder so I can find easy what MPs I have installed. Tip 2: I always make a copy of the previous version before installing the new one.

image

2. After the installation I import the new versions. Tip 3: I install only those MPs I need. In the case below I do not install MPs for Windows Server 2000 and 2003 because I do not have such servers in my environment.

image

3. Importing was successful.

image

4. After the import you will see the added collection rules in this new version.

image

5. I also check if there are any new alerts that may have risen because of this new MP in Active Alerts view.

6. If you synchronize objects from SCOM to SCSM you have to update the MPs in SCSM also.

image

Happy updating!

The Power of the Community: New Tool to “Sanitize” Runbook Exports

When you export runbook from development environment and import in production generally this runbook imports also global settings and global configurations even if they are not referenced by the exported runbook. This is where this tool comes in help. The tool removes these global settings and configurations from the exported runbooks.

Author of the tool is Ryan Andorfer you can find more information about the tool on his blog.

SanitizeExport.exe can be download at codeplex.