Showing posts with label System Center Service Manager Beta1. Show all posts
Showing posts with label System Center Service Manager Beta1. Show all posts

21 February 2009

Configuring Email Notification channel in Service Manager

Extremely straightforward and simple.


  • Logon to your Service Manager Console
  • Go to the Administration space and expand the Administration -> Notification node
  • Click on the Channels node
  • On the Middle pane, select Email Notification Channel and click the Edit link on the right pane
  • This will launch the Email Notification Settings window
  • Tick on the Enable e-mail notifications checkbox. Click on the Add button to launch the Add SMTP Server window
  • Input your mail server settings and click OK.
  • Enter the Return Address and click OK again to save your settings and now you have added your email notification channel.

19 February 2009

pre-Reqs for Service Manager

For those who are like me who just wouldn't be interested in reading installation notes and eventually got burnt. I will be kind enough to share this with

you after having my hands charred a couple of times.

One of the key pre-Reqs when you want to install and configure Service Manager is to get you action accounts configured properly. Here I have copied

excerpts from the Initial Config guide and let it be our light ...

1) Create an Active Directory group of users that will be assigned to the role of Service Manager administrators of both the data warehouse and Service Manager management groups. For example, create the group SM_Admins. This group of users must be in the same domain that Service Manager is in. Users from any other domain, even child domains, are not supported.

2)For the account you use to run Setup, verify the following:

  • Must be a SQL Server sysadmin on the SQL server where you install the databases.
  • Must be a member of the data warehouse management group administrators. For example, add this account to the SM_Admins group.
3)Identify or create a domain account that will be used for the Service Manager account. For example, create the domain account SM_Acct.
  • This account must be in the same domain that Service Manager is in. Accounts from any other domain, even child domains, are not supported.

4) For the domain account, for example, SM_Acct, make sure of the following:


  • The domain account is a member of the group you created in step 1. For example, make the domain account SM_Acct a member of the SM_Admins group.
  • The domain account is a member of the local administrator group on the computer that will host the Service Manager management server and the data warehouse server.
  • The domain account is a member of the sysadmin role for the data warehouse SQL Server as well as for the Service Manager database SQL ServerThe domain account is a member of the Content Manager role (or higher) in SQL Server Reporting Services.
5)Make sure that the SQL instances used for Service Manager databases are using port number 1433.
6)If you are installing the databases on a remote computer running SQL Server, the computer account (for
example, $) of the computer you are running Setup on must be a local administrator on the SQL Server computer.

18 February 2009

How do I know whether my Active Directory Connector successfully sync data ?

One of the key configuration activity that you need to do when you setup Service Manager Beta 1 is to import objects from Active Directory into Service Manager. This can be achieved via the Active Directory connector which will act as the synchronization engine between both components.

However regardless whether it's is successfully synchronized or not, you will always get a successful sync message.


But then, my objects is still not synchronized? So what is the problem ? How do I know whether it is an error or synchronization is still running ?

To have a detailed view on what happened and whether the synchronization is successful, go over to Event Viewer and open the Operations Manager log.
(Yes, Service Manager uses the same framework/engine model as Operations Manager R2)

Find events where the Event Source is "Lfx Service" and if there is an error you will be able to see something like this:


By now, you should be able to see what is the details of the error for the synchronization process.