Monitoring DFS-R BackLogs with OpsMgr

Hi,

Here is a good article that explains how to configure DFS-R monitoring and how to keep track of the DFS-R BackLogs.

http://blogs.technet.com/b/filecab/archive/2009/10/27/optional-configuration-for-the-dfs-replication-management-pack.aspx

/Peter

Tags:

OpsMgr / Microsoft SQL 2005 Reporting Services Issue

Hi Folks,

I found a small bug in Microsoft SQL 2005 Reporting Services where you aren't able to create a report database.

During the "Database Setup" slide of wizard "Reporting Service Configuration Manager" tool you may see on of the these error:

1. First error.

System.Data.SqlClient.SqlException: Could not locate entry in sysdatabases for database '<xxxxxx>'. No entry found with that name. Make sure that the name is entered correctly.
   at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
   at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
   at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
   at System.Data.SqlClient.SqlCommand.RunExecuteNonQueryTds(String methodName, Boolean async)
   at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe)
   at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
   at Microsoft.ReportingServices.Common.DBUtils.ApplyScript(String connectionString, String script)

 2. Second error.

 'Verify Database Version' and 'Setting Connection Info For Reporting Server' are warnings while 'Create grants rights script' task is failing

Example.

After during some troubleshooting I discovered that the issue occured everything I used a specific syntax for the report database name.

I've reported the issue to Microsoft and gotten the following reply:

------------------------------------------------------------------------------------------------

From your description, I understand that you are wondering why we can’t create a reporting database with the specific xxxReportServer name. If I am off the base, please feel free to let me know.

 

I performed a test in my side and found that we also can’t assign the database to xxxReportServe  without SCOM environment. So, we confirmed it’s a known issue for reporting service. I will report this problem to our product team and hope that they can do some change in the future .  As a workaround, we can use ReportXXXServer as the database name to bypass this bug.  

 

Let’s have an internal look. In my testing, I use sc3ReportServer for its report database name and generate all the scripts of creating database. I found the below records four copies.

 

USE sc3[sc3ReportServerTempDB]

 

These records/statements will make creating database operation failed and block our SCOM installation. To fix this problem, we can do some scripts modify(replace USE sc3[sc3ReportServerTempDB] with  USE [sc3ReportServerTempDB]) and run the generated scripts to create the database manually. After creating, we can point the reporting service configuration database to the new created database and then continue SCOM installation.

------------------------------------------------------------------------------------------------

Hope it helps you get around the issue.

Peter

Tags:

List of tools/management packs for OpsMgr

 

  1. LocalPortMonitor.zip – A vbs script (as a .txt file) for use in a SCOM unit monitor to locally check the status of a listening TCP port.  Described here.
  2. WSHCheck.zip – A vbs script (as a .txt file) for use in a SCOM unit monitor to check the WSH version on 32-bit Windows agents.  Described here.
  3. PutNodeInPatchMaint.zip - A powershell script to put nodes (and clusters, if applicable) in maintenance mode.  Described here.
  4. DocumentMPs.zip – A powershell script to document unsealed management packs by outputting MP entities to a formatted html file.  Described here.
  5. ListUsers2.zip – A powershell script to recursively list the members of a specified group to the defined recursion depth.  Initially descriped here.  Updates described here.
  6. WebMon.zip – A SCOM 2007 R2 management pack for monitoring of multiple websites controlled by a configuration file.   Described here.
  7. EventLogSearch.zip – A simple Windows Forms application for searching events in a local or remote eventlog, including search by description.  Described here.
  8. CiscoSNMP_R2_v1.0.2.7.zip - Version 1.0.2 of the Cisco Managment Pack for OpsMgr 2007 R2.  Described here and here.  (This has been replaced by the xSNMP Management Packs).
  9. Net-SNMP_v1.01.zip – Version 1.0.1 of the Net-SNMP UNIX/Linx Management Packs.  Described here.
  10. CiscoSNMP_SP1_v1.0.2.7.zip - Version 1.0.2 of the Cisco Managment Pack for OpsMgr 2007 SP1.  Described here.
  11. WSSBackup.zip – A VBS script for automating WSS 3.0 backups and an OpsMgr 2007 Management Pack to schedule and monitor the script.  Described here.
  12. xSNMP Management Pack Suite - Version 1.1.0 (Beta) of the xSNMP Management Pack Suite, introduced here, and updates described here.
  13. UNIX.Custom MP - Example SCOM 2007 R2 management pack for monitoring Defunct/Zombie processes on UNIX/Linux systems.  Described here

Source: http://operatingquadrant.com/downloads/

Tags:

How To: Enable Maintenance Mode from OpsMgr Agent side

 

This guide explians how to enable maintenance mode from the agent side. Allowing for a simplified way of activating computer maintenance mode.

 

This version adds the ability to turn off maintenance mode from the agent as well as turn it on. The vbscript has been updated with some more options and some instructions on how to use it.

To install or update you need to import the management pack and copy the 2 ps1 files to System Center Operations Manager 2007 program folder on the RMS.

Then you need to copy the vbscript file to any agent managed server and run it to set any server in maintenance mode for the desired time period.

------------------------------

VBScript Usage:

Usage: MaintMode ON|OFF [ON Duration][D][H][M]

Examples: MaintMode ON 6H
MaintMode ON 2D

ON is a mandatory keyword to put a server in maintenance mode.

ON Duration is number of [D]ays [M]inutes or [H]ours Maintenance
Mode should remain ON.

If not specified, the default is 6 hours.
This means Maintenance mode will turn itself OFF after 6 hours.

If ON Duration is specified without [D][H][M], the number is
interpreted as hours.

------------------------------

This MP creates a new class which contains all Windows Operating Systems. There are 2 rules in this class. One listens for the Maint Mode ON event and the other listens for the Maint Mode OFF event. The script on the RMS that turns on Maintenance Mode actually turns it on for all the components of the server and then turns it off again only for the Maint Mode class. This means that even in Maint Mode it can listen for the OFF event.

NOTE: The discovery for this class runs every 12 hours so be aware that systems may take this long after install for the scripts to work

Thanks again to Boris for his examples and scripts for doing maintenance mode.

 

NOTE:

Be aware the PowerShell execution policy might block the script from being run.

You may need to do the following:
1. Open the Command Shell, and do "set-executionpolicy remotesigned" (using "allsigned" may be considered a bit more secure.
2. Right-click on the .ps1 files, chose properties and click "Unblock" especially if you've downloaded these scripts using Internet Explorer.

 

Source: http://derekhar.blogspot.com/2008/08/updated-agent-maintenance-mode.html

 

Download scripts and Management Pack here:

AgentMaintMode.xml (19,78 kb)

MaintModeON.ps1 (2,00 kb)

MaintModeOFF.ps1 (1,49 kb)

MaintMode.vbs (2,89 kb)

 

Tags: