You are browsing the archive for 2009 November.

System Center Service Manager Session with Nigel Cain

9:32 pm in Uncategorized by Kenny Buntinx [MVP]

On January 19 we will have a session with Nigel Cain, Senior Product Manager!

System Center Service Manager Integration

 Abstract:

In this session, we will take a detailed look at how Service Manager integrates with Operations Manager (SCOM) and Configuration Manager (SCCM) to help you to more effectively manage systems in your data center, learn how to define and manage business services, manage change to those services and create incidents when components fail or degrade. 

 

Speaker: Nigel Cain, Senior Program Manager

Nigel Cain is a Senior Program Manager in the Virtualization & Datacenter Management team responsible for driving customer focused design and development efforts.  His primary product responsibilities include System Center Service Manager and System Center Virtual Machine Manager.  Nigel joined Microsoft in 1998 as technical consultant and moved into a Program Management role in 2003. Since then he has worked on a number of different products and initiatives but his primary focus has always been on solutions that make Microsoft technologies easier to manage

 

Agenda Thuesday, January 19, 2010

  • 18:00 Registration and lunch
  • 18:45 Welcome
  • 19:00 System Center Service Manager Integration  by Nigel Cain
  • 21:00 Q&A and drink

 

For more information have a look at http://scug.be/content/Events.aspx

Register fast, seats are limited!

Alexandre Verkinderne

by

System Center Service Manager – Introduction and scope

10:44 pm in Uncategorized by

Hello Chaps,

This is my first article about System Center Service Manager 2010. This will be a multi part articles series.

Part 1: Introduction and scope

Part 2: High Level Architecture

Part 3: Diving into Incident Management

——————–

let’s start with Part 1:

 

Product Positioning

 

 

 The above picture describes the System Center Global Picture.

System Center Service Manager obviously tries to close the Gap between the current System Center Portfolio and a 360 degrees approach.

 

So far the following items were addressed or at least partially:

  • Operations Management
    • System Center Operations Manager
  • Configuration Management
    • System Center Configuration Manager
  • CMDB
    • Partially addressed in Configuration Manager
  • Knowledge
    • Partially addressed in Operations Manager

System Center Service Manager addresses the following items:

 

  • Incident Management
  • Problem Management
  • Self Service Portal
    • Password Reset
    • Software Request
  • CMDB
  • Knowledge Database
  • Native Integration with AD,SCOM,SCCM

SCSM builds and extends the familiar Management Pack Architecture with a more robust MP …

In fact the new MP structure allows images, forms, assemblies,etc…. bundled into a new .MPB file format( I will write blog article on this matter later)

Have a nice Day

Frederic Dumesle –

http://www.linkedin.com/pub/frederic-dumesle/0/229/9a2

 

 

 

Avatar of kurtvh

by kurtvh

New SCSM Solution Accelerator to Address Compliance and Risk Management Challenges!

1:09 pm in Uncategorized by kurtvh

Beta evaluations of the Compliance and Risk Process Management Pack and the IT Compliance Management Library for System Center Service Manager now available

This Beta release includes control activities and test automation for Windows Server 2008, Windows Server 2008 R2, and Windows 7.

The Compliance and Risk Process Management Pack and the IT Compliance Management Library extend System Center Service Manager with several new features that allow customers to:

  • Use the included Program Creation Wizard to quickly and easily determine which control objectives must be addressed to address compliance requirements defined in required regulations and standards.
  • Help eliminate the complexities and redundancies often found in multiple, overlapping regulations and standards.
  • Leverage System Center Service Manager’s integration with System Center Configuration Manager and System Center Operations Manager to monitor, validate, and report on the compliance state of deployed Microsoft products.

To Download the Beta

Please note that to begin your evaluation of this management pack you will need to download and install the Service Manager Beta-2 Update, available here

