You are browsing the archive for 2008 September.

Avatar of alkin

by alkin

Changing the ACS DataRetention Period for Opsmgr

1:23 pm in Uncategorized by alkin

Changing the Audit Collection Service DataRetention Period (based on the info found on the technet site)

Operations Manager grooms, or removes, data from its various databases at regular configurable intervals. For the Operations database, this is done in the Operations console. For the ACS database, these settings are configured during setup with a default value of 14 days. This means that every day, all database partitions (and their data) that are older than 14 days are dropped or deleted. Because of the volume of data that ACS can accumulate, 14 days is not an unreasonable setting. However, some companies might need to retain data for longer periods and they must have already planned for that when making the sizing and performance calculations for their environment. You can change the retention period for the ACS data by following this procedure.

To Change the ACS Data- Retention Period

1. Log on to the computer running SQL Server that hosts the ACS database with an account that has administrative rights to the ACS database.

2. Open the SQL Server Management Studio tool, and connect to the database engine.

3. Expand the Databases folder, and select the OperationsManagerAC database.

4. Right-click to open the context menu and select New Query….

5. Run the following query to see what your retention period is: SELECT * FROM dtConfig

clip_image002

Look for row 6. The result contains the days to retain + 1

6. In the Query pane, type the following, where number of days to retain data + 1 equals the number of days you want to pass before data that has aged past that point is deleted. For example, if you want to retain data for 30 days, type 31

USE OperationsManagerAC UPDATE dtConfig SET Value = <number of days to retain data + 1> WHERE Id = 6 and then click the Execute button on the toolbar. This will run the query and then open the Messages pane, which should read (1 row(s) affected).

clip_image004

7. To view the new setting, delete the previous query text from the Query pane and enter SELECT * FROM dtConfig. This will open the Results pane below the Query pane.

8. Look at the value in the sixth row; it should now equal the value you entered for <number of days to retain data + 1>.

9. Restart the Operations Manager Audit Collection Service for this to take effect.

 

Greetz,

Alkin

http://scug.be/blogs

 

Avatar of alkin

by alkin

Operations Manager/SSAS and PerformancePoint Scorecards

4:03 pm in Uncategorized by alkin

Daniel Savage posted on the team blog that the performancePoint team released  a sample solution that shows how to build cubes from the Operations Manager DW and then build balanced IT scorecards using Office PerformancePoint server from these cubes.

 

I had to look for 30 minutes on the net before I finally found what I needed!  Because I know you’re all lazy people I just put the links below. :-)

 

Scorecards and Dashboards for your IT Department A solution accelerator to help you create a complete performance management solution for monitoring the health of your IT infrastructure. Go beyond canned operational reports with interactive performance dashboards, comprehensive scorecards, and powerful analytics all built on Microsoft platform components including Microsoft® SQL Server®, Systems Center, Microsoft Office SharePoint® Server 2007, and Microsoft Office PerformancePoint® Server 2007.

 

The following diagram illustrates the major components of the framework, and the flow of data from source data to the finished dashboards. Data processes are numbered one through six in the diagram, with detailed descriptions to follow.

 

 Untitled

 

Greetz,

Alexandre Verkinderen

http://scug.be/blogs/scom

Avatar of alkin

by alkin

Configuration of Opsmgr Exchange 2007 management pack

7:51 am in Uncategorized by alkin

Here are some guidelines if you want to import the Exchange 2007 management pack in your scom environment:

Requirements

This Management Pack requires the Operations Manager 2007 updates specified in Knowledge Base articles 950853, 951979 and 951380 (see the Management Pack Guide for details).

Ensure that all systems running Exchange Server 2007 that are managed by Operations Manager use Local System as the Agent Action Account

  • If you are monitoring Exchange Server 2007 clusters, ensure that all physical nodes of the cluster are monitored by Operations Manager 2007 and that Agent Proxy is turned on for each physical node in the cluster.
  • Install the agent update specified in Knowledge Base article 950853 on all Exchange-based servers managed by Operations Manager before importing the Exchange Server 2007 Management Pack. This update addresses an agent memory leak issue.
  • Install the update specified in Knowledge Base article 951979. This update contains an updated agent restart script and fixes issues with cluster discovery.
  • If you are monitoring Exchange Server 2007 clusters, ensure that you have installed the agent update specified in Knowledge Base article 951380 on all Exchange Server 2007 cluster nodes managed by Operations Manager. This update addresses an issue with cluster discovery.

 

Configuration is required for the following monitoring scenarios:

· ActiveSync (Test-ActiveSyncConnectivity)

· Outlook Web Access (Test-OWAConnectivity)

· Web Services (Test-WebServicesConnectivity)

· Remote Unified Messaging (Test-UMConnectivity)

Enabling Outlook Web Access, Exchange ActiveSync, and Exchange Web Services Connectivity

Test-OwaConnectivity, Test-ActiveSyncConnectivity, and Test-WebServicesConnectivity are the cmdlets used by the Exchange Server 2007 Management Pack to test Microsoft Office Outlook Web Access, Exchange ActiveSync, and Exchange Web Services connectivity from Client Access servers to Mailbox servers. The cmdlets require that a test mailbox be created on each Exchange Server 2007 Mailbox server that is to be tested.

To create the test mailbox, log on to the Exchange Server 2007 Mailbox server with a user account that is both an Exchange administrator and an Active Directory administrator. Open the Exchange Management Shell, locate the Scripts directory under the installation path for Exchange Server 2007 (usually \Program Files\Microsoft\Exchange Server\Scripts) and execute the script New-TestCasConnectivityUser.ps1. Repeat this process on each Exchange Server 2007 Mailbox server that is to be tested. Note that if you have several organizational units named “Users” in your directory, you will need to specify the organizational unit in which to store the user.

c:\Program Files\Microsoft\Exchange Server\Scripts\New-TestCasConnectivityUser.ps1

image

Note:

Pass=> must meet AD complexity

OU=Users,DC=dolmen,DC=be

Results:

image

Enabling External Outlook Web Access Connectivity Monitoring

The rule is enabled by default. However, you must set an external URL on your Outlook Web Access virtual directory. To set an external URL, you must run the Set-OwaVirtualDirectory Exchange Management Shell command. The syntax of the command is: set-owavirtualdirectory “<Server name>\owa (Default Web site)” -externalurl:”https://<Fully Qualified Domain Name>/owa”

Note :

The examples assume that SSL is enabled. If SSL is not enabled, use http:// instead of https://.

powershell command:

set-owavirtualdirectory “Exchange1\owa (Default Web site)” -externalurl:https://Exchange1.dolmen.be/owa

image

Greetz,

Alexandre Verkinderen

http://scug.be/blogs/scom

 

Tags van Technorati: ,,,
Visit Us On TwitterVisit Us On Linkedin