You are browsing the archive for System Center Service Manager.

Avatar of kurtvh

by kurtvh

Service Manager management servers in NLB

2:31 pm in Service Manager by kurtvh


The following procedure will guide you through the installation and configuration of the Network Load Balancing functionality with multiple Service Manager management servers.

Network load balancing in Windows Server 2008 lets you to configure a pool of computers so that they take turns responding to requests. In Service Manager, the initial Service Manager management server you deploy is the server that processes workflows. You can deploy additional management servers to provide fail-over for a failed initial management server and to provide load balancing for handling Service Manager console.

As a minimum, you have to deploy an initial Service Manager management server, the management server that hosts the workflow processes, and at least one additional Service Manager management server. You can always install more management servers in your environment, for example to have a dedicated workflow mgmt server, and exclude them from the NLB cluster.


Installation information of the SCSM environment can be found here:

Installation of the NLB feature in server 2008 (R2):

  • Click Start, click Administrative Tools, and then click Server Manager. In the Features Summary area of the Server Manager main window, click Add Features.
  • In the Add Features Wizard, select the Network Load Balancing check box and confirm the installation.
  • Click Install.


To create a new NLB cluster

  • To open Network Load Balancing Manager, click Start, click Administrative Tools, and then click Network Load Balancing Manager.
  • Right-click Network Load Balancing Clusters, and then click New Cluster.
  • To connect to the host that is to be a part of the new cluster, in the Host text box, type the name of the host, and then click Connect.
  • Select the interface that you want to use with the cluster, and then click Next. (The interface hosts the virtual IP address and receives the client traffic to load balance.)


  • In Host Parameters, select a value in Priority (Unique host identifier). This parameter specifies a unique ID for each host. The host with the lowest numerical priority among the current members of the cluster handles all of the cluster’s network traffic that is not covered by a port rule. (You can override these priorities or provide load balancing for specific ranges of ports by specifying rules on the Port rules tab of the Network Load Balancing Properties dialog box. )


  • Click Next to continue.
  • In Cluster IP Addresses, click Add and type the cluster IP address that is shared by every host in the cluster. NLB adds this IP address to the TCP/IP stack on the selected interface of all hosts that are chosen to be part of the cluster.


  • Click Next to continue.
  • In Cluster Parameters, select values in IP Address and Subnet mask. Type the full Internet name that users will use to access this NLB cluster.
  • In Cluster operation mode, click Unicast to specify that a unicast media access control (MAC) address should be used for cluster operations. In unicast mode, the MAC address of the cluster is assigned to the network adapter of the computer, and the built-in MAC address of the network adapter is not used. It is recommended that you accept the unicast default settings.


  • Click Next to continue.
  • In Port Rules, click Edit to modify the default port rules. SCSM console make connection to port 5724. In this example only this network traffic is load balanced.


  • Wait until the NLB configuration is set on the first NLB member
    • Review log entries below the NLB mgmt console.
    • Status of the first NLB cluster member should be “Converged”.
  • To add more hosts to the cluster, right-click the new cluster, and then click Add Host to Cluster. Configure the host parameters (including host priority, dedicated IP addresses, and load weight) for the additional hosts by following the same instructions that you used to configure the initial host. Because you are adding hosts to an already configured cluster, all the cluster-wide parameters remain the same.


  • Same procedure, wait until the NLB configuration is set on the first NLB member
    • Review log entries below the NLB mgmt console.
    • Status of the first NLB cluster member should be “Converged”.

Job done, in normal cases you should be able to connect the mgmt console to the virtual NLB name.


Some attention points that can help debugging failure of connection.

  • Security rights, of course you need to have the needed rights in SCSM to connect. No special configuration on this topic. If you can connect to the physical name you should also be able to connect to the virtual name.
  • Network issues can block the connection to the management servers. Work together with the network team to solve firewall,switch,… issues.
  • You need to manually configure the DNS A record for resolving the virtual name.
  • SPN registration: additional Kerberos SPN registration for the virtual NLB cluster name to the SDK account is required to make Kerberos working in the clustered environment. (MSOMSdkSvc/Netbios name & FQDN – Otherwise NTLM authentication is used)

Have fun,

Kurt Van Hoecke

Technorati Tags: ,,

System Center Service Manager 2010 Unleashed Book is up on Amazon for Pre-order

7:26 am in Uncategorized by The WMI guy


The Service Manager 2010 Unleashed book is up on Amazon for Pre-order !