To download, simply go to the Service Manager site on Connect www.connect.microsoft.com. click the Downloads link and select “Compliance and Risk Process Management Pack Beta ” and then select all of the following files from the download details page:

  • ComplianceAndRiskProcessMPBeta_Documentation.zip – This file contains the documentation for the Compliance and Risk Process Management Pack. Please download this file first and read the Getting Started Guide prior to installation.
  • ComplianceAndRiskProcessMPBeta.exe – This is the install file for the Compliance and Risk Process Management Pack. This must be installed on your server running Service Manager Beta 2 to add compliance management capabilities.
  • IT_Compliance_Management_Library_Beta.exe – This is the install file for the IT Compliance Management Library containing control libraries and automation enhancements for the Compliance and Risk Process Management Pack. Please read the ITCML User’s Guide before installing.

Have Fun,

Kurt Van Hoecke

Session Recording Service Manager: From Re-active to Pro-active

7:41 pm in Uncategorized by Kenny Buntinx [MVP]

In this session Maarten Goet, SCOM MVP and participant in the TAP-program for Service Manager, is going to show us what the possibilities are of Service Manager. First he will explain the architecture of Service Manager after which he will deep-dive into the possibilities of Incident-, Change Management and CMDB. With some real life examples Maarten will also show us the possibilities of the SCOM and SCCM connector.

For IT-pros who are working with ITIL, COBIT or the MOF framework, for IT-pros who are interested or searching for a helpdesk system with integration into the system center suite and for IT-decision takers that need to comply with several standards, this is a session you can’t miss.

Part I

[evid:technet:1474]

Part II

[evid:technet:1475]

Availability of Service Manager Beta-2 (Update)

7:34 pm in Uncategorized by The WMI guy

The Service Manager team just announced the availability of Service Manager Beta-2 (Update)

This refresh is being made available to support the release of the Compliance and Risk Process Management Pack (click here to download). In addition to specific fixes to support this solution, a number of other issues have been addressed from the earlier Beta build:

· Allow Administrators to select which SCCM packages to display to end users in the self-service portal

· Enable import of CIs from custom Operations Manager 2007 objects

· Active Directory Connector wizard supports user accounts in another forest (included non-trusted)

· Provide view of workflow failures or timeouts and allow administrators to retry workflows if needed

· Fixed issue for workflow authoring – enable the use of parameter settings defined in an unsealed management pack

· Group memberships are now refreshed automatically

· Templates continue to work after list values are deleted

· Knowledge Categories can now be customized

· Fixed an issue where time worked was incorrectly calculated in the Incident Analyst report

 

Download

To download, simply go to the Service Manager site on Connect www.connect.microsoft.com. Once you have successfully signed in, click the Downloads link, click Service Manager Beta-2 Update.

Have fun,

Alexandre Verkinderen

Avatar of kurtvh

by kurtvh

Importing data into SCSM (part2) – the SCSM OpsMgr Alert connector

3:25 pm in Uncategorized by kurtvh

Hello,

Part 1 blog post (Importing data into SCSM (part 1) – the SCSM AD & SCCM connectors) of the importing data into SCSM blog series is handling the AD and ConfigMgr connector. This second part will provide some more information about the OpsMgr connectors in SCSM.

Two connectors are available in Service Manager:

  • Operations Manager Alert connector: The OpsMgr alert connector is used to automatically generate incidents that are based on Operations Manager alerts.
  • Operations Manager CI connector: This connector will import objects that were discovered by Operations Manager into the Service Manager database.

In this post we will handle the Operations Manager Alert Connector.

Installation and configuration of the Operations Manager Alert Connector

The installation of this connector is a two phase’s process.

  • The first part involves creating the Alert connector on the SCSM server.
  • The second part requires that you start the OpsMgr console and set up a subscription for the newly created connector.

Creating the Alert connector on the SCSM server

Pre-requisites:

OpsMgr Alert Connector account with the following rights:

  • Must be a domain account.
  • Must be a member of the Users local security group on the Service Manager management server.
  • Must be an Operations Manager 2007 Administrator.

Installation of the connector

In the Service Manager console, click Administration.

In the Administration pane, expand Administration, and then click Connectors.

In the Tasks pane, under Connectors, click Create Connector, and then select Operations Manager Alert Connector.

clip_image002

1. On the Before You Begin page, click Next.

2. On the General page, in the Name box, type a name for the new connector.

clip_image004

(On this page, we can enable or disable the connector.)

3. On the Server Details page, type the name of the server that is hosting the OpsMgr root management server.

