monitoring windows server systems demo script

Chapter 3 Microsoft Confidential Chapter 4 – Microsoft Internal Use Only

TechNet Q3 FY09Q3 FY09

SRV-303Monitoring Windows Server Systems

Level 300

Demo Script

TechNet Field Event Content SRV-303


CONTENTS

BEFORE YOU BEGIN...........................................................................................................................1

SEND US YOUR FEEDBACK ABOUT THIS SECTION........................................................................................................................................................ 1

DEMO 1: CONFIGURING USER ROLES...................................................................................................2

DEPLOY AGENTS TO WINDOWS SERVER 2008 SYSTEMS............................................................................................................................................ 2CONFIGURE USER ROLES..................................................................................................................................................................................... 3SEND US YOUR FEEDBACK ABOUT THIS DEMONSTRATION............................................................................................................................................. 6

DEMO 2: CONFIGURING NOTIFICATIONS..............................................................................................7

ENABLE AN E-MAIL NOTIFICATION CHANNEL............................................................................................................................................................ 7CREATE A NOTIFICATION RECIPIENT........................................................................................................................................................................ 7CREATE A NOTIFICATION SUBSCRIPTION.................................................................................................................................................................. 8VERIFY THAT NOTIFICATIONS ARE BEING SENT......................................................................................................................................................... 9SEND US YOUR FEEDBACK ABOUT THIS DEMONSTRATION........................................................................................................................................... 10

DEMO 3: USING MANAGEMENT PACKS...............................................................................................11

IMPORT MANAGEMENT PACKS............................................................................................................................................................................. 11VIEW RULES AND KNOWLEDGE IN THE WINDOWS SERVER 2008 BASE MANAGEMENT PACK............................................................................................14SEND US YOUR FEEDBACK ABOUT THIS DEMONSTRATION........................................................................................................................................... 15

DEMO 4: MONITORING WINDOWS SERVER.........................................................................................16

MONITOR WINDOWS SERVER SYSTEMS TO SEARCH AND FILTER DATA........................................................................................................................16CREATE A UNIT MONITOR................................................................................................................................................................................... 17SEND US YOUR FEEDBACK ABOUT THIS DEMONSTRATION........................................................................................................................................... 18

DEMO 5: INVESTIGATING AND RESOLVING ALERTS............................................................................19

INVESTIGATE WINDOWS SERVER 2008 PRINT SERVER ALERTS..................................................................................................................................19INVESTIGATE TERMINAL SERVICES CONNECTION ISSUES............................................................................................................................................ 20MONITOR SYSTEM CENTER CONFIGURATION MANAGER............................................................................................................................................ 23SEND US YOUR FEEDBACK ABOUT THIS DEMONSTRATION........................................................................................................................................... 25

DEMO 6: CREATING OPERATIONS MANAGER REPORTS.......................................................................26

CREATE A REPORT MODEL................................................................................................................................................................................. 26CREATE A NEW REPORT IN REPORT BUILDER......................................................................................................................................................... 28

TechNet Field Event Content i SRV-303


SEND US YOUR FEEDBACK ABOUT THIS DEMONSTRATION........................................................................................................................................... 29

DEMO 7: CONFIGURING SERVICE-LEVEL DASHBOARDS.......................................................................30

CREATE THE WEB APPLICATION MONITOR............................................................................................................................................................. 30ADD A RECORDING TO AN EXISTING WEB APPLICATION OBJECT.................................................................................................................................31CREATE THE DISTRIBUTED APPLICATION MODEL..................................................................................................................................................... 32CHANGE THE SERVICE-LEVEL DASHBOARD ATTRIBUTES FOR AN APPLICATION...............................................................................................................33SEND US YOUR FEEDBACK ABOUT THIS DEMONSTRATION........................................................................................................................................... 34

TechNet Field Event Content ii SRV-303


Chapter 1 Before you begin 1. The password for the images is Password1.2. Turn on SEA-DC-01, and log on as Contoso\Administrator.3. Turn on SEA-SCOM-01, and log on as Contoso\OpsMgrAdmin.4. Turn on SEA-SCCM-01, and log on as Contoso\Administrator.5. Turn on SEA-WRK-001, and log on as Contoso\Administrator.6. On SEA-DC-01, if a message appears about not being able to locate a license server, click the message.

a. In Terminal Services Configuration, double-click License server discovery mode.b. Click Check Names.c. Click OK twice.d. Close Terminal Services Configuration.

7. On SEA-SCOM-01, open Services and verify that the OpsMgr Config Service is started.8. On SEA-SCCM-01, open Services and verify that the SMS Agent Host is started.9. On SEA-WRK-001, open Services and stop the SMS Agent Host service.10.A note on Operations Manager alerts. During these demonstrations, we rely on alerts appearing for certain demos. The alerts do not always appear at the same time because they are laid out in the demo script and sometimes different alerts will appear first, depending on the timing. To alleviate this, the demos have been constructed to flow at a certain pace, along with the slide deck, so that the alerts have as much time as possible to appear. The hardware you run these VMs on may affect when alerts appear.

Chapter 2 Send us your feedback about this section.

We appreciate hearing from you. To send your feedback, click the following link and type your comments in the message body.

Note: The subject-line information is used to route your feedback. If you remove or modify the subject line, we may be unable to process your feedback.

Send feedback.

TechNet Field Event Content 1 SRV-303

mailto:[email protected]?subject=SRV-303(/1:IT%20Pro%20Content/2:Demonstration%20Script/3:v1.0/4:Customer/5:none/6:en-us)&Body=---Please%20type%20any%20comments%20here,%20leaving%20the%20subject%20line%20in%20place.%20All%20feedback%20must%20be%20in%20English.---%20


Chapter 3 Demo 1: Configuring User Roles In this demonstration, we will configure various user roles that have access to perform different tasks in Operations Manager. We will also review how to deploy Operations Manager agents through the Operations Console.

Chapter 4 Deploy Agents to Windows Server 2008 Systems

Speaker Script StepsYou can deploy agents in three different ways: using the MOMAgent.msi from command prompt, using the Agent Setup Wizard on the installation media, or from the Operations Console. In this demonstration, we will see how it is done with the Operations Console.

Perform these steps on SEA-SCOM-01.1. On the desktop, double-click Operations Console.

2. System Center Operations Manager 2007 opens. Maximize the window.

You can use the Discovery Wizard to install agents on the computers in your organization. There are three steps to complete this wizard.

3. At the bottom of the Navigation pane, click Discovery Wizard.

4. The Computer and Device Management Wizard appears. Click Next.

The first is to discover computers or network devices. There are two methods available to do this. Automatic computer discovery scans the domain the root Management Server is in for Windows-based computers.

5. The Auto or Advanced page appears. Point to Automatic computer discovery.

Advanced discovery allows you to specify criteria for the computers the wizard will return, such as computer names starting with SEA.

6. Point to Advanced discovery.

You can select which types of objects you want to discover, such as Servers and Clients, Servers Only, Clients Only, or Network Devices.

7. In the Computer & Device Types list, point to the options.

8. Click Servers & Clients.

If you selected Servers & Clients, you can select the Verify discovered computers can be contacted check box. This is likely to increase the success rate of agent deployment, but discovery can take longer.

9. Point to Verify discovered computers can be contacted.

10. Click Next.

You can locate the computers that you want to manage by either scanning or browsing Active Directory Domain Services or by typing the computer names.

11. The Discovery Method page appears. Click Configure.

12. The Find Computers dialog box appears. Click OK, and then click Next.

The account used to run the scan must have administrative privileges on the targeted computers. This account will also be used to install the agents on the managed computers.

13. The Administrator Account page appears. Click Other user account.

14. In the User name field, type Administrator.

15. In the Password field, type Password1.

If you select the local account option, the agent installation task will be 16. Point to This is a local computer account, not a domain



run as the local account, but the discovery task will be run using the Management Server Action Account.

account.

17. Click Discover.

For the purpose of this demonstration, all other computers in the environment already have agents installed, so this discovery will fail. If we did have computers to discover, then the next step of the wizard would allow you to select which ones you wanted to manage. After that, you could then configure the agent installation for the computers, and the agents would be installed.

