You are browsing the archive for service level dashboard.

Avatar of alkin

by alkin

MMS 2010 Keynotes

7:25 am in Uncategorized by alkin

The MMS 2010 keynotes are available online!


KEY1 Managing Systems from the Datacenter to the Cloud

Bob Muglia, President of Microsoft Server and Tools Business, returns to speak at this year’s event. Since MMS 2009, the buzz in the IT industry about cloud computing has continued to grow. There are many different perspectives on the cloud, its capabilities, its enablers and what it means to the world of IT operations and systems management. Get Bob Muglia’s perspective on what cloud services mean for the datacenter, what you can do today with these services, and how your approach to cloud services can help you change your company’s IT operations for the better.



KEY2 User Centric Client Management

Unify. Simplify. Control. Get inspired as Brad Anderson, Corporate Vice President of the Management and Services Division at Microsoft, returns to speak on user-centric client management. Listen in as Brad gives his perspectives on the rising need for a more user-centric approach to client management and discusses the technologies and roadmap Microsoft is delivering to help you get there. Learn what you can do today with the hottest technologies in client management like desktop virtualization and cloud computing to deliver user-centric services while lowering your overall TCO and improving your business processes. Hear how you can use these technologies to dramatically simplify client management while you unify your client environment to drive lower costs and improve services.


Avatar of alkin

by alkin

Session Recording Using System Center Operations Manager to monitor your SharePoint environment.

7:00 pm in Uncategorized by alkin

SESSION RECORDING Using System Center Operations Manager to monitor your SharePoint environment

System Center Operations Manager 2007 is THE end to end Monitoring Solution. In this session we will discuss what you, as SharePoint guys, find relevant to be monitored.
System Center Operations Manager uses a SharePoint Monitoring toolkit for monitoring the SharePoint Environment. This toolkit consists of a set of System Center Operations Manager 2007 management packs designed to help IT pros monitor their WSS 3.0 and MOSS 2007 and 2007 SP1 environments. These newly released packs were engineered to take advantage of SCOM 2007’s features, including new and improved reporting, additional actions, new views, and integrate IIS and SQL health rollup for a better understanding of the system-level dependencies of the SharePoint environments.
And last but not least: System Center Operations Manager can also emulate end user experience by monitoring a Web Application. We will show you how to monitor a Web Application, even if it is require credentials, and how to record a browser session.





Download Here


Have Fun,

Alexandre Verkinderen

Avatar of alkin

by alkin

Opsmgr Service Level Dashboard for Exchange 2007

2:31 pm in Uncategorized by alkin

It is possible to create custom reports for Exchange 2007 using the Service Level Dashboard Solution Accelerator and the Exchange 2007 Management Pack. The Opsmgr Team made a nice guide on how to make a Service Level Dashboard for Exchange.


But you have to change the Monitor dependency of the distributed applications otherwise the Health wouldn’t rolling up.


1. In the monitoring section of the console, under “Distributed Applications”, right-click on the “Exchange 2007 Server Availability” distributed application that you defined and select to open the Diagram View

2. Right-click on Exchange 2007 CAS Servers and select “Health Explorer”.

sshot-1 (2)

3. Right-click on Component Group Health Roll-up for type Ex. Client Access Servers and select “Monitor Properties”.

4. On the Monitor Dependency tab, click “MOM 2005 Computer Role Health” and click ok. This will allow health to roll up to the Component Group level. By default, health of converted Management Packs rolls up via MOM 2005 Computer Role Health.

sshot-1 (3)


But now come the tricky part. The state of you distributed applications will stay on unmonitored until a state change occurred for state to start rolling up.

sshot-1 (4)


The solution for this problem is just to put your exchange servers in maintenance mode for a while!



That’s how I resolved the unmonitored issue for my service level dashboard.



Alexandre Verkinderen


After the maintenance mode my

Avatar of alkin

by alkin

Define a Health Criteria for your web application Monitor Part III

9:52 pm in Uncategorized by alkin

W’re almost at the end! :-) Only 3 steps left. First we have to define a healt criteria for our web appliction and after that we can create our distributed appliction that will drive ou service level dashboard.


Use the Web Application Editor to choose what conditions will cause an error or warning during a synthetic transaction. For the Service Level Dashboard, an error is equivalent to an availability exception, and a warning is equivalent to a performance exception. Availability exceptions will also affect performance reporting. You can also choose to generate an alert when the status changes. For example, if your transaction includes a request to a specific Web page, you can choose to generate an alert if the page is unavailable. This is done by changing the health status of the transaction when the HTTP status code is 404.

Synthetic transactions are created by recording a Web site or by manually creating requests. For more information about recording a Web site, see How to Capture a Web Application Recording in Operations Manager 2007. For more information about manually creating or editing individual requests, see

How to Create or Edit a Request in Operations Manager 2007.

To set health criteria for a request in a Web monitoring session

1. Open the Authoring pane.

2. Expand Management Pack Templates, and then click Web Application.

3. Select the object you want to edit, and then click Edit Web application settings.

4. In the Request Details pane, you can set criteria to generate an error or warning health state for the request. For example, select the Http Status Code check box, and then select Equals and 404 to change the status when the page is not found.


5. If you want an alert generated when the health status changes, select the Generate an alert if any error criteria is met or Generate an alert if any warning or error criteria is met check boxes.