In the credentials section of the page, select an existing account with adequate right or create a new account. Test the connection before preceding the wizard.

clip_image006

4. On the Alert Routing Rules page, click Add if you need to configure specific templates for alerts. For this example, we leave the field empty. In this way, all alerts will be using the operation manager incident template.

clip_image008

5. On the Schedule page, specify the polling interval for the connector. Alert handling can be configured with following options: Resolve alerts in Operations Manager when incident is resolved and Resolve incident when alerts in Operations Manager are resolved. For this example, both options are selected.

clip_image010

6. On the Summary page, make sure that settings are correct, and then click Create.

7. On the Completion page, click Close to finish the OpsMgr connector installation.

clip_image012

First part of the OpsMgr installation is finished…

 

Creating the subscription in the OpsMgr Console

8. To continue with the second part of the installation, start the Operations Manager console and connect to the Operations Manager root management server.

9. In the Administration pane, click Product Connectors (SCOM SP1), or for Operations Manager 2007 R2, click Products Connectors, and then click Internal Connectors.

clip_image014

10. In the Connectors pane, right click the name of the alert connector (Connector name configured in step 2) and select properties.

11. On the internal connector general properties page, click on Add in the Subscriptions sections

clip_image016

12. In the Product Connector Subscription Wizard dialog box, on the General page, in the Subscription Name field, type the name for this subscription

13. Click Next.

clip_image018

14. On the Approve groups page, select the OpsMgr groups that need to forward alerts to SCSM.

Click Next.

clip_image020

15. On the Approve targets page, click Next if you want to forward all alerts from all targets.

clip_image022

16. If detailed alert information needs to be forwarded, select the Forward only alerts with targets explicit… option and click Add

Targets can be selected OpsMgr targets lists, click Ok when finished and Next on the Approve targets page.

clip_image024

17. On the Criteria page, select the criteria for alert forwarding. Click Create.

(On this page you can select witch alerts you want to forward to the Service Manager)

clip_image026

18. The just created Subscription is added to the subscriptions list. Click Ok to close the properties page.

clip_image028

Job is done in the OpsMgr console.

 

Review Configuration in the SCSM console

19. Go back to you SCSM console and navigate to the “Work Items” pane.

20. Expand “Work Items” –> “Incident Management” and click on “All Open OM Incidents

In the results pane you can see the forwarded alerts from OpsMgr (can take some time before the console is updated with the forwarded alerts)

clip_image030

All done…

(This can be further extended with automatic ticket assignment and notification, but that is for another blog…)

 

Enjoy,

 

Kurt Van Hoecke

http://www.linkedin.com/in/bunkco

 

This is a second post in the importing data into SCSM series:

Part 1: (Importing data into SCSM (part 1) – the SCSM AD & SCCM connectors)

Avatar of kurtvh

by kurtvh

Importing data into SCSM (part 1) – the SCSM AD & SCCM connectors

10:40 pm in Uncategorized by kurtvh

The Service Manager database contains information about the environment. After a fresh installation, we have an empty database. This SCSM database can be easily populated with different entries (configuration items for SCSM) with the use of connectors. In the SCSM console, you have four different connectors that can be configured.

clip_image002

Active Directory Connector: This connector enables the import of users, groups, printers, and computers from Active Directory as configuration items (CI) into the Service Manager database. Complete domain, OU or a selection of different objects are source configurations that can be set during installation of the connector.

Configuration Manager Connector: This connector enables the import data from Microsoft System Center Configuration Manager 2007 Site Database into the System Center Service Manager database. The ConfigMgr connector can enable a couple of functions:

– Importing assets by using a Configuration Manager Connector can add details about a configuration item that has already been imported by using an AD Connector, or add new configuration items that do not exist in Active Directory.

– Importing configuration baselines from ConfigMgr and then use that to automatically generate incidents for non-compliant configuration items.

Operation Manager Alert Connector: The OpsMgr alert connector is used to automatically generate incidents that are based on Operations Manager alerts.

Operation Manager CI Connector: The CI connector imports discovered objects from Operation Manager as configuration items into the SCSM database.

This first blog post will cover the installation and configuration of the AD & ConfigMgr connector.

Installation of the Active Directory Connector

Pre-requisites:

– Connector account with read rights in Active Directory

Installation of the connector

In the Service Manager console, click Administration.

In the Administration pane, expand Administration, and then click Connectors.

In the Tasks pane, under Connectors, click Create Connector, and then select Active Directory Connector.

clip_image004

The Active Directory Connector Wizard starts…

On the Before you Begin page, click Next.

clip_image006

On the General page, in the Name box, type a name for the new connector. On this page, we can enable or disable the connector.

clip_image008

On the Domain or Organizational Unit page, we have two configuration options:

– Select Use the domain: <domain name> for complete domain import

– Or select Let me choose the domain or OU and then click Browse to choose a domain or an organizational unit (OU) in your environment. (I have selected a specific OU “Accounts” in this example setup.)

In the Credentials area, click New or select an existing Run As account from the drop down list.

Configuration made on this page can be tested using the Test Connection button.

clip_image010

On the Objects page, we can configure the connector to import “All computers, printers, users, and user groups” or alternatively to import only selected items with selecting “Select individual computers, printers, users or user groups”.

clip_image012

On the Summary page, make sure that settings are correct, and then click Create.

On the Completion page, make sure that Active Directory Connector successfully configured appears, and then click Close.

clip_image014

Go back to the Administration pane, expand Administration, and then click Connectors.

Select the just created AD connector and navigate to the Tasks pane, under AD Connector, click Synchronize Now.

Wait a few moments and you can see that the discovered objects from AD are imported as configuration items in SCSM. To check the import, just navigate to the Configuration Items in the SCSM console, expand Configuration Items and select for example All Computers. The CI’s are listed in the results pane.

clip_image016

(Example of the imported Configuration items)

Next step is to configure the Configuration Manager Connector. This will import more meta-data information for the imported configuration items from AD. (or add new configuration items)

Installation of the ConfigMgr Connector

The following procedure can be used to import data from ConfigMgr 2007.

Pre-requisites:

– Connector account that must be a member of the smsdbrole_extract and the db_datareader groups on SCCM site database.

Installation of the connector

In the Service Manager console, click Administration.

In the Administration pane, expand Administration, and then click Connectors.

In the Tasks pane, under Connectors, click Create Connector, and then select Configuration Manager Connector.

clip_image018

On the Before you Begin page, click Next.

On the General page, in the Name box enter a name for the new connector and provide a description if needed. On this page, we can enable or disable the connector.

clip_image020

On the Select Management Pack page, in the Connector Management Pack list, select System Center Configuration Manager Connector Configuration, and then click Next.

clip_image022

On the Connect to System Center Configuration Manager Database page, specify the name of your SCCM server and the name of the SMS database.

In the Credentials area, click New or select an existing Run As account from the drop down list.

Note: Account must have rights in the SCCM database to import object information like it is specified in the pre-requisites.

clip_image024

On the Collections page, select the appropriate collection, and then click Next. I have enabled the configuration for “All Systems” collection. This can be changes at a later stage…

clip_image026

On the Schedule page, in the Synchronize list, set how often, and at what time, synchronization should occur, and then click Next.

clip_image028

On the Summary page, confirm the connector settings you made, and then click Create.

On the Confirmation page, make sure that You have successfully completed the System Center Configuration Manager Connector Wizard is displayed, and then click Close.

clip_image030

Go back to the Administration pane, expand Administration, and then click Connectors.

Select the just created SCCM connector and navigate to the Tasks pane, under SCCM Connector, click Synchronize Now.

In production environments where many objects are defined in ConfigMgr, it can take several hours to complete the import. A status of the import procedures is displayed on the connector result pane.

clip_image032

When the import is finished, we have detailed information available on the objects imported via the AD connector.

To check the import, just navigate to the Configuration Items in the SCSM console, expand Configuration Items and select for example All Computers. The CI’s are listed in the results pane. You can see that after the import a more exhaustive list of information is available for each configuration item.

clip_image034

Next blog post will cover the configuration of the OpsMgr connectors…

Enjoy,

Kurt Van Hoecke

http://www.linkedin.com/in/bunkco