If the task fails for a computer, click the targeted computer. The reason for the failure is displayed in the Task Output text box.

18. The Discovery is in progress page appears. Click Cancel.

It could take up to five minutes for this process to finish and there is no need to let it. You can cancel any time.

Chapter 5 Configure User Roles

Speaker Script StepsOperations Manager 2007 can monitor many types of applications in the enterprise. As the Operations Manager administrator, you want to limit access to monitoring data. Role-based security allows you to limit privileges that users have for various aspects of Operations Manager 2007.

In Operations Manager 2007, user roles assign the rights that are needed to access monitoring data and perform actions. User roles apply to groups of users that need access to perform actions on the same group of monitored objects. A user role is the combination of a profile and scope. A user can be a part of multiple roles, and the resultant scope is the union of all the user roles.

A profile determines the actions that an Operations Manager user can perform. Profiles have a defined set of rights, and you cannot add or remove any of these assigned rights.

Scope determines which objects you can view and perform actions on in Operations Manager 2007. A scope is composed of one or more Operations Manager groups.

1. In the Administration pane, under Security, click User Roles.

In Operations Manager 2007, operations—such as resolving alerts, running tasks, overriding monitors, creating user roles, viewing alerts, and viewing events—have been grouped into profiles, with each profile representing a particular job function.

2. In the details pane, point to the profiles.

The Operations Manager Administrators User Role uses the Administrator profile which includes the full privileges available in Operations Manager. In our environment, members of the Operations

3. In the details pane, right-click Operations Manager Administrators, and then click Properties.



Manager Administrators domain group have this user role assigned. 4. The Operations Manager Administrators - User Role Properties dialog box appears. Click OK.

Let's create a new user role using the Operator profile. 5. In the Administration pane, right-click User Roles, and then click New User Role | Operator.

The Operator profile includes a set of privileges designed for users who need access to alerts, views, and tasks. It grants members the ability to interact with alerts, run tasks, and access views according to their configured scope.

We will create a new group for Windows Server 2008 Operators.

6. The Create User Role Wizard - Operator Profile dialog box appears. In the User role name field, type Windows Server 2008 Operators.

7. Click Add.

For now, we will add the user Aaron Con to our new role. 8. The Select Users or Groups dialog box appears. In the Enter the object names to select field, type ACon, and then click OK.

9. Click Next.

On the Approve groups page, you can choose approved groups that are monitored by members of this role.

Groups, like other Operations Manager objects, are defined in Management Packs. In Operations Manager 2007, groups are logical collections of objects, such as Windows-based computers, hard disks, or instances of Microsoft SQL Server. Several groups are created by the Management Packs that are imported automatically during an Operations Manager installation. If these groups do not contain the monitored objects you need for a scope, you can create a group that does.

10. The Approve groups page appears. Point to Groups.

You can clear the parent group and then select individual subgroups, if you want to limit the groups that this user role can monitor.

We will only select the Windows Server 2008 groups to limit this user role to those servers.

11. Clear Contoso.

12. Select Windows Server 2008 Computer Group, Windows Server 2008 Core Computer Group, Windows Server 2008 Full Computer Group, and then click Next.

On the Approve tasks page, you can configure the approved tasks that members of this user role can run. The default is that all tasks are automatically approved.

13. The Approve tasks page appears. Point to All tasks are automatically approved.

You can also configure a subset of available approved tasks for this user role to limit the tasks they can perform.

14. Click Only tasks explicitly added to the Approved tasks grid are approved, and then click Add.

15. The Select Tasks dialog box appears. Scroll through the tasks, and then click Cancel.

16. Click All tasks are automatically approved, and then click Next.

On the Views page, you can configure the views that members of the Advanced Operators User Role can see. Just like with groups and tasks,

17. The Approve views page appears. Point to the two options on



the default is for all views to be approved, but you can configure a subset of available monitoring views for this role.

If you do not select All views are automatically approved, users assigned this role will not be able to open alert views from within Health Explorer.

this page, and then click Next.

We will now create our new Operators group. 18. The Summary page appears, click Create.

If we have a user who only needs access to reports, we could add them to the Operations Manager Report Operators User Role. This role includes a set of privileges designed for users who need access to reports. It grants members the ability to view reports according to their configured scope.

19. In the details pane, right-click Operations Manager Report Operators, and then click Properties.

20. The Operations Manager Report Operators - User Role Properties dialog box appears. Click Add.

Users assigned to this role can access all the reports in the Reporting Data Warehouse, including reports from applications such as Microsoft Exchange that use the Reporting Data Warehouse. Failure to restrict access to the Report Operator User Role can result in unintended information disclosure.

21. The Select Users or Groups dialog box appears. In the Enter the object names to select field, type CPhilips, and then click OK.

22. Click OK.

If we have users who only needed to view alerts and views, we can use the Read-Only Operator profile. It includes a set of privileges designed for users who need read-only access to alerts and views. It grants members the ability to view alerts and access views according to their configured scope.

23. In the details pane, right-click Operations Manager Read-Only Operators, and then click Properties.

24. The Operations Manager Read-Only Operators - User Role Properties dialog box appears. Click Add.

25. The Select Users or Groups dialog box appears. In the Enter the object names to select field, type JWood, and then click OK.

Members of this role do not have access to tasks and are not assigned rights to the Task Status view.

26. Click the Group Scope tab.

27. Click the Views tab.

28. Click OK.

Finally, we will create a Run-As Account that will be used for notifications in our next demonstration.

29. In the Administration pane, right-click Security, and then click Create Run As Account.

Run-As Profiles and Run-As Accounts are used to select users with the privileges needed for running rules, tasks, and monitors.

30. The Create Run As Account Wizard appears. Click Next.

You can select which type of authentication that the account provides. For this account, we want Windows authentication.

31. The General page appears. In the Run As Account type list, point to the options.

32. Click Windows.

We will name this account Notification Account. 33. In the Display name field, type Notification_Account, and then click Next.

The Windows Run-As Account page is used to specify attributes of the account you are creating. We will specify the OpsMgrNotification domain

34. The Windows Run As Account page appears. In the User name field, type OpsMgrNotification.



account and enter the password, as well. 35. In the Password and Confirm password fields, type Password1, and then click Create.

Now that we have created the Run-As Account, we need to associate it with a Run-As Profile. By default, there is already a profile called Notification Account.

36. In the Administration pane, click Run As Profiles.

37. In the details pane, right-click Notification Account, and then click Properties.

38. The Run As Profile Properties - Notification Account dialog box appears. Click the Run As Accounts tab.

We will add the Notification Account Run-As Account we just created and select the SEA-SCOM-01 server as the target computer.

39. Click New.

40. The Add Alternate Run As Account dialog box appears. In the Run As Account list, click Notification_Account.

41. Under Matching Computers, click SEA-SCOM-01.Contoso.com, and then click OK twice.

Chapter 6 Send us your feedback about this demonstration.



Send feedback.


mailto:[email protected]?subject=SRV-303%20Demonstration%201(/1:IT%20Pro%20Content/2:Demonstration%20Script/3:v1.0/4:Customer/5:none/6:en-us)&Body=---Please%20type%20any%20comments%20here,%20leaving%20the%20subject%20line%20in%20place.%20All%20feedback%20must%20be%20in%20English.---%20


Chapter 7 Demo 2: Configuring Notifications In this demonstration, we will configure notifications using the e-mail channel. We will enable the e-mail channel, create a notification recipient, configure a subscription, and then test to verify that the notifications are working.

Chapter 8 Enable an E-Mail Notification Channel

Speaker Script StepsOperations Manager 2007 can send a notification to operators as soon as an alert occurs. The first step is to configure a notification channel. We will configure an e-mail channel for this demonstration.

Perform these steps on SEA-SCOM-01.1. In the Administration pane, click Settings.

2. In the details pane, right-click Notification, and then click Properties.

3. The Global Management Group Settings - Notification dialog box appears. Select Enable e-mail notification.

We need to specify a SMTP server by typing the fully qualified domain name, the port number, and the authentication method.

4. For SMTP servers click Add.

5. The Add SMTP Server dialog box appears. In the SMTP server (FQDN) field, type SEA-SCOM-01.contoso.com, and then click OK.

