Archive for January 2011
When the agent is located in a domain separate from the domain where the Operations Manager management server is located, and no two-way trust exists between the two AD forests, certificates must be used so that authentication can take place between the agent and management server.
Anders Bengtsson wrote a excellent article on how to deploy SCOM to untrusted zones with Opalis
New great Integration Packs has been released for Microsoft System Center Opalis :
- Intregation Pack for Telnet, Ftp, Http (Rename the file to .OIP)
- Integration Pack for Text Manipulation
- Integration Pack for MSSQL Tasks
- Integration Pack for Windows Tasks
- Integration Pack for SharePoint
- Integration pack for Opalis logging
- Integration Pack for Data Manipulation
- Integration Pack for Exchange
- Integration Pack for Local Group and User Management
- The Opalis documentation exporter (to Visio and Word)
- The Opalis UI generator (browse policies and generate an XML file or web page)
Willemjan van Laarhoven wrote a great post on how to install SCOM Unix Agent without having the root password.
Promoting a new server as the new RMS of your SCOM infrastructure could be very useful when you want to upgrade your OS from Windows Server 2003 to Windows Server 2008.
The information below are coming directly from Microsoft TechNet, I just add some print screen for simplifying the procedure.
In the example, CENMOMRMS701 is my current RMS and CENMOMMS701 is the MS that I want to promote as RMS.
- Make sure that you have a backup of the databases and all servers.
- Backup the Key from the RMS by using SecureStorageBackup.exe
and copy it to the MS that you want to promote.
- Be sure to have all the services accounts passwords available.
- Be sure that no agent, no Linux servers, no website, no network devices that are currently monitored by the RMS.
To promote a management server to a root management server role
- On the management server that you want to promote, copy the ManagementServerConfigTool.exe tool from the SupportTools folder of the installation media to the installation folder (by default, C:\Program Files\System Center Operations Manager 2007), called installdir in this example.
- Open a command prompt window using the Run as Administrator option, and then change the folder to the installdir folder.
Type the following command:
SecureStorageBackup.exe Restore < filename >
Here, filename is the root management server encryption key backup file.
- Provide a password as required.
On the management server, open a command prompt window using the Run as Administrator option, and then type the following command:
You will see two warnings come up. The first warns you to backup your OperationsManager database, the second warns you to take the System Center Management, System Center Management Configuration and System Center Data Access services offline if your RMS is on a cluster. Type in Y for both.
Demote the original root management server to a management server by doing the following on the original root management server:
- Type the following command: ManagementServerConfigTool.exe UpdateDemotedRMS. Type in Y to the backup database warning.
- Stop System Center Management service
- Delete the existing subfolders of the Health Service State folder in the installdir.
- Start System Center Management service
To configure the reporting server with the name of the new root management server
- Log on to the reporting server.
- Navigate to the installation folder of Reporting Services for example, %ProgramFiles%\Microsoft SQL Server\MSSQL.2\Reporting Services\ReportServer if you are using SQL Server 2005 or %ProgramFiles%\Microsoft SQL Server\MSRS10.MSSQLSERVER\Reporting Services\ReportServer if you are using SQL Server 2008.
- Open the rsreportserver.config file in Notepad, and locate the two instances of <ServerName>ServerName</ServerName>, where ServerName is the name of the original root management server. Change ServerName to be the name of the new root management server.
- Save the file, and then close Notepad.
- Open the registry and locate the key HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft Operations Manager\3.0\Reporting.
- Change the DefaultSDKServiceMachine value to be the name of the new root management server.
To configure the data warehouse server with permissions for the new root management server
- On the server hosting the data warehouse, open Microsoft SQL Server Management Studio, and in the Object Explorer pane, navigate to Security and then expand Logins.
- Locate the account that corresponds to the new root management server and on which the System Center Data Access Service is running (if it’s running under LocalSystem, the format is <domain\computername$>).
- Right-click the account and select Properties.
- In the Login Properties dialog box, in the Select a page pane, select User Mapping.
- In the Users mapped to this login list, in the Map column, select the box that corresponds to the OperationsManagerDW database.
- In the Database role membership for: OperationsManagerDW list, ensure that the following items are selected: configsvc_users, db_datareader, db_datawriter, db_ddladmin, and sdk_users.
- Click OK to save your changes and to close the Login Properties dialog box.
Today, I will blog about the installation of the NetApp Management Pack for monitoring your storage environment directly in Microsoft Operations Manager 2007 R2.
This management is free and directly provided by NetApp, so there is no reason to not use it.
- Available on the NetApp Connect Website, you have to download the ApplianceWatchPRO2.1_x64_NetApp.exe file.
- Service account that could access to the NetApp Controller.
On the SCOM Root Management Server, each Management Servers and computers where you have SCOM console installed, run the ApplianceWatchPRO2.1_x64_NetApp.exe installer. The installation of this application is required everywhere you have SCOM console installed, if you want to be able to use Netapp task in directly from the Task pane of all your SCOM Consoles. If you don’t need that, just install the application on the RMS.
The setup is just a next-next, without any specific configuration. After the installation process, the official NetApp documentation and management packs are available in the installation folder.(by default located in : C:\Program Files\NetApp\ApplianceWatch PRO)
As always, read the documentation and after that import the following management pack (by default located in: C:\Program Files\NetApp\ApplianceWatch PRO) in SCOM Console:
Configure all your NetApp Controllers as Network Devices
Add all your NetApp Controllers as Network Devices, so you will have to know the Controllers IP and the SNMP community.
You could confirm the good working of the communication in the Network Devices State:
Set the credentials
After a few minutes, the controllers will appear in the Controllers
view from the NetApp folder in SCOM console, click on one controller and in the Action Pane
execute Data ONTAP : Manage Controller Credentials
Specify the credentials and protocol for each Controllers:
Enable the discovery
The Netapp management pack needs to run an automatic discovery every x times. Normally this discovery could be launch by any servers, but after several tests, I only succeeded to have it working when I run it from the RMS.
Go to Authoring > Management Pack Objects > Rules
and look for ‘Data ONTAP: Discovery Rule‘
Create an override to enable this rule and targeted it to the RMS:
The automatic discovery is now ok, if you want to force the discovery, go to Monitoring > Discovered Inventory and Change Target Type to Management Servers.
Click on the RMS and go to the Action Pane, and click on Data ONTAP : Run discovery task
and execute the task.
All the views
After a few hours, all the views will be populated with the data from the NetApp Controllers:
I hope this post help you with the installation of the NetApp Management for SCOM. Don’t hesitate to post a comment if you have any questions.