I hope you will enjoy reading it and find a lot of interesting information in it.

Alexandre Verkinderen

Avatar of kurtvh

by kurtvh

System Center Service Manager 2010 International RTM!

8:58 pm in Uncategorized by kurtvh

Microsoft has announced that SCSM 2010 International RTM is available! This release contains the localized version of SCSM 2010 and supports the following languages:

  • Chinese (simplified)
  • Chinese (traditional)
  • English
  • French
  • German
  • Italian
  • Japanese
  • Korean
  • Portuguese (Brazilian)
  • Russian
  • Spanish

180-days evaluation version download link to Microsoft download site.

Important note:

A single installation of the international version of SCSM supports all the languages listed above.  SCSM Console uses the OS Display Language setting and SCSM Portal uses the Browser’s Encoding setting to render the contents in the appropriate language.

Important information about this release:

Frequently Asked Questions about the SCSM 2010 International.

Some highlights:

  • It is not possible to upgrade from English to the International version of SCSM.
  • Starting from SCSM 2010 Service Pack 1, Microsoft is going to ship English and International versions of SCSM as one version of the product (sim-shipping)
  • The language of the server OS (SKU & OS Display Language) doesn’t impact the language of the client (console/browser) UI on the separate client computer.
  • Windows Client can be in any language (SKU & Display Language) supported by Windows Client OS
  • Language SKUs should be the same for all SQL Servers used for SCSM SM Servers and Data Warehouse
  • All SCSM SQL Servers (SMDB and DW) must have the same collation setting from the list of supported SQL Collations.
  • Read more from Microsoft Team blog – URl above


Have Fun,


Avatar of kurtvh

by kurtvh

Service Manager Self-Service Portal Error: Server Error in ‘/’ Application

7:15 pm in Uncategorized by kurtvh

I’ve encountered the following error after installing a fresh SCSM 2010 RTM environment.The following error was displayed when accessing the Self-Service portal (EndUser & Analyst):


Environment statistics:

  • Server 2008 R2 64bit with SCSM management server and Self-Service portal installed on the same server.
  • Pre-requisites for Self-Service portal installed
    • Microsoft Internet Information Services 7 with IIS 6 metabase compatibility installed – ASP.NET 2.0
    • I have an SSL certificate installed and configured.
  • Account used to install Self-Service portal
    • Is local administrator on the Service Manager management server and SQL Server 2008.
    • Is SQL Server system administrator.
    • Is the account specified for Service Manager services during setup of the Service Manager management server.


The error message indicates that a virtual directory is configured and should be configured as an application in IIS. EndUser & Analyst self-service portal folders (and no IIS applications) are visible when browsing to the corresponding web site in IIS. The followings steps have solved the issue in this case:

  • In IIS there is the possibility to convert folder to an application. Right click on the EndUser SCSM portal folder and select “Convert to application”


  • The following pop-up is displayed. Make sure that the correct Application Pool is specified in the “Add Application” pop-up.


  • Do the same for the Analyst folder.
  • After these conversions the SCSM portal should be up-and-running again…
    • If not, check that the correct account is used in the SM Application Pool. (Same as the SM Service account…)


Hope this helps!



Avatar of kurtvh

by kurtvh

Service manager @ MMS 2010 – Service Manager Partner Solutions

9:28 pm in Uncategorized by kurtvh

This blog post provides a brief overview of the partner solutions that are presented at MMS. The session “Beyond Service Manager Partner Solutions” was a nice overview of the partner solution around SCSM. Some of them are already available or will be soon (check partner website for availability).