We will also specify a return e-mail address that will appear on the e-mail notifications.

6. In the Return address field, type [email protected].

For the e-mail notification format, you can customize the e-mail subject and e-mail message with wildcard parameters, such as Alert Source and Alert Description.

7. Under Default e-mail notification format, click the arrow to the right of the E-mail subject field.

You can also specify the encoding type. 8. Point to Encoding. Click OK.

Chapter 9 Create a Notification Recipient

Speaker Script StepsNow that we have enabled the e-mail notification channel, and our notification account was created in the previous demo, we can create a notification recipient. A notification recipient defines when and to what devices notifications can be sent.

This recipient will be the Peter Waxman domain user.

1. In the Administration pane, right-click Recipients, and then click New Notification Recipient.

2. The Notification Recipient Properties dialog box appears. For the Notification recipient display name field, click the ellipses (…) button.

3. The Select Users or Groups dialog box appears. In the Enter the object names to select field, type PWaxman, and then



click OK.

You can specify a default schedule for when notifications can be sent to the recipient. For this demonstration, we will always send notifications.

4. Point to Only send notifications during specified times.

Now, we need to add any devices that will be used to receive notifications. In this case, we only have to add one for our e-mail channel.

5. Click the Notification Devices tab. Click Add.

6. The Create Notification Device Wizard appears. In the Notification channel list, click E-mail.

7. Click Next.

You can set separate delivery schedule for device or use the default you set previously for this recipient.

8. The Schedule page appears. Click Next.

Finally, we need to name the notification device. We will name this one Peter Waxman E-mail.

9. The General page appears. In the Notification device name field, type Peter Waxman E-mail, and then click Finish.

10. Click OK.

Chapter 10 Create a Notification Subscription

Speaker Script StepsNow that we have created a notification recipient, we can create a notification subscription. A subscriber can be an individual user account or a distribution list. We will name this subscription All Alerts.

1. In the Administration pane, right-click Subscriptions, and then click New Notification Subscription.

2. The Create Notification Subscription Wizard appears. In the Subscription name field, type All Alerts.

The Add Notification Recipient dialog box displays all notification recipients that were previously created. We will add the Peter Waxman recipient we just created.

3. For Recipients, click Add.

4. The Add Notification Recipient dialog box appears. Select CONTOSO\PWaxman, and then click OK.

5. Click Next.

You can limit the users that can subscribe to this notification subscription by selecting Available groups and classes filtered by role and then selecting a user role.

6. The User Role Filter page appears. Click Next.

By default, all groups are selected to receive notifications. If you want to limit the groups that receive notifications, clear the top-level group, and then select the groups you want.

7. The Groups page appears. Click Next.

You can filter notifications so that only notifications of selected object types are sent.

8. The Classes page appears. Click Next.



You can select the desired severity, priority, and resolution states that you want to receive notifications for. You can also select different categories. For the purpose of this demonstration, we will select all options to increase the chances of receiving a notification.

9. The Alert Criteria page appears. Select Warning, Information, and Low.

10. Click Next.

You can specify a period of time that an alert remains in the alert resolution state before a notification is sent.

11. The Alert Aging page appears. Click Next.

Finally, you can customize the format of the e-mail sent for notification. 12. The Formats page appears. Click Finish.

Chapter 11 Verify That Notifications Are Being Sent

Speaker Script StepsNow that the notification has been configured, we can create an alert to verify that it is working. We will stop the Operations Manager Health service on our Domain Controller.

Perform these steps on SEA-DC-01.1. On the desktop, double-click Services.

2. The Services window opens. Maximize the window.

3. Right-click OpsMgr Health Service, and then click Stop.

Our Operations Manager server also has the SMTP Server feature installed, so we can first look here to see if a notification has been sent.

Perform these steps on SEA-SCOM-01.4. Minimize System Center Operations Manager 2007.

5. On the desktop, right-click Computer, and then click Explore.

6. The Computer window opens. Maximize the window.

We can navigate to the drop folder for the SMTP server and see if any e-mails have been generated. It may take a couple of minutes before one appears.

7. Browse to C:\inetpub\mailroot\Drop.

8. In the details pane, point to the e-mail files.

It may take two or three minutes for an alert to be triggered. Any alert will work, so proceed once any e-mail files are present.

9. Close Computer.

Because Windows Server 2008 does not include POP or IMAP support, and Windows Mail can't read e-mail from standard SMTP queues, we can't show the e-mail being delivered to the client. We can open the .eml file on our workstation and show what it contains.

Perform these steps on SEA-WRK-001.10. On the desktop, double-click MailDrop.

11. The MailDrop window opens. Maximize the window.

12. In the details pane, double-click any .eml file

In the e-mail, we can see that it is from Operations Manager and that it was sent to Peter Waxman.

13. The Alert window opens. Maximize the window.

14. Point to From and To.

In the subject, we can see the alert information, which tells us what the alert is, the priority, severity, and the resolution state.

15. Point to Subject.

In the body of the e-mail, we see more detail about the alert and there is also a link to the alert view. The account that is currently logged in

16. Point to the body of the e-mail.



would need the appropriate permissions to open the alert view. 17. Close Alert, and then close MailDrop.

We will restart the OpsMgr Health Service on our Domain Controller. Perform these steps on SEA-DC-01.18. Right-click OpsMgr Health Service, and then click Start.

19. Close Services.




Send feedback.




Chapter 13 Demo 3 : Using Management Packs In this demonstration, we will import Management Packs for various products. We will also examine the rules and product knowledge in the Windows Server Base Operating System Management Pack.

Chapter 14 Import Management Packs

Speaker Script StepsBefore importing Management Packs, you need to review the documentation to see if the prerequisites, if any, have been meet. In the case of the Windows Server 2003 and Windows Server 2008 DNS Management Pack, there are a couple of requirements. If you have a previous version of this Management Pack installed, it should be removed. Also, the Windows Server 2008 Base Operating System Management Pack needs to be installed before you install the DNS Management Pack, which has already been done in our network.

Perform these steps on SEA-SCOM-01.1. Restore System Center Operations Manager 2007.

2. In the Administration pane, right-click Management Packs, and then click Import Management Packs.

3. The Select Management Packs to import dialog box appears. Browse to C:\Program Files\System Center Management Packs\ MICROSOFT Windows Server 2000 2003 and 2008 DNS MANAGEMENT PACK.

First, we’ll select DNS Server Library. This Management Pack contains all of the version-agnostic objects and monitoring logic for all supported versions of Windows DNS Server.

4. Click Microsoft.Windows.DNSServer.Library.mp, and then click Open. The Import Management Pack dialog box appears.

Then, we’ll select Microsoft Windows DNS 2008 Server. This Management Pack contains the additional monitoring logic necessary for the new features added in Windows Server 2008 DNS.

5. Click Add.

6. The Select Management Packs to import dialog box appears. Click Microsoft.Windows.DNSServer.2008.mp, and then click Open.

After the Windows Server DNS Management Pack is imported, we need to perform some additional steps to finish our initial configuration.

7. Click Import.

This process may take up to one minute to complete.

8. Click Close.

First, we need to create a new Management Pack for customizations. Most vendor Management Packs are sealed so that you cannot change any of the original settings in the Management Pack file. However, you can create customizations, such as overrides or new monitoring objects, and save them to a different Management Pack.

9. In the Administration pane, right-click Management Packs, and then click Create Management Pack.

10. The Create a Management Pack dialog box appears. In the Name field, type Windows Server 2008 DNS Custom.

It is an important best practice to tightly control the versioning of Management Packs by implementing a strict version number policy that is followed by all Management Pack authors in your environment.

11. Point to Version.

12. Click Next.

We could create an overview knowledge article for this Management Pack.

13. The Knowledge Article page appears. Click Create.



Next, we need to enable proxy discovery on every DNS managed node. It is essential for discoveries to function properly.

14. In the Administration pane, click Agent Managed.

15. In the details pane, right-click SEA-DC-01, and then click Properties.

This configures an Operations Manager 2007 agent-managed computer as a proxy for agentless managed computers.

16. The SEA-DC-01.Contoso.com - Agent Properties dialog box appears. Click the Security tab.