6. If you want the transaction to stop when an error or warning criteria is met, select the Stop processing the subsequent requests if any criteria is met check box.

7. Click Verify to test your changes.


8. After the changes are verified, click Apply, and then close the Web Application Editor.

Important   Repeat this process for every monitor that you create.


Next we will create a distributed appliction to drive the service level dashboard.



Alexandre Verkinderen

Avatar of alkin

by alkin

Configuring the Service Level Dashboard Part V

9:08 pm in Uncategorized by alkin

After you create your monitors and distributed applications, you must take some additional steps to configure the Service Level Dashboard group and service level goal properties. Discovery finds all the objects that are associated with a distributed application. The current setting of these attributes is displayed in the Service Level Dashboard Attributes view in the Operations Console. This view lists the distributed applications that can be shown on the Service Level Dashboard, their Dashboard group, and their current service level goals.







The distributed application name

Availability Service Level Threshold


The percentage of availability the application must achieve to be shown as in compliance with the availability service level

Performance Service Level Threshold


The percentage of performance the application must achieve to be shown as in compliance with the performance service level

Dashboard Group


The Dashboard Group setting controls which dashboard the model will display on. All applications are assigned a default setting of 1, which allows multiple dashboards to be created for multiple views of the applications, or for views of different applications.



The GUID of the distributed application


Change the Service Level Dashboard Attributes for an Application

To change the Service Level Dashboard attributes, use overrides.

To override Service Level Dashboard attributes for a distributed application

1. Open the Authoring pane.

2. Expand Management Pack Objects, and then click Object Discoveries.

3. In the Look for box, type SLDBase and then click Find Now.


4. Click Enterprise Service Monitoring Service Level Dashboard Discovery and then, in the Actions pane, click Overrides.


5. Click Override the Object Discovery and then click For a specific object of type: Service Level Dashboard Application.

6. In the Select Object box, select the distributed application that contains attributes you want to edit, and then click OK.

7. Select the Override check box next to the attribute you want to edit.


8. Enter the adjusted setting in the Override Setting column.

a. For Dashboard Group, enter an integer or a string.

b. For the Performance and Availability Service Level Thresholds, enter the uptime percentage in a decimal number, without any symbols.

9. Click OK.


Now that everything is configured we can start using our service level dashboard!



ALexandre Verkinderen

Avatar of alkin

by alkin

Creating the Distributed Application Models to Drive the Service Level Dashboard Part IV

9:06 pm in Uncategorized by alkin

The distributed application model interface provides a flexible way to customize the Service Level Dashboard display to your needs. The Service Level Dashboard accepts a simple distributed application model as its configuration for application listings and transaction groupings. This model allows you to group Web applications or other monitors on the Service Level Dashboard into applications and regions. You can define how the health rolls up to the component group and the application as a whole by editing the health rollup of the distributed application model.

Important   Note that these distributed application models are in addition to any distributed application models you might have already created for your applications. The Service Level Dashboard works only with a specific style of distributed application model—one that is based on the Service Level Dashboard Application template.

The Service Level Dashboard display shows three levels. The top level lists applications by their distributed application model names, the second level shows the component groups, and the third level lists the actual transaction names. Each level can contain several entries.


To create a distributed application model

1. In the Operations Console, click Authoring, right-click Distributed Applications, and then click Create a new distributed application.


2. In the Name box, type a name for the distributed application, which will appear on the Service Level Dashboard. In the Description box, you can type a description.

3. Under Template, select the Service Level Dashboard Application template.

4. In the Management Pack drop-down box, choose the management pack created in the previous steps from the list of unsealed management packs. (By default, the distributed application you create is saved to the Default Management Pack.) Or, click New to create a new management pack. Click OK.

To design your distributed application model

1. The diagram pane in the distributed application designer displays the component groups of your distributed application. You will see two component groups defined by the template: Component Group 1 and Component Group 2. Right-click each component group to review it. If necessary, edit the object types that are included in your distributed application, and modify the name. On the toolbar, click Add Component to create a new component group. Component groups are generally used to define regions or other groups of transactions on the report.

2. The buttons at the bottom of the Objects pane list all object types that are defined by the template you chose earlier. If your distributed application does not contain one or more of the components shown in the list, click Organize Object Types to view a list of all currently included object types. Clear the check box for any object type that is not part of your distributed application.

3. Click each of the remaining buttons at the bottom of the Objects pane to view the objects that are listed in each. By default, the list contains all the discovered objects on your network that are of that object type.

4. Right-click each object that is a component of your distributed application, point to Add To, and then click the name of the component group to which this object belongs. (These objects may be the Web monitors defined earlier, or other types of objects that you want to display on the Service Level Dashboard at the transaction level. Any item in the component group displays as a transaction, with its health state calculated.) Click Save.


5. To configure the health rollup of the distributed application (and by extension the Service Level Dashboard), in the Component Group Details pane, click the Configure health rollup link, and create an override for the rollup algorithm for the component group (or entire model) that rolls up in the manner expected.

6. To save the distributed application to a management pack, click Save.


After you create your monitors and distributed applications, you must take some additional steps to configure the Service Level Dashboard group and service level goal properties.


Alexandre Verkinderen

Visit Us On TwitterVisit Us On Linkedin