Beyond Service Manager Partner Solutions

  • Provance IT Asset Management Pack: With this SCSM add-on IT service Management (ITSM) and IT Asset Management (ITAM) are integrated in one management console. SCSM CMDB captures IT asset information to support both ITAM and ITSM processes, giving Analysts a broad set of CI information to realize various objectives. The IT Asset Management Pack adds following new capabilities in SCSM: 
    • IT Asset Life Cycle Management for controlling IT costs and effectively managing hardware and software through the entire life cycle, from receipt to disposal.
    • Software Asset Management and License Compliance for identifying over and under licensed software titles, thus minimizing software costs and maintaining license compliance
    • Supplemental cost, contract and organizational information for supporting decision making, resulting in more efficient and cost effective IT Service Management
  • Infront Consulting Group: Infront has developed an AlarmPoint connector for SCSM. This connector automatically forwards notifications (like approvals) to the AlarmPoint notification engine. This SCSM add-on was included in an MMS demo were change approval was forwarded to a mobile device and the “manager” approved the change request from his mobile…
  • Savision live maps v5 for System Center Service Manager: This integrated solution provides the functionality in SCSM to dynamically build and access Savision service maps.
  • Bay Dynamics: IT Analytics for System Center leverages advanced business intelligence and analytics technology to enable SCSM Analysts to maximize the value of the data that resides within System Center Service Manager databases by providing multidimensional ad-hoc analysis, Key Performance Indicators, and robust graphical trending. Features included:
  • Atea Spintop accelerator for Service Manager: This SCSM add-on provides:
  • SVT Audit Manager: SVT Audit Manager is an integrated auditing solution for Microsoft System Center comprised of tools, knowledge and guidance focused on optimizing IT GRC auditing for regulations such as Sarbanes-Oxley, HIPAA, ISO, COBIT, PCI DSS and FISMA.
    • SVT Audit Manager fully leverages the Operations Manager 2007 architecture to provide a unified application and systems performance management and now, an enterprise security auditing solution allowing organizations to consolidate and reduce silos of information, point solutions, manual procedures, reducing the overall cost of meeting today’s complex regulatory requirements
    • Integration with Service Manager further enhances SVT Audit Manager with key security related incident management processes as well as risk, program and change control workflows and automation, all of which help to ensure regulatory alignment and reduced corporate security exposure.
  • Absolute Software System Center Service Manager Management Pack: BIOS-enabled security from Absolute Software’s Computrace platform
    • Computrace Data Protection: Remote data delete
    • Intel Anti-Theft platform disable
    • Computrace call history / statistics from within SCSM UI
  • Service Mgr 2010 Features for Intel Core vPro Processor Family: KVM Remote Control & Power Control
    • KVM Remote Control allows an authorized IT Technician to remotely control the keyboard, video, and mouse of a remote PC independent of OS State
    • Ability to remotely interact with remote remediation images booted through IDE Redirection
    • Implement AMT Power control directly into Service Manager workflow to automated IT business processes.

I will try to keep an eye on the partner solutions that get available and update this blog post accordantly.

Have fun,

Kurt Van Hoecke

Avatar of kurtvh

by kurtvh

Service manager & Opalis @ MMS 2010 – day 1

4:55 pm in Uncategorized by kurtvh

First day of MMS was completely filled with instructor labs.

A very nice instructor lab was the “Data Warehouse and Reporting in System Center Service Manager 2010

  • A more or less complete overview of how to access, use and integrate the Service Manager reports via a variety
    of means. A little overview what was covered in the lab: 
    • Accessing reports via from the Service Manager console and a web browser:
      • Performing and saving simple report customizations from the Service Manager console
    • Creating and deploying a custom report based on the Service Manager data warehouse.
      • Using SQL Server Business Intelligence Development Studio or with Report Builder
      • PowerPivot for Excel (add-in to Excel 2010: )
    • Integrating reports into SharePoint and customizing them for optimal usability within SharePoint
      • Create a simple dashboard within SharePoint
    • Review and manage the datawarehouse jobs using Powershell cmdlets
      • Get-SCDWJob
      • Get-SCDWJobSchedule
      • Set-SCDWJobSchedule
  • Check out Maarten Goet his blog, he did a presentation about this topic in MMS and will post his queries from the presentation. These can be used as a basis for further report creation… ( )
  • This lab proofs the strong reporting capabilities in service manager. I will certainly go deeper in this topic in future blogs.


Another instructor lab was the “Introduction to Opalis

  • The goal of the lab was to provide a basic introduction to the Opalis Integration Server architecture and functionality, as well as the process of creating and running Policies.
  • Basic integration packs are used in this lab. Upcoming integration packs – Q2 2010 (aug):
    • Microsoft Configuration Manager
    • Microsoft Virtual Machine Manager
    • Microsoft Data Protection Manager
    • Microsoft Service Manager

More information is following…



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


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

Register fast, seats are limited!

Alexandre Verkinderne

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


Part II


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



To download, simply go to the Service Manager site on Connect 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 (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.


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


– 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.


The Active Directory Connector Wizard starts…

On the Before you Begin page, click Next.


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.


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.


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”.


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.


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.


(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.


– 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.


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.


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


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.


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…


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


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.


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.


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.


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


Kurt Van Hoecke