17. Select Allow this agent to act as a proxy and discover managed objects on other computers.

18. Click OK.

We will now import the Windows Server Print Server Management Pack. The Windows Server 2008 Base Operating System Management Pack must be installed before this Management Pack is installed.


20. The Select Management Packs to import dialog box appears. Browse to C:\Program Files\System Center Management Packs\Microsoft Windows Server Print Server MP for System Center Operations Manager 2007.

First, we will select Print Server Library. This Management Pack contains the generic class definitions for the various version-specific Print Server Management Packs. This Management Pack is a prerequisite for the version-specific Management Packs and must be imported before or at the same time as the version-specific Management Packs.

21. Click Microsoft.Windows.Server.PrintServer.Library.mp, and then click Open. The Import Management Pack dialog box appears.

Then, we will select Microsoft Windows Print Server 2008. This Management Pack defines the classes, discoveries, rules, and monitors required for monitoring the Print Server role on Windows Server 2008 systems. In addition, this Management Pack defines tasks and views.

22. Click Add.

23. The Select Management Packs to import dialog box appears. Click Microsoft.Windows.Server.PrintServer.2008.mp, and then click Open.

Just like the DNS Management Pack, you should create a Management Pack for any customizations you might configure with the Print Server Management Pack. For the purpose of this demonstration, we will not do this.

24. Click Import.


25. Click Close.

Next, we will import the Terminal Services Management Pack. This Management Pack also requires the Windows Server 2008 Base Operating System Management Pack. In addition, each type of terminal server must be managed by Operations Manager for this Management Pack to function optimally.


27. The Select Management Packs to import dialog box appears. Browse to C:\Program Files\System Center Management Packs\Terminal Services System Center Operations Manager 2007 MP.

The Terminal Services Library Management Pack is required for discovering objects, monitoring objects, and viewing information on computers running Windows Server 2008, Windows Server 2003, and Windows 2000 Server.

28. Click Microsoft.Windows.Server.TerminalService.Library.mp, and then click Open. The Import Management Pack dialog box appears.



The Terminal Services 2008 Management Pack is required for monitoring computers running Windows Server 2008.

29. Click Add.

30. The Select Management Packs to import dialog box appears. Click Microsoft.Windows.Server.TerminalService.2008.mp, and then click Open.

As with all sealed Management Packs, you should create a Management Pack for any customizations you might configure.

31. Click Import.


32. Click Close.

We will move on to the Microsoft System Center Configuration Manager 2007 Management Pack. Before you import this Management Pack, you need to make a change to the Configuration Manager server. This change was made as a part of setup for this session, so we will review the change instead.

Perform these steps on SEA-SCCM-01.33. On the desktop, right-click Computer, and then click

Properties.

34. The System window opens. Maximize the window.

35. Click Advanced system settings.

36. The System Properties dialog box appears. Click Environment Variables.

A number of rules in the Configuration Manager Management Pack read Configuration Manager–based log files to check for errors. To monitor these logs, the location of the Configuration Manager installation folder must be specified. To do so, we created the SMS_INSTALL_DIR_PATH system environment variable on a site server so that the Operations Manager Agent running under Local System or a local administrator user context has access to the log files in the SMS_INSTALL_DIR_PATH\Logs directory.

37. The Environment Variables dialog box appears. Click SMS_INSTALL_DIR_PATH, and then click Edit.

38. Click OK three times.

39. Close System.

This Management Pack was imported before this demonstration, but we will review where the Management Pack is located.

Perform these steps on SEA-SCOM-01.40. In the Administration pane, right-click Management Packs, and

then click Import Management Packs.

41. The Select Management Packs to import dialog box appears. Browse to C:\Program Files\System Center Management Packs\Microsoft System Center Configuration Manager 2007 Management Pack.

This Management Pack monitors Microsoft System Center Configuration Manager 2007.

42. Click Microsoft.SystemCenter.ConfigurationManager.2007.mp, and then click Open. The Import Management Pack dialog box appears.

Because this Management Pack has already been imported, we will cancel the import.

43. Click Cancel.



Chapter 15 View Rules and Knowledge in the Windows Server 2008 Base Management Pack

Speaker Script StepsThe Authoring pane of the Operations Console displays the monitoring settings of imported Management Packs. You can view existing attributes, monitors, object discoveries, rules, tasks, and views by clicking the appropriate leaf object under the Management Pack Objects node. You can also create new attributes, monitors, rules, and tasks from each corresponding leaf object.

Let's take a look at rules.

1. In the Navigation pane, click Authoring.

2. In the Authoring pane, expand Management Pack Objects, and then click Rules.

You can use rules to collect data, such as events, generated by managed objects. Rules can be used instead of monitors to generate alerts when the data collected from managed objects does not indicate the health state of the managed objects.

3. In the details pane, point to the rules.

We will focus on the rules from the Windows Server 2008 Base Operating System Management Pack.

4. In the details pane, click the Management Pack column header to sort the rules by Management Pack.

You may need to resize this column so that the full Management Pack name is displayed.

5. Scroll down until you see Windows Server 2008 Operating System rules.

Given the number of rules, we will search for some specific ones to take a closer look at. Notice that the same rule appears in three different groups.

6. In the Look for field, type Duplicate IP Address, and then click Find Now.

You may need to click the details pane to get the results to appear.

7. Point to the three rules.

This rule will generate an alert when a duplicate IP address has been detected on the network.

8. Right-click the first rule, and then click Properties.

9. The Duplicate IP Address has been Detected Properties dialog box appears. Point to Description.

Each rule has product knowledge that contains information from the Management Pack author about the causes of an alert and suggestions on how to fix the issue that caused an alert to be raised.

This rule has a summary of the problem, possible causes of the problem, resolutions for how to troubleshoot and fix the problem, and a link to an external knowledge source to get more information on this topic.

10. Click the Product Knowledge tab.

11. Scroll down as you discuss.

Administrators can add their own knowledge to rules and monitors to expand the troubleshooting information and provide company-specific

12. Click the Company Knowledge tab.



information for operators, which is known as company knowledge. 13. Click Close.

Let's look at a different kind of rule. 14. In the Look for field, type Total Processor, and then click Find Now.

You may need to click the details pane to get the results to appear.

15. Right-click the first Total Processor % Interrupt Time 2008 rule, and then click Properties.

This rule collects performance data for the Processor % Interrupt Time performance counter. This information is collected and is exposed in one or more Views and/or Reports.

16. The Total Processor % Interrupt Time 2008 Properties dialog box appears. Point to Description.

The product knowledge for this rule gives us a summary of the information that is collected.


18. Click Close.




Send feedback.




Chapter 17 Demo 4: Monitoring Windows Server In this demonstration, we will review how to search and filter data using the Scope, Find, and Search options in Operations Manager.

Chapter 18 Monitor Windows Server Systems to Search and Filter Data

Speaker Script StepsWe will first create a new alert view. We want as many alerts as possible to better show how to search and filter data your data. So this alert view will show all alerts.

Perform these steps on SEA-SCOM-01.1. In the Navigation pane, click Monitoring.

2. In the Monitoring pane, right-click Monitoring, and then click New | Alert View.

3. The Properties dialog box appears. In the Name field, type All Alerts.

One way to filter alerts is to select specific criteria in the alert view itself. We can select alerts of a specific severity or priority, alerts created by a specific source, alerts with a specific resolution state, alerts resolved by a specific user, or alerts from a specific time period, among others.

4. Point to the options in the Criteria tab.

5. Click OK.

Another way to filter alerts is by applying a scope. A list of existing groups and distributed applications is displayed. If the list is too long, you can find a specific group or distributed application by entering a word or phrase in the Look for text box.

6. Click the Scope toolbar button.

7. The Change View Scope dialog box appears. Point to Look for.

We will select DNS 2008 Servers, which will filter the alert view to only show alerts from computers in that group.

8. Click DNS 2008 Servers, and then click OK.

9. Point to the details pane.

You can change the scope by clicking Change Scope… 10. Point to Change Scope.

…And you can close the scope clicking the X or by clicking the Scope button again.

11. Point to X, and then click the Scope toolbar button.

