Date: Thu, 28 Mar 2024 23:29:02 +0000 (UTC) Message-ID: <1243975118.69479.1711668542362@ip-10-0-1-26.ec2.internal> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_69478_1670494664.1711668542359" ------=_Part_69478_1670494664.1711668542359 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Before importing the SQLDM Manage= ment Pack for SCOM, you must import the relevant Microsoft Windows manageme= nt packs for your current operating system. For example, if SQL Diagnostic = Manager is installed on Windows Server 2008 R2, then you must install the m= anagement pack for that OS before continuing.
You can find the SQLDM MP (Idera.SQLDM.mp= ) in the root of the installation kit.
The SQLDM Management Pack requires that t= he SCOM agent has at least read access to the SQLDM Repository. Grant this = access before installing the SQLDM MP and enabling discovery of any SQL Dia= gnostic Manager installed instances.
SQLDM MP also requires that a SCOM agent = (version 2007 or above) be installed locally on each server where an instan= ce of SQL Diagnostic Manager is present. If an agent is not already install= ed, then use the Discovery Wizard in the SCOM Console to push the agent ins= tallation.
The SQLDM Management Pack import process = loads into the SCOM database the SQLDM MP settings, classes, and rules nece= ssary for monitoring SQL Diagnostic Manager. The import replicates the rele= vant rules and objects to all systems where SQL Diagnostic Manager is insta= lled.
The following steps hel= p you import the SQLDM Management Pack when it is downloaded to a hard driv= e local to the SCOM Console. For more information about other methods of im= porting the Management Pack, see How to Import a Management Pack in Operations Manager 2= 007.