Monday, November 29, 2010

SCSM Command Shell

Unlike Operations Manager and Exchange 2010, the Service Manager command shell is not simply a shortcut. However, you can add the Service Manager command shell to PowerShell. The below is a clip taken from a TechNet article.


To add the Service Manager Windows PowerShell snap-in to a PowerShell session

  1. On the computer that you run Windows PowerShell on, for example, the computer that hosts the Service Manager or data warehouse management server, on the taskbar, click Start, point to Programs, point to Windows PowerShell 1.0, right-click Windows PowerShell, and then click Run as administrator.
  2. In the Windows PowerShell window, type the following commands:
  • Set-ExecutionPolicy RemoteSigned
  • Add-PSSnapIn SMCmdletSnapIn

Incident Resolution Satisfaction Surveys on SharePoint - SCSM Engineering Team Blog - Site Home - TechNet Blogs

Many people have requested incident surveys. Here is a potential solution.

Wednesday, November 24, 2010

Authoring Console and Management Pack References after CU3

If you have updated to Service Manager CU3, you will notice warnings in the event logs that show management pack mismatches between. *.0 and *.216. This is a bug, and it will be fixed in the next release. However, if you are working in the Authoring console the referenced management packs will not necessarily be *.216. To successfully import the management pack, you will have to manually change the references back to *.0 first. After making the changes, you will be able to open the MP in the authoring console until you change the references back.


Changing the Authored Management Pack References for Import into Service Manager.
  1. Make a copy of your authored management pack.
  2. Open the MP using an editor.
  3. Find the references section.
  4. Perform a Find and Replace. Find .216. Replace with .0.
  5. Import the MP into Service Manager

Monday, November 22, 2010

Troubleshooting Operations Manager Alert Connector

In Service Manager, there have been times where the OpsMgr Alert connector would stop forwarding alerts. I would troubleshoot for hours to no end. I tried just about everything short of uninstalling the software. Finally, I found what seems like a tried and true solution (for me).

Operations Manager Alert Connector problems I have had:

  • Alerts stop forwarding
  • I received a "Task Cannot be completed" error when attempting to delete the connector in SM, or even trying to view the properties.
Here are the steps I took to get alert forwarding working again. 

***Disclaimer: Microsoft may not support all of these steps, so please test and use at your own risk.

Delete the SCSM Connector
  • Open SCSM
  • Go to the Administration Tab, then go to connectors
  • Find the OpsMgr Alert Connector and delete it.
What if it won't delete?
  • I have been searching for a way to delete it from the database, but I have not been successful. I will update this post when I do.
Delete the Connector from OpsMgr
Create a new Connector in Service Manager (Pulled Directly from the Admin Guide)
***Follow steps exactly, and wait for the Connector to show up in Operations Manager
1.   In the Service Manager console, click Administration.
2.   In the Administration pane, expand Administration, and then click Connectors.
3.   In the Tasks pane, under Connectors, click Create Connector, and then click Operations Manager Alert Connector.
4.   Follow these steps to complete the Operations Manager Alert Connector Wizard:
a.   On the Before You Begin page, click Next.
b.   On the General page, in the Name box, type a name for the new connector. Make sure that the Enable check box is selected, and then click Next. Make note of this name; you will need this name in step 7 of this procedure.
c.   On the Server Details page, in the Server name box, type the name of the server that is hosting the Operations Manager root management server. Under Credentials, click New.
d.   In the Run As Account dialog box, in the Display name box, type a name for this Run As account. In the Account list, select Windows Account.
e.   In the User Name, Password, and Domain fields, type the credentials for the Run As account, and then click OK. For more information about the permissions that are required for this Run As account, see Accounts Required During Setup (http://go.microsoft.com/fwlink/?LinkId=182907) in the System Center Service Manager Planning Guide.
f.    On the Server Details page, click Test Connection. If you receive the following confirmation message, click OK, and then click Next:
The connection to the server was successful.
g.   On the Alert Routing Rules page, click Add.
h.   In the Add Alert Routing Rule dialog box, create a name for the rule, select the template that you want to use to process incidents created by an alert, and then select the alert criteria you want to use. Click OK, and then click Next.
i.    On the Schedule page, select Close alerts in Operations Manager when incidents are resolved or closed or Resolve incidents automatically when the alerts in Operations Manager are closed, click Next, and then click Create.
5.   Start the Operations Manager console, and connect to the Operations Manager root management server.
6.   Use the appropriate method based on the version of Operations Manager 2007 you are using:
·      In Operations Manager 2007 SP1, in the Administration pane, click Product Connectors.
·      In Operations Manager 2007 R2, in the Administration pane, click Product Connectors, and then click Internal Connectors.
7.   In the Connectors pane, click the name of the alert connector you specified in step 4b.
8.   In the Actions pane, click Properties.
9.   In the Alert Sync: <name of connector> dialog box, click Add.
10.  In the Product Connector Subscription Wizard dialog box, on the General page, in the Subscription Name box, type the name for this subscription. For example, type All Alerts, and then click Next.
11.  On the Approve groups page, click Next.
12.  On the Approve targets page, click Next.
13.  On the Criteria page, click Create.
14.  In the Alert Sync:<name of connector> dialog box, click OK.
To validate the creation of an Operations Manager 2007 alert connector
·      Confirm that the connector you created is displayed in the Service Manager console in the Connectors pane.
·      Confirm that incidents are created in Service Manager from alerts in Operations Manager.

New System Center Service Manager Blog

I have recently been required to learn, demo and deploy Service Manager to various customers. I have created this blog to help you and me in our journey with System Center Service Manager. Feel free to comment on posts, as I will probably need help along the way. I will attempt to post the more helpful articles.