We used the Find button earlier when we looked at rules, and we will use it to search through alerts. You can use the Find button when the list of objects in the results pane is too long to quickly pick out a particular object.

12. Click the Find toolbar button twice.

This should cause the Look for field to disappear and then reappear.

The Find button will search against the Source and Name columns. In this case, we will search for the word DNS.

13. In the Look for field, type DNS, and then click Find Now.

14. In the details pane, point to the alerts.

15. Click Clear.



Use the Search button if you want to find all objects that meet a certain criterion. Search will search through all objects in Operations Manager and produce a list of all objects that meet the criterion. The list is sorted by object type.

16. Click the Search toolbar button.

17. The Search Window opens. Maximize the window.

18. In the Search field, type DNS, and then click Search.

19. Close the Search Window.

Chapter 19 Create a Unit Monitor

Speaker Script StepsThere may be times when you want to monitor a service that is not included in a Management Pack. You can create monitors in Operations Manager 2007 so that you can create performance thresholds, look for events, monitor Windows services, and evaluate SNMP to set health state and generate alerts when changes occur in your environment.


2. In the Authoring pane, click Monitors.

3. In the Actions pane, click Create a monitor, and then click Unit Monitor.

We will create a Windows services unit monitor that can be used to generate an alert.

4. The Create a unit monitor Wizard appears. Expand Windows Services, and then click Basic Service Monitor.

5. Click Next.

We will use this monitor to generate an alert when the Telnet Windows Service stops running.

6. The General Properties page appears. In the Name field, type Telnet Windows Service.

7. In the Description field, type This monitor will alert when the Telnet Windows Service stops running.

Now, we will define a monitor target. A monitor target is used to specify what managed objects will receive this monitor and be monitored.

In this demonstration, we will choose the Agent target. This will allow all Operations Manager agents to receive this monitor.

8. Click Select.

9. The Select a Target Type dialog box appears. Click Agent, and then click OK.

You can also select a Parent monitor or disable it. We will use the availability monitor for our unit monitor.

10. Point to Parent monitor, and then click Next.

Now, we need to select the service we want to monitor. In this case, we will select the Telnet service.

11. The Service Name page appears. Click the ellipses (…) button.

12. The Select Windows Service dialog box appears. Click Display Name to sort the list by name, click Telnet, and then click OK.

13. Click Next.

We can adjust the health states for the monitor condition. By default, a critical health state is raised when the service is not running. When it is running, the health state will be healthy. You can change these, but for the purpose of this demonstration, we will accept the defaults.

14. The Configure Health page appears. Point to the Health State column.

15. Click Next.

Finally, we can specify the alert settings. We can select whether an alert is generated and then specify under which conditions that will happen.

16. The Configure Alerts page appears. Select Generate alerts for



We can also specify whether to automatically resolve the alert when the monitor returns to a healthy state.

this monitor.

We can then set additional alert properties, such as the alert name, description, the priority, and the severity. We will accept the defaults and create the new unit monitor.

17. Point to Alert properties.

18. Click Create.




Send feedback.




Chapter 21 Demo 5: Investigating and Resolving Alerts In this demonstration, we will investigate alerts for Print Server and Terminal Services and see how to resolve them.

Chapter 22 Investigate Windows Server 2008 Print Server Alerts

Speaker Script StepsThe Windows Server Print Server Management Pack monitors the performance and health of print servers running the Microsoft Windows 2000 Server, Windows Server 2003, and Windows Server 2008 operating systems. This Management Pack highlights performance, health, and availability conditions that might indicate problems with print servers and shared printers.

Unfortunately it is difficult to simulate printer issues inside a virtual environment without a physical printer. Stopping the Print Spooler service is an obvious failure, but it will help show how to investigate and resolve alerts with a print server.

Perform these steps on SEA-DC-01.1. On the desktop, double-click Services.


3. Right-click Print Spooler, and then click Stop.

4. Close Services.

Before we investigate the print spooler issue, we will examine some of the rules that come with the Print Server Management Pack. First, let's change the scope so that we only see the rules from the Print Server Management Pack.

Perform these steps on SEA-SCOM-01.5. In the Authoring pane, click Rules.

6. In the details pane, click Change Scope.

7. The Scope Management Pack Objects by target(s) dialog box appears. Click Clear All.

8. Select Windows 2008 Print Services Role, and then click OK.

The Print Router: Check resource availability rule creates an alert when Windows printing cannot allocate sufficient resources for an operation or is processing an upgrade.

9. In the details pane, right-click Print Router: Check resource availability, and then click Properties.

10. The Print Router: Check resource availability Properties dialog box appears. Point to Description.

By looking at the product knowledge, we learn that no immediate action is required for this alert. We also learn that if problems persist, we should determine whether the computer is low on system resources, such as CPU resources, disk I/O performance, or memory, and consider restarting the server after notifying users. It then goes on and tells us how to go about doing this.

11. Click the Product Knowledge tab. Scroll down as you discuss.

12. Click Close.

The Shared Printer: Restart the print spooler fix sharing problems and check Group Policy rule will create an alert when there are certain problems with a shared printer.

13. In the details pane, right-click Shared Printer: Restart the print spooler fix sharing problems and check Group Policy, and then click Properties.



14. The Shared Printer: Restart the print spooler fix sharing problems and check Group Policy Properties dialog box appears. Point to Description.

The Product Knowledge tab tells us to restart the print spooler, and it warns us that this will cause all print jobs to be restarted. It then goes on to list a number of troubleshooting steps for this alert.

15. Click the Product Knowledge tab. Scroll down as you discuss.

16. Click Close.

Now, let's see if an alert has been generated for our print spooler. We could use the general Active Alerts view, but we can also use the Active Alerts view specific to the Print Server.

17. In the Navigation pane, click Monitoring.

18. In the Monitoring pane, expand Microsoft Windows Print Server | Microsoft Windows Server 2008 Print Services, and then click Active Alerts.

The alert tells us that the print spooler service has stopped and that it needs to be started again. It even tells us how to start it using the command prompt.

19. In the details pane, right-click the alert, and then click Properties.

20. The Alert Properties dialog box appears. Click the Product Knowledge tab.

21. Click OK.

Instead, we can use the Start Printer Spooler task that comes with the Print Server Management Pack. This task will start the Print Spooler service on our Print Server without us having to leave the Operations Console.

22. In the Actions pane, click Start Printer Spooler.

23. The Run Task - Start Printer Spooler dialog box appears. Click Run.

After a short time, the service has been successfully restarted. 24. The Task Status - Start Print Spooler dialog box appears. When the process is complete, point to Success.

25. Click Close.

After the issue that caused the alert has been resolved, the alert is automatically closed. This view only shows active alerts, and we would have to use a different view that also shows closed alerts if we wanted to add company knowledge about this alert.

26. Point to the details pane.

Chapter 23 Investigate Terminal Services Connection Issues

Speaker Script StepsNow, we will create an issue with the Terminal Services license server. We want to create an issue that is not an obvious one.

Perform these steps on SEA-SCCM-01.1. On the desktop, double-click Windows Firewall.

2. The Windows Firewall window opens. Maximize the window.

3. Click Change settings.

To accomplish this, we will disable the firewall exception for the Terminal Services licensing server on our license server. This will allow

4. The Windows Firewall Settings dialog box appears. Click On, and then click the Exceptions tab.



for normal network traffic but will block attempts to reach the license server.

5. Clear Terminal Services Licensing Server, and then click OK.

6. Minimize Windows Firewall.

To trigger the alert, we will open a connection to our terminal server, which is a different server than our license server. We will open the Calculator RemoteApp program.

Perform these steps on SEA-WRK-001.7. On the desktop, double-click Calculator.

8. The RemoteApp dialog box appears. Click Connect.

9. The Windows Security dialog box appears. In the User name field, type Contoso\Administrator.

10. In the Password field, type Password1, and then click OK.

It could take up to two minutes for the Calculator program to appear. You can skip the next step and move on with the rest of the demonstration instead of waiting.

Even though the terminal server cannot reach the license server, the RemoteApp program still opens. This is because our terminal server is still in the initial 120-day grace period.

11. The Calculator dialog box appears. Point to Calculator.

If the terminal server is out of the initial 120-day grace period then the Calculator should not appear and you might receive an error message.

If we switch back to our Operations Manager server and look at the alert view, we can see that an alert has been generated.

Perform these steps on SEA-SCOM-01.12. In the Monitoring pane, expand Microsoft Windows Terminal

Services, and then click Active Alerts.

13. In the details pane, point to the alert.

By looking at the alert properties, we can see that it was generated because the terminal server could not locate a license server in the Contoso.com domain.

14. Right-click the alert, and then click Properties.

15. The Alert Properties dialog box appears. Point to Alert Description.

If we look at the Product Knowledge tab, we find a list of possible issues and troubleshooting steps to try. The four main possibilities are listed as: There is a network connectivity problem between the terminal server and the license server; The license server is not correctly configured to be automatically discovered; The terminal server cannot automatically discover a Terminal Services license server; or the Terminal Services Licensing service is not running on the license server.


17. Point to the four bullet points under the Resolutions header.

Before we begin troubleshooting, we will check the Company Knowledge tab to see if this alert has been encountered and fixed before in our organization. There is no company knowledge, so we will switch back to the Product Knowledge tab.

18. Click the Company Knowledge tab.




The first possible issue was network connectivity between the two servers. It is suggested that we ping the license server from the terminal server to see if there is an issue.

The ping resolved successfully using the fully qualified domain name of the license server.

Perform these steps on SEA-DC-01.20. On the desktop, double-click Command Prompt.

21. The Command Prompt appears. Type ping sea-sccm-01.contoso.com, and then press ENTER.

We will ping the license server by IP address, as well, just to be sure. 22. Type ping 192.168.32.4, and then press ENTER.

23. Close Command Prompt.

Since network connectivity does not seem to be the issue, we will investigate by using the next suggested troubleshooting method: checking to see if the license server is configured correctly to be automatically discovered.

Perform these steps on SEA-SCCM-01.24. On the desktop, double-click TS Licensing Manager.

25. The TS Licensing Manager window opens. Maximize the window.

26. In the console tree, expand All Servers, and then click SEA-SCCM-01.

27. On the Action menu, click Review Configuration.

The license server is not installed on the domain controller, so terminal servers in the domain will not be able to automatically discover this license server. This could be the cause of this issue.

28. The SEA-SCCM-01 Configuration dialog box appears. Point to the warning.

29. Click OK.

30. Close TS Licensing Manager.

Using the next recommended troubleshooting step, we will determine if the terminal server can discover the license server.

Perform these steps on SEA-DC-01.31. On the desktop, double-click Terminal Services Configuration.

32. The Terminal Services Configuration window opens. Maximize the window.

By using the Terminal Services Configuration console on the terminal server, we can see that the terminal server has the SEA-SCCM-01 server listed as the license server.

33. In the console tree, click Licensing Diagnosis.

34. In the details pane, scroll down, and under Summary, point to sea-sccm-01.

The last initial troubleshooting step that was suggested is to verify that the Terminal Services licensing service is running on the license server. If we look in the Services console we can see that it is.

Perform these steps on SEA-SCCM-01.35. On the desktop, double-click Services.


37. Point to Terminal Services Licensing.

38. Close Services.

The product knowledge for this alert has additional troubleshooting steps to try, but for the purpose of this demonstration, we will stop at this point. This should give you a good understanding of how troubleshooting alerts works in Operations Manager 2007.

Now, we will enable the Terminal Services licensing server exception for

39. Restore Windows Firewall.

40. Click Change settings.

41. The Windows Firewall Settings dialog box appears. Click the Exceptions tab.



the license server firewall to resolve the alert. 42. Select Terminal Services Licensing Server, and then click OK.

43. Close Windows Firewall.

In order for the terminal server to check the availability of the license server, we need to have terminal server try to contact the license server again. We can do this by using the Terminal Services Configuration Console and having it check the name of the license server.

Perform these steps on SEA-DC-01.44. In Terminal Services Configuration, in the console tree, click

Terminal Services Configuration: SEA-DC-01.

45. In the details pane, double-click License server discovery mode.

46. The Properties dialog box appears. Click Check Names, and then click OK twice.

47. Close Terminal Services Configuration.

Now that we have fixed the issue, we can close the alert. First, you may want to add a note about the issue and how it was resolved in the Company Knowledge tab. This way, if the issue occurs again, you can see what was done last time and perhaps save time and effort if the issue reoccurs.

Perform these steps on SEA-SCOM-01.48. Point to the Company Knowledge tab.

Finally, we will close the alert. Alerts can be closed automatically if the Operations Manager collects updated information that the alert is resolved before you have a chance to close it.

49. Click the General tab.

50. In the Alert State list, click Closed.

51. Click OK.

Chapter 24 Monitor System Center Configuration Manager

Speaker Script StepsNow, we will advertise a package and then investigate any issues that come up.

Perform these steps on SEA-SCCM-01.1. On the desktop, double-click ConfigMgr Console.

2. The Configuration Manager Console window opens. Maximize the window.

We have already created a package for Microsoft Office Visio Viewer, so let's distribute it.

3. In the Navigation pane, expand Site Database | Computer Management | Software Distribution, and then click Packages.

4. In the Packages pane, right-click VisioViewer, and then click Distribute | Software.

We'll use the current server as our distribution point. 5. The Distribute Package Wizard appears. Click Next.

6. The Distribution Points page appears. Select SEA-SCCM-01, and then click Next.

We'll advertise the package to the clients. 7. The Advertise Program page appears. Click Yes, and then click



Next.

We'll use the Visio Viewer Installer to install Visio Viewer. 8. The Select Program page appears. Click VisioViewer, and then click Next.

Let's use an existing collection to specify the computers that we want to receive the advertisement. Let's advertise Visio Viewer to all the workstation systems.

9. The Advertisement Target page appears. Click Browse.

10. The Browse Collection dialog box appears. Scroll down, click All Windows Workstation or Professional Systems, and then click OK.

We'll leave the scheduling options at the default settings. We can assign the program so that it is a mandatory installation, and we can set a date on which the program will be automatically installed. Let's have it installed now.

11. Click Next four times.

12. The Advertisement Schedule page appears. Click Yes, assign the program.

Now, we need to update the distribution points. 13. Click Next twice.

14. Wait for the wizard to finish, and then click Close.

15. In the Actions pane, click Update Distribution Points.

16. The Confirm Update Distribution Points dialog box appears. Click Yes.

Because the distribution and policy updates will take some time to run automatically, we'll run advertised programs from the client computer. But, we don't see any programs listed, so let's check our Operations Console and see if there are any alerts.

Perform the following steps on SEA-WRK-001.17. On the desktop, double-click Run Advertised Programs.

18. The Run Advertised Programs window opens. Maximize the window.

19. Click Close.

We can see that there is indeed an alert for the workstation. Perform the following steps on SEA-SCOM-01.20. In the Monitoring pane, expand Microsoft System Center

Configuration Manager 2007, and then click Alerts.

21. In the details pane, right-click the alert for SEA-WRK-001, and then click Properties.

Due to the nature of the timing of alerts, this alert may not appear right away. You can perform these steps to force the alert to appear sooner. In the Monitoring pane, under Monitoring, click Computers. Right-click SEA-WRK-001, point to Maintenance Mode and then click Start Maintenance Mode. In the Maintenance Mode Settings page, under Duration, set the Number of minutes to 5 and then click OK.

It looks as though the SMS Agent Host service has stopped, which would prevent the workstation from seeing the advertised program. This could happen if the client computer is shut down, Configuration Manager is being upgraded, the SMS Agent Host service was manually stopped, or one of the dependent components, such as Windows Management

22. The Alert Properties dialog box appears. Click the Product Knowledge tab.

23. Click OK.



Instrumentation, is shut down.

On the workstation, we will check the SMS Agent Host service and see if it is stopped. It is, so we will start the service and move back to the Operations Manager server.

Perform these steps on SEA-WRK-001.24. On the desktop, double-click Services.


26. Right-click SMS Agent Host, and then click Start.

27. Close Services.

After starting the SMS Agent Host service, we will close the alert for the workstation.

Perform the following steps on SEA-SCOM-01.28. In the details pane, right-click the alert for SEA-WRK-001, and

then click Properties.

29. The Alert Properties dialog box appears. In the Alert Status list, click Closed.

30. Click OK.

31. Minimize Operations Console.

Now, we will try the workstation again and see if we can run the advertised program.

Perform the following steps on SEA-WRK-001.32. Click the Assigned Program balloon when it appears on the

taskbar. The Program Countdown Status dialog box appears.

It may take several minutes for the advertised program to appear, depending on the hardware used for the demo.

33. Click Run.

34. The Microsoft Office Visio Viewer 2007 dialog box appears. Close the dialog box, and then click Yes to confirm.




Send feedback.




Chapter 26 Demo 6: Creating Operations Manager Reports In this demonstration, we will see how to create a new report from Operations Manager. We will create a report model and then create a new report using Report Builder.

Chapter 27 Create a Report Model

Speaker Script StepsTo create reports in Report Builder, at least one model needs to be available. A report model project contains the definition of the data source, the definition of a data source view, and the model.

Perform these steps on SEA-SCOM-01.1. On the desktop, double-click SQL Server Business Intelligence

Development Studio.

2. The Program Compatibility Assistant dialog box appears. Click Run program.

3. The Start Page - Microsoft Visual Studio window opens. Maximize the window.

We will create a report model project called OpsMgrDW by using Business Intelligence Development Studio.

4. On the File menu, click New | Project.

5. The New Project dialog box appears. Click Report Model Project.

6. In the Name field, type OpsMgrDW, and then click OK.

Now, we need to define one data source from which we will extract business intelligence data and metadata.

7. In the Solution Explorer, right-click Data Sources, and then click Add New Data Source.

8. The Data Source Wizard appears. Click Next.

You can define a data source based on an existing connection or on a previously defined data source object, or you can define a new connection. We will define a data source based on a new connection.

9. The Select how to define the connection page appears. Click New.

10. The Connection Manager dialog box appears. In the Server name field, type SEA-SCOM-01.

We will use the OperationsManagerDW database. This database contains data that has been processed and prepared for reporting.

11. In the Select or enter a database name list, click OperationsManagerDW, and then click OK.

12. Click Next.

13. The Completing the Wizard page appears. Click Finish.

After defining the data source that we will use in our report model project, our next step is to define a data source view for the project. A data source view is a logical data model based on one or more data sources.

14. In the Solution Explorer, right-click Data Source Views, and then click Add New Data Source View.

15. The Data Source View Wizard appears. Click Next.



We will use the data source we just created. 16. On the Select a Data Source page, click Next.

We will only include the table objects in our data source view. 17. The Select Tables and Views page appears. In the Available objects field, click the first table in the list.

18. Hold down the SHIFT key, scroll down, and then click the last table in the list.

19. Click >, and then click Next.

Data source views facilitate the model design process by providing you with a useful representation of the data that you specified. Because metadata is stored in the data source view, you do not need to be connected to the underlying data source to work with the objects.

20. The Completing the Wizard page appears. Click Finish.

We will now create a new report model. A report model is a metadata layer on top of a physical database that identifies business entities, fields, and roles.

21. In the Solution Explorer, right-click Report Models, and then click Add New Report Model.

22. The Report Model Wizard appears. Click Next.

We will use the data source view that we just created. 23. The Select Data Source View page appears. Click Next.

These rules determine how the metadata is generated from the data source. For the purpose of this demonstration, we will accept all the defaults. The metadata will be combined into objects called entities.

24. The Select report model generation rules page appears. Point to the rules.

25. Click Next.

To generate certain settings within the model, the Semantic Model Definition Language depends on database statistics that are stored in the data source view. If the data in the data source has changed, or if the data source view was modified, we recommend that you select the Update statistics before generating option.

26. The Collect Model Statistics page appears. Click Next.

We will name the model OpsMgrDW.

After they are published, these models enable Report Builder users to develop reports without having to be familiar with database structures or understand and write queries. Models are composed of entities, which are sets of related report items that are grouped together under a friendly name, predefined relationships between these business entities, and predefined calculations. Models are defined by using an XML language called Semantic Model Definition Language.

27. The Completing the Wizard page appears. In the Name field, type OpsMgrDW.

28. Click Run.

This process could take up to three minutes to complete.

29. Click Finish.

30. The Microsoft Visual Studio dialog box appears. Click Yes.

To build reports using the model that we just created, we must publish it to our report server. The data source and data source view are included with the model when it is published.

31. In Solution Explorer, right-click OpsMgrDW.smdl, and then click Deploy.

32. Close Microsoft Visual Studio.



Chapter 28 Create a New Report in Report Builder

Speaker Script StepsNow that we have finished creating the report model, we can create a new report. You can run and even create new reports from the Operations Console.

1. Restore Operations Console.

2. In the Navigation pane, click Reporting.

3. In the Reporting pane, click Authored Reports.

4. In the Actions pane, click Design a new report.

Clicking the Design a new report link opens Report Builder. We need to provide credentials in order to connect.

5. The Connect to SEA-SCOM-01.Contoso.com dialog box appears. In the User name field, type Contoso\OpsMgrAdmin.

6. In the Password field, type Password1, and then click OK.

7. The Microsoft Report Builder window opens. Maximize the window.

We will select the report model that we created earlier and create a blank report by using the table layout.

8. In the Select a source of data for your report field, click OpsMgrDW, and then click OK.

We will create a report that lists the components of the Management Packs.

9. In the design surface, click Click to add title, and then type Management Pack Components.

We will add the Management Pack System Name field from the Management Pack entity to the report.

10. Under Entities, click Management Pack.

11. Under Fields, drag Management Pack System Name to the design surface.

Next, we will add the number of rules field to the report, placing it after the Management Pack System Name field. Management pack rules collect data from various sources, such as Perfmon, EventLog, SNMP, and log files.

12. Under Entities, click Rules.

13. Under Fields, drag #Rules field to the design surface, placing it after the Management Pack System Name field.

We will add the number of monitors field to the report. Monitors are used to determine the health state of an application component and are an integral part of the health model.

14. Under Entities, click Monitors.

15. Under Fields, drag #Monitors field to the design surface, placing it after the #Rules field.

Then, we will add the number of overrides field to the report. Overrides adjust the configuration of Operations Manager monitoring settings for monitors, attributes, object discoveries, and rules.

16. Under Entities, click Overrides.

17. Under Fields, drag #Overrides field to the design surface, placing it after the #Monitors field.

We will now run the report to make sure it appears the way we want it to.

18. Click the Run Report toolbar button. The Management Pack Components report appears.

Now, we will save the report to our report server. We will name the report Management Pack Components, and save it to My Reports.

19. On the File menu, click Save As.

20. The Save As Report dialog box appears. Click the folder button.



This is the button in the upper-right corner of the dialog box.

21. Double-click My Reports.

22. In the Name field, type Management Pack Components, and then click Save.

Now, we will see if the report is available from the Operations Console. We find it in the Authored Reports view.

23. Close Report Builder.

24. In the Reporting pane, right-click Authored Reports, and then Refresh.

25. In the Reporting pane, click Authored Reports.

We can run the report, and it behaves and looks just as it did in Report Builder. We have now created a custom report from the Operations Console by using the Report Builder.

26. In the details pane, right-click Management Pack Components, and then click Open.

27. The Management Pack Components window opens. Maximize the window.

28. Click the Next Page toolbar button.

29. Close Management Pack Components.




Send feedback.




Chapter 30 Demo 7: Configuring Service-Level Dashboards In this demonstration, we will configure a Service-Level Dashboard for a Web application.

Chapter 31 Create the Web Application Monitor

Speaker Script StepsThe Service-Level Dashboards Management Pack has already been imported, so we will begin by creating a new Management Pack to store Web Application Monitors and distributed application models for our Web application.

Perform these steps on SEA-SCOM-01.1. In the Navigation pane, click Administration.

2. In the Administration pane, right-click Management Packs, and then click Create Management Pack.

The Web application that we will monitor is the Woodgrove Bank Resources page. Woodgrove Bank is a company we have partnered with.

3. The Create a Management Pack dialog box appears. In the Name field, type Woodgrove Bank, and then click Next.

4. The Knowledge Article page appears. Click Create.

Now, we will create a Web application monitor. The Web application monitor provides the synthetic transaction for the Service-Level Dashboard. It monitors the Web application and then changes the health state of an object associated with the Web application, based on the results of the synthetic transaction. It is this change in health state that the Service-Level Dashboard records and reports on.


6. In the Authoring pane, click Management Pack Templates.

This may already be selected.

7. In the Actions pane, click Add monitoring wizard.

We will be monitoring a Web application, so we select that first in the Add Monitoring Wizard.

8. The Add Monitoring Wizard appears. Click Web Application, and then click Next.

We will name the Web application monitor WoodgroveBank. We will also select the Management Pack we just created.

9. The Web Application Name and Description page appears. In the Name field, type WoodgroveBank.

10. In the Select destination Management Pack list, click Woodgrove Bank, and then click Next.

Now, we will test the Web address to ensure that it is valid. It is possible to proceed through the wizard without this test succeeding. If the test returns an error, you should verify the URL and then click Details for more information.

11. The Enter and Test Web Address page appears. In the field after the http://, type SEA-SCCM-01, and then click Test.

If a dialog box appears stating that the test may be timing out, click Yes.

12. Click Next.

We will select the SEA-WRK-001 managed computer as the watcher node. To act as a watcher node, the system needs an Operations Manager agent installed.

13. The Choose Watcher Nodes page appears. Select SEA-WRK-001.Contoso.com.

We can have the watcher node query as often as we like. The minimum is every 30 seconds, which we will use for this demonstration.

14. In the Run this query every field, type 30.



15. In the Minutes list, click Seconds, and then click Next.

We will now finish the wizard and create our Web application monitor. 16. The Web Application Monitoring Settings Summary page appears. Click Create.

Chapter 32 Add a Recording to an Existing Web Application Object

Speaker Script StepsNow, we will use the Web Application Editor to capture navigation through our Web site. In the Web Application Editor, you can interactively record a sequence of actions on a Web site, or you can manually create a set of requests that monitor the Web site. The capture Web site navigation feature intercepts traffic between Internet Explorer and the Web site and captures all HTTP request data, such as headers and body. This feature also sets defaults for monitoring criteria to match the captured data.

1. In the details pane, click WoodgroveBank.

2. In the Actions pane, click Edit Web application settings.

You can add recordings to existing Web Application objects, or you can create a recording immediately after creating a new Web Application object. If you add a recording to an existing object, the captured requests can be inserted in between other requests that you have already created or recorded.

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. Let's start the recording.

3. The Web Application Editor - WoodgroveBank window opens. In the Actions pane, click Start capture.

We will browse to the Web site and then briefly navigate the page. 4. Internet Explorer opens. Maximize the window.

5. In the Address field, type http://SEA-SCCM-01, and then press ENTER.

6. Under Account, click Log In.

7. Close Internet Explorer.

Now that we have captured some navigation of the Web site, we will run the test and see the results. If the Web application requires authentication, this test may fail. Credentials that have been configured for this Web application will not be used to run the test. Be aware that if the site you are testing does not explicitly require authentication, the test may still succeed.

8. In the Actions pane, click Stop capture.

9. In the Actions pane, click Run Test.

10. The Run Now Results window opens. Maximize the window.

We can see that our Web site ran successfully in most of the test, but 11. Point to the results.



there are some warnings and even a couple of errors. For the Service-Level Dashboard, an error is equivalent to an availability exception, and a warning is equivalent to a performance exception.

12. Click OK.

13. Close Web Application Editor - WoodgroveBank.

Chapter 33 Create the Distributed Application Model

Speaker Script StepsThe 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.

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

2. The Distributed Application Designer dialog box appears. In the Name field, type Woodgrove Bank.

We will select the Service-Level Dashboard Application template. This template can be used to create distributed applications that conform to the standards required by the Service-Level Dashboard Report.

3. Under Template, click Service-Level Dashboard Application.

We will select the Woodgrove Bank Management Pack we created earlier.

4. In the Management Pack list, click Woodgrove Bank, and then click OK.

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.

5. The Distributed Application Designer window opens. Maximize the window.

Each component group contains objects, and you can control which types by adjusting the properties.

6. Right-click Woodgrove Bank Component Group 1, and then click Properties.

7. The Component Group Properties dialog box appears. Point to the objects, and then click OK.

The Objects pane lists 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, you can clear the check box for any object type that is not part of your distributed application.

8. In the Objects pane, clear Distributed Application Component.

Each of the other buttons in the Objects pane allows you to view the different objects. By default, the list contains all the discovered objects on your network that are of that object type.

We will add the WoodgroveBank Web Application Group entity to the

9. In the Objects pane, click Entity. Drag the WoodgroveBank Web Application group to Woodgrove Bank Component Group 1.



Woodgrove Bank Component Group 1.

We will then add the SEA-SCCM-01 Windows computer entity to the Woodgrove Bank Component Group 2.

Any item in the component group is displayed as a transaction, with its health state calculated.

10. Drag the SEA-SCCM-01.Contoso.com Windows computer to Woodgrove Bank Component Group 2.

You can configure the health rollup of the distributed application, and by extension, the Service-Level Dashboard, in the Component Group Details pane. You can create an override for the rollup algorithm for the component group, or entire model, that rolls up as expected.

11. Click the Save toolbar button.

12. In the diagram pane, click Woodgrove Bank Component Group 1.

13. In the Component Group details pane, click Configure Health Rollup.

14. The Override Properties dialog box appears. Click Cancel.

15. Close Distributed Application Designer.

Chapter 34 Change the Service-Level Dashboard Attributes for an Application

Speaker Script StepsAfter 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. First, we need to change the scope of this view and add the SLDBase.

1. In the Authoring pane, expand Management Pack Objects, and then click Object Discoveries.

2. Click Change Scope.

3. The Scope Management Pack Objects by target(s) dialog box appears. Click View all targets.

4. Select SLDBase, and then click OK.

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.

5. Click Enterprise Service Monitoring Service Level Dashboard Discovery and then, in the Actions pane, click Overrides | Override the Object Discovery | For a specific object of type: Service Level Dashboard Application.

6. The Select Object dialog box appears. Click Woodgrove Bank, and then click OK.

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

7. The Override Properties dialog box appears. Select Override for PerformanceSLThreshold.

8. In the Override Setting field, type 90, and then click OK.

Now that we are finished configuring the Service-Level Dashboard, we will view the reports. First, we will open the Service-Level Dashboard report.

9. In the Navigation pane, click Reporting.

10. Press F5.

11. In the Reporting pane, click Service Level Dashboard for System Center Operations Manager 2007.



12. In the details pane, right-click Service Level Dashboard, and then click Open.

We will set the date range and then select the Default Dashboard Group.

13. The Service Level Dashboard Report window opens. Maximize the window.

14. In the From list, click Yesterday.

15. Under Dashboard Group, select Default Group.

16. Click Run.

When the report is generated, we see the availability and performance of our Web application. We can also see the component groups that we configured.

17. The Service Level Dashboard Report window refreshes. Expand Woodgrove Bank.

18. Expand Woodgrove Bank Component Group 2.

By clicking Woodgrove Bank, we see the availability report that shows us the up-time and down-time of the Web application.

19. Click Woodgrove Bank.

20. The Availability Report page appears. Close Availability Report.

We will run another report. This time, we open the Service-Level Dashboard Summary by Application report. We select the same date range and dashboard group.

21. In the details pane, right-click Service Level Dashboard - Summary by Application, and then click Open.

22. The Service Level Dashboard - Summary by Application Report window opens. Maximize the window.

23. In the From list, click Yesterday.

24. Under Dashboard Group, select Default Group.

25. Click Run.

This report shows the same information, summarizes it by application, and uses gauges to display the service levels. Even though we have a small data sample for this demonstration, you can see how the Service-Level Dashboard can help you track, monitor, and report the service level compliance for your line-of-business applications.

26. The Service Level Dashboard - Summary by Application Report window refreshes.

27. Close Service Level Dashboard - Summary by Application Report.




Send feedback.TechNet Field Event Content 34 SRV-303


monitoring windows server systems demo script

Technology