Deploying on Windows Server 2008 and SQL Server 2008

  • Article

Applies To: Operations Manager 2007 R2, Operations Manager 2007 SP1

This section shows you how to prepare and install the OperationsDatabase and RMS into Windows Server 2008 failover clusters. It presumes that you have two Windows Server 2008 failover clusters, one for the OperationsManager, Data Warehouse, and ACS databases and one for the root management server.

Before you start

  1. Create domain accounts for the following:

    • Management Server Action Account (MSAA), System Center Data Access and System Center Management Configuration, (data access and config), Data Reader, Data Warehouse Write Action, and Operations Manager Administrators accounts.

      Important

      For this scenario, the MSAA must be a domain-based account, do not use Local System for the MSAA. In addition, the MSAA must have permissions on the SQL Server 2008-based server that hosts the OperationsManager database. For more information, see the Operations Manager 2007 Security Guide.

      Important

      When clustering the root management server, the Data Access and Config account must be a domain account and that one account should be fused on all cluster nodes and all secondary management servers. If you need to use different domain-based accounts for the System Center Data Access and the System Center Management Configuration services on the cluster node and secondary management servers, see https://go.microsoft.com/fwlink/?LinkId=108566 for more information before proceeding.

    • Operations Manager Administrators Group.

  2. Add the Operations Administrator domain account to the Operations Manager Administrators group.

    Note

    Adding these accounts to the Operations Manager Administrators group helps with setting up the RMS service in a clustered configuration and is not necessary for the SQL Database cluster configuration.

  3. Add the Operations Manager Administrators group to the Local Administrators Group on each node.

  4. Add the MSAA, Data Access and Config accounts to the Local Administrators group on each node.

  5. Plan network names for the following:

    • Each node in each cluster.

    • An RMS network name.

  6. Plan IP addresses for the following:

    • A SQL IP address.

    • An RMS IP address.

  7. Plan shared disk (clusterable disk) for the following:

    • The Quorum drive.

    • Dedicated disk for SQL data files.

    • Dedicated disk for SQL log files.

    • Dedicated disk for RMS files.

  8. Consider the following points for SQL Server clustering:

    • Prior to installing SQL Server 2008 Enterprise Edition in the cluster, you must create a Microsoft Distributed Transaction Coordinator (MSDTC) Resource in the Cluster Administrator. For more information about SQL Server 2008 Failover clustering see: Getting Started with SQL Server 2008 Failover Clustering.

High-level order of installations

  1. Install the OperationsManager database component in the SQL cluster.

  2. Install the Operations Manager Data Warehouse component in the SQL cluster.

  3. Install the Operations Manager 2007 management server and Operations console components in the other two-node MSCS cluster.

  4. Install one or more secondary management servers on stand-alone servers.

  5. Install SQL Server 2008 and SQL Server 2008 Reporting Services on a stand-alone server. This will be used for the Installing Reporting in the Multiple Server, Single Management Group procedure.

  6. Install ACS on a stand-alone server.

  7. Install Operations Manager gateway server on a stand-alone server.

Installing OperationsManager and Data Warehouse Components in a SQL Server 2008 Cluster

This procedure assumes that you have access to a dedicated, healthy SQL Server 2008 Failover cluster. The Database services and the Workstation components, Books Online and development tools components have been installed.

Note

If you are using SQL Server 2008 R2, you must install the Operations Manager 2007 R2 databases using the DBCreateWizard tool. See KB2425714 for details.

To check prerequisites for OperationsManager and Data Warehouse database installation

  1. Log on to Node 1 of the cluster that is to be used for SQL Server 2008 with the Operations Manager Administrator account credentials.

  2. In the Failover Cluster Management tool navigation pane, expand the cluster that you are installing the OperationsManager and Data Warehouse databases on.

  3. Expand the Services and Applications container and select your SQL Server instance.

  4. In the results pane, ensure that all your SQL Server resources are owned by Node 1 and that they are online. The required resources are:

    • Server Name and IP Address

    • Disk Drives

    • SQL Server

    • SQL Server Agent

  5. Ensure that the Data Transaction Coordinator is owned by and available on Node 1.

  6. Close the Failover Cluster Management Tool.

  7. From your installation media, start SetupOM.exe.

  8. On the System Center Operations Manager 2007 R2 Setup Start page, in the Prepare area, click Check Prerequisites to start the System Center Operations Manager 2007 R2 Prerequisite Viewer.

  9. In the Components box, select the Operational Database and Data Warehouse options, and then click Check. The results are displayed at the bottom of the Prerequisite Viewer. If there are any deficiencies, they are marked either as Warning or as Failed. Warnings can be ignored at the risk of degraded performance or other specific issues; Failed prerequisites must be fixed before the installation can proceed. You can close the Prerequisite Viewer, fix the items, and then rerun the Prerequisite Viewer checks as many times as necessary until a Pass evaluation is achieved on all items.

    Note

    When the Operational Database and Data Warehouse components are selected, the Prerequisite Viewerchecks for presence of 2048-MB Physical Memory, Windows Server 2003 SP1, and SQL Server 2005 SP1 or SQL Server 2008 SP1. Note that these are the minimum requirements; if your installation exceeds these, a status of Passed will be returned.

  10. When you are done with the Prerequisite Viewer, click Close.

Installing the OperationsManager and Data Warehouse Database in a SQL Server 2008 Cluster

This section shows you how to install the OperationsManager and Data Warehouse databases onto a SQL Server 2008 Failover cluster. It assumes that the MSCS cluster is operational and that the DTC resource has already been created.

To install the OperationsManager database

  1. Log on to cluster node 1 (the SQL Server 2008 owning node) with an account that has administrator rights and is a member of the Operations Manager Administrators group.

  2. On your Operations Manager 2007 installation media, start SetupOM.exe.

  3. On the Start page, in the Install area, click the Install Operations Manager 2007 R2 link.

  4. On the Welcome page, click Next.

  5. On the End User License Agreement (EULA) page, accept the agreement, and then click Next.

  6. On the Product Registration page, type in the 25-digit CD key. Optionally, type in appropriate values in the User Name and Organization fields, and then click Next.

  7. On the Custom Setup page, click the Database component, and then select This component and all dependent components, will be installed on local disk drive.

  8. Select the Management Server, User Interfaces, Command Shell, and Web Console components and set them to This component will not be available. Click Next.

  9. On the Management Group Configuration page, type in a name for your management group in the Management Group name box.

  10. In the Configure Operations Manager Administrators area, click Browse to open the Select group search tool and type in the name of the Operations Manager Administrators group that you created in the “Before you Start” section. Make sure that the From this location option is set to the domain that contains the group, and then click Check Names. When the group name is confirmed (becomes underlined), click OK.

  11. Click Next.

  12. On the SQL Server Database Instance page, select the SQL Server instance that you want to install on from the SQL Server database instance drop-down box.

  13. Accept the default value of 1433 in the SQL Server Port box or type the correct protocol number if you have changed the default SQL port for your SQL installation. Ignore the Second node of a Windows Server Cluster check box.

  14. Click Next.

  15. On the Database and Log File Options page, accept the default value of OperationsManager for the SQL database name or change it as desired. Ensure that the Data file and Log file locations are set to the shared disk that you created for this SQL instance. Accept the default Database size of 1000 MB or type in the desired starting database size. For more information on calculating a starting database seize, see the Operations Manager 2007 Design guide at https://go.microsoft.com/fwlink/?LinkId=104550. The minimum starting database size is 500 MB.

  16. Click Next.

  17. On the Operations Manager Error Reports page, optionally choose to send error reports to Microsoft and click Next.

  18. On the Microsoft Update page, optionally choose whether you want to use Microsoft Updates, and then click Next.

  19. On the Ready to Install the Program page, click Next when you are ready to start the installation.

  20. When setup completes successfully, click Finish on the Completing the System Center Operations Manager 2007 setup wizard page

To confirm the existence of the OperationsManager database

  1. On the owning node, and open SQL Server Management Studio.

  2. If prompted, logon to your database engine instance and expand the Databases folder.

  3. Check for the presence of the OperationsManager database.

  4. Close SQL Server Management Studio

To install the OperationsManagerDW database

  1. If the Operations Manager 2007 Start page is not already displayed, start SetupOM.exe on your installation media.

  2. On the Start page, in the Install area, click the Install Operations Manager 2007 R2 Reporting link.

  3. On the Operations Manager 2007 R2 Reporting Setup welcome page, click Next.

  4. On the End User License Agreement (EULA) page, click I accept the license agreement to accept the agreement, and then click Next.

  5. On the Product Registration page, optionally type appropriate values in the User Name and Organization fields, and then click Next.

  6. On the Custom Setup page, click the Data Warehouse component, and select This component and all dependent components will be installed on local disk drive.

  7. Click the Reporting component and select This component will not be available.

  8. Accept the default installation location, and then click Next.

  9. On the SQL Server Database Instance page, select your database instance from the drop-down list.

  10. Accept the default SQL Server port of 1433 or type the correct value if you have changes the default SQL port for your SQL instance.

  11. Click Next.

  12. On the Database and Log File Options page, accept the default value of OperationsManagerDW for the SQL database name or change it as desired. If you decided to specify a different name, do not insert a ‘-‘ in the database name as it will cause the installation to fail. Ensure that the Data file and Log file locations are set to the shared disk that you created for this SQL instance. Accept the default Database size of 1000 MB or type in the desired starting database size. For more information on calculating a starting database size, see the Operations Manager 2007 Design guide at https://go.microsoft.com/fwlink/?LinkId=104550. The minimum starting database size is 500 MB.

    Note

    If you are planning to install multiple OperationsManager, or Data Warehouse databases into the same SQL Server, you can use the setup wizard for the first installation, but you must use the dbcreatewizard for all subsequent database installations on the same SQL Server.

  13. Click Next.

  14. On the Microsoft Update page, optionally select if you want to use Microsoft Updates and click Next.

  15. On the Ready to Install the Program page, click Next when you are ready to start the installation.

  16. When setup is completed successfully, click Finish on the Completing the System Center Operations Manager 2007 R2 Reporting Components setup wizard page.

To confirm the existence of the Data Warehouse database

  1. On the owning node, open SQL Server Management Studio.

  2. If prompted, log on to your database engine instance and expand the Databases folder.

  3. Check for the presence of the Data Warehouse database.

  4. Close SQL Server Management Studio.

Using Log Shipping for the OperationsManager Database

Log shipping sends transaction logs from a primary to a secondary database, which keeps the secondary database nearly synchronized with the primary database. For more information about log shipping, see https://go.microsoft.com/fwlink/?LinkId=149021 in the SQL Server 2008 documentation.

To use log shipping, you need to set the OperationsManager database to use Full Recovery mode. For more information, see https://go.microsoft.com/fwlink/?LinkId=91991.

To set up transaction log shipping to a secondary server, see https://go.microsoft.com/fwlink/?LinkId=91992.

Deploying a Root Management Server on a Windows Cluster in Operations Manager 2007

The root management server (RMS) is the only management server in a management group that runs the System Center Data Access (previously named the SDK service) and the System Center Management Configuration (previously named the config service) services, and the management group cannot operate without these services. This makes these services a single point of failure. Just as the risk of the single OperationsManager database is mitigated by clustering it, so too can the risk of single instance of the Data Access and Management Configuration services be mitigated through clustering.

Note

Do not install agents on the cluster nodes that support the root management server. If you want to monitor the health of a root management server on a cluster as part of another management group, use agentless management.

In this procedure, the management server and user interface components are installed on the cluster, and it makes use of the OperationsManager database that is hosted on the SQL Server 2008 cluster that was created in the ‘Installing the OperationsManager and Data Warehouse Database in a SQL Server 2008 Cluster’ procedure.

The following procedures show how to install Operations Manager 2007 root management servers on a Windows cluster. Installing Operations Manager 2007 root management servers on a Windows cluster involves the following tasks:

  • Preparing the Windows cluster and creating a Service or Application for the RMS.

  • Creating Physical Disk, IP Address, and Network Name resources in the RMS cluster group.

  • Installing the RMS and secondary management servers on the cluster nodes and backing up the RMS encryption key.

  • Creating Generic Service cluster resources in the RMS cluster group for the RMS System Center Management (health) Service (HealthService), the RMS System Center Data Access (SDK) (OMSDK), and the RMS System Center Management Configuration (config) (OMCFG) services.

  • Backing up the OperationsManager database.

  • Running SecureStorageBackup with the Backup option on the RMS to back up the RMS encryption key.

    Note

    If the RMS encryption keys are successfully backed up at the end of the RMS setup, it is not necessary to back them up again at this point.

  • Running SecureStorageBackup with the Restore option on all secondary management servers to place the RMS key on them.

  • Running the ManagementServerConfigTool with the InstallCluster option to cluster the RMS cluster group resources.

  • Bringing all RMS cluster groups online.

  • Moving the RMS cluster group to each node to complete the configuration.

  • Testing to verify successful cluster installation.

  • Optionally running the ManagementServerConfigTool with the AddRMSNode option to add cluster nodes to the RMS cluster that were inaccessible during the InstallCluster action described previously.

  • Optionally running SetSPN.exe if it did not succeed while running the InstallCluster action described previously.

If you have previously installed or attempted to install Operations Manager on a cluster and that attempt has failed, see the additional procedure "To uninstall an Operations Manager 2007 in a cluster" prior to reinstalling.

To prepare the cluster nodes, the RMS cluster group, and the RMS cluster group resources

  1. On each RMS cluster node, ensure that the domain Operations Manager Administrators security group has been added to the local Administrators group.

  2. Ensure that each cluster node meets the prerequisites for the management server and User Interface components:

    • Windows Server 2003 SP1 or Windows Server 2008

    • MDAC version 2.80.1022.0 or later

    • .NET Framework version 2.0

    • .NET Framework version 3.0 features

    • WSMAN v 1.1 (this is only required if UNIX/Linux computers will be monitored in this management group).

  3. Add the Data Access and Config service account to the Local Administrators group on each node of the RMS cluster.

  4. Log on to the cluster node that will be the primary owning node for the RMS with administrative rights.

  5. Start the Failover Cluster Management tool from Administrative tools.

  6. If this is the first time that the Failover Cluster Management tool has been run, you will be prompted to connect to a cluster. Select the Manage a cluster option from the Action drop-down box and either enter or browse for the cluster name for the Cluster or server name box.

  7. In the Failover Cluster Management tool, right-click the Services and Applications folder to open the context menu and click Configure a Service or Application to start the High Availability Wizard.

  8. On the Before You Begin page, click Next.

    Note

    On the Select Service or Application page, select Other Server and click NEXT.

  9. On the Client Access Point page, type in the network name that you have planned for your rms. This name will be registered in DNS as an A record.

  10. Click the address box and type the IPv4 address you have planned for the rms. This is the publicly accessible address for the rms.

  11. Click Next.

  12. On the Select Storage page, select the disk resource that will be used for the rms. This should not be the quorum disk.

  13. Click Next.

  14. On the Select Resource Types page, click Next.

  15. On the Confirmation page, review the information and click Next.

  16. On the Summary page, optionally review the report and click Finish.

  17. Right-click the application that you just created and open its properties. On the General tab, optionally select a preferred owner node and on the Failover tab, accept the default failover values and ensure that the Prevent failback option is selected.

  18. Click OK.

To check prerequisites for RMS installation

  1. Log on to the cluster node that will be the primary owning node for the RMS with administrative rights.

  2. Ensure that the RMS application is owned by the node that you are logged onto. For example, in a two-node cluster, log on to node 1, open Failover Cluster Management, and select the RMS application in the navigation pane. The value in the Owner column for the RMS application should be the node that you are logged onto. If it is not, right-click the RMS application and move it to node 1.

  3. On your installation media, start SetupOM.exe. This starts the System Center Operations Manager 2007 R2 Setup on the Start page.

  4. Under the Prepare heading, click Check Prerequisites to start the Prerequisite Viewer.

  5. In the Components box, select the Server and Console components, and click Check.

    Note

    When these components are selected, the Prerequisite Viewer checks for presence of Windows Server 2003 SP1, MDAC version 2.80.1022.0 or later, .NET Framework version 2.0, .NET Framework version 3.0 components and for WSMAN v1.1.

    Note

    The results are displayed at the bottom of the Prerequisite Viewer. If there are any deficiencies, they are marked either as Warning or as Failed. Warnings can be ignored at the risk of degraded performance or other issues; Failed prerequisites must be fixed before the installation can proceed. You can close the Prerequisite Viewer, fix the items and rerun the Prerequisite Viewer checks as many times as necessary until a Passed evaluation is achieved on all items.

  6. When you are done with the Prerequisite Viewer, click Close.

Installing RMS

In this procedure, you install the first management server in the management group (the RMS).

To prepare the cluster and install RMS and User Interfaces components

  1. Log on to the cluster node that will be the primary owning node for the RMS with administrative rights.

  2. On your installation media, start SetupOM.exe. This starts the System Center Operations Manager 2007 R2 Setup Wizard on the Start page.

  3. Under the Install heading, click Install Operations Manager 2007 R2. This starts the Operations Manager 2007 R2 Setup Wizard.

  4. On the Welcome page, click Next.

  5. On the End User License Agreement page, select the I accept the terms in the license agreement option, and then click Next.

  6. On the Product Registration page, enter the appropriate values in the User Name and Organization fields. Enter your 25-digit CD Key, and then click Next.

  7. On the Custom Setup page, leave the management server and User Interfaces options set to This component, and all dependent components, will be installed on the local disk drive. Set the Database, Command Shell and Web Console components to This component will not be available, accept the default installation location, and then click Next.

  8. On the SQL Server Database Instance page, type the SQL Server name and database instance in the SQL Database Name box. This is in the format of SQL Server\SQL Instance. If the SQL Server database was installed in the default instance, you only need to enter the SQL Cluster name that was created when you installed SQL Server 2008 in the cluster.

  9. Check that the SQL Database Name field reads OperationsManager.

  10. Check that the SQL Server Port field has the value of 1433.

    Note

    If you have chosen a different port for SQL Server communications and have already configured that in SQL Server, you should enter that value here; otherwise, accept the default of 1433. If you have installed SQL Server using a named instance, type in the dynamic port value.

  11. Click Next.

  12. On the Management Server Action Account page, accept the default Domain or Local Computer Account option, enter the credentials of the MSAA, and then click Next.

    Note

    By using a domain-based account, it will be much easier to perform discovery and push agent installation later on than if you chose the Local System account.

  13. On the SDK and Config Service Account page, select the Domain or Local Account option, enter the credentials for the Data Access and Config service account, and then click Next.

    Note

    In this configuration, the account must be a domain account, because reporting is installed on a separate server. This account must have permissions on the reporting system.

    Note

    If you receive an Account Verification Error when you click Next, it is most likely that you mistyped the credentials or the SDK and Config service account was not added to the local Administrators group.

  14. On the Customer Experience Improvement Program page, optionally indicate whether you want to join this program, and then click Next.

  15. On the Microsoft Update page, optionally indicate whether you want to use the Microsoft Update services to check for updates, and then click Next.

  16. On the Ready to Install the Program page, click Install when you are ready for the installation to proceed.

  17. On the Completing the System Center Operations Manager 2007 R2 Setup Wizard page, clear the Start the Console check box, ensure that the Back up Encryption Key check box is selected, and then click Finish. The Encryption Key Backup or Restore Wizard will now launch.

    Important

    Even though the Operations console has been installed, do not launch the console at this point. Clear the Launch the Operations Console check box to prevent the Operations console from launching.

    Note

    If setup fails, it provides you with a value to search on and a link to open the setup log.

  18. On the Introduction page of the Encryption Key Backup or Restore Wizard, click Next.

  19. On the Backup or Restore? page, select Backup the Encryption Key option, and then click Next.

  20. On the Provide a Location page, specify a valid path and file name for the encryption key and click Next.

    Important

    It is critical that the location provided for backing up the encryption key be accessible to all nodes in the cluster.

  21. On the Provide a Password page, enter a password to secure the encryption key backup file and click Next to start the backup process. You will be prompted for this password when you restore the RMS encryption key later in this procedure.

  22. You should see the Secure Storage Backup Complete page. Click Finish.

Note

Be sure to copy the encryption key to a location that is accessible by all computers that will be management servers. Also be sure to make multiple copies and store them in separate, secure locations.

Installing the Secondary Management Servers

In this procedure, you will install secondary management servers on all other nodes in the cluster. These servers are secondary management servers until this process is complete, at which time they will be able to host the root management server.

To install secondary management servers in the RMS cluster

  1. Log on to each remaining cluster node with the Operations Manager Administrator account.

  2. Follow the ‘Install RMS’ procedures to install the management server and User Interface components on each of the other nodes in the management group.

  3. Do not start the console.

Note

If you choose to install any management server without the User Interfaces component and you want to run SecureStorageBackup.exe, you must copy Microsoft.EnterpriseManagement.UI.ConsoleFramework.dll, Microsoft.Mom.UI.Common.dll, and SecureStorageBackup.exe from the installation media (make sure to copy the correct platform version x86 or x64) to the installation directory on the management server. Typically this is C:\Program Files\System Center Operations Manager 2007.

Preparing RMS Cluster Resources

In this procedure, you create cluster resources out of the System Center Management service (HealthService), the System Center Management Configuration service (OMCFG), and the System Center Data Access service (OMSDK). These are the RMS resources that can fail over between cluster nodes along with the network name, IP address, and physical disk.

To prepare RMS cluster resources

  1. Log on to the node that is the owner of the RMS application with an account that has administrative rights.

  2. In Failover Cluster Management, right-click the RMS application in the navigation pane, and then select Add a resource 4-Generic Service.

  3. On the Select Service page, select the System Center Management Service, and click Next.

  4. On the Summary page, click Finish.

  5. In the summary pane of your RMS application, right click the System Center Management resource and open its properties.

  6. On the Dependencies tab, click Insert, and select the shared disk that you prepared for the RMS cluster from the Resource list.

  7. Click Insert again and select the network name from the Resource list.

  8. Click Apply.

  9. On the General tab, select the Use Network Name for computer name option.

  10. Click Apply.

  11. Click OK

  12. Repeat the same process for the System Center Management Configuration service and the System Center Data Access service.

Creating the RMS Cluster

In this procedure, you distribute the RMS Key to the secondary management servers and create the RMS cluster. At the end of this procedure, all nodes in a cluster can host the RMS.

Before you start

  1. Ensure that the file share with the encryption key is accessible by all cluster nodes. This is used for distributing the RMS Key.

Creating the Virtual RMS

To create the virtual Root Management Server

  1. Log on to the computer that owns the RMS application with an account that is a member of the Administrators group.

  2. If you successfully backed up the encryption key at the end of RMS setup, you can skip to step 5.

  3. On the RMS owning node, as an Administrator, open a Command Prompt window and change current directory to the Operations Manager installation folder; for example, cd\Program Files\System Center Operations Manager 2007.

  4. To back up the RMS Key, type the following, where <fileshare> is a share accessible to all cluster nodes:

    SecureStorageBackup.exe Backup \\<fileshare>\<filename>.bin.

    Note

    This will launch the Encryption Key Backup or Restore Wizard. A password will be requested. It must be at least eight characters long and must include at least one symbol. You must confirm the password to create the encryption key file.

  5. Log on to each secondary management server computer with an account that is a member of the Administrators group.

  6. On each secondary management server, navigate to the Operations Manager installation directory and launch SecureStorageBackup.exe as an administrator.

  7. This will launch the Encryption Key Backup or Restore Wizard. On the Introduction page, click Next.

    Note

  8. On the Provide a Location page, type in the path or browse to the encryption key file and click Next.

  9. On the Provide a Password page type in the password that you used when you backed up the encryption key and click Next.

  10. Click Finish.

  11. Log on to the RMS computer with an account that is a member of the Administrators group.

  12. In Failover Cluster Management, expand the cluster, and ensure that the RMS application is owned by node 1.

  13. On the SQL Server-based computer that hosts the OperationsManager database, open the SQL Server Management Studio tool, open the Databases folder, and select the OperationsManager database. Right-click to open the context sensitive menu and select Tasks, Back Up to initiate a backup. On the Back Up Database - OperationsManager page, ensure that the Backup type value is set to Full, give the Backup set an appropriate name, and set the Backup set will expire value to a date in the distant future. In the Destination box, for the Back up to value, select Disk and add an appropriate disk location to hold the backup, if one is not already present, and then click OK.

    Important

    When you run the ManagementServerConfigTool to create the RMS cluster, you are advised to back up the OperationsManager database because irrecoverable damage can be done by creating the RMS cluster if something is done incorrectly.

  14. On the RMS server, as an Administrator, open a Command Prompt window, type cd <path to Operations Manager installation directory>, and then press ENTER.

  15. To instantiate the RMS cluster group as a cluster, type the following, where G is the disk resource that is allocated to the cluster group that is being used to create this virtual Root Management Server and where <VirtualServerNetbiosName> is the network name resource allocated to the same cluster group:

    ManagementServerConfigTool.exe InstallCluster /vs:<VirtualServerNetbiosName> /Disk:G

    The value you enter for <VirtualServerNetbiosName> must be the value that appears in the Name box on the General tab of the Properties dialog box.

    Note

    ManagementServerConfigTool.exe InstallCluster will install the RMS as a clustered service on every available node in the cluster.

    Note

    When you run the ManagementServerConfigTool, the output might display instructions for running the SetSPN command; these instructions can be ignored.

  16. In Failover Cluster Management, right-click the RMS application to open the context menu and select Bring Online to bring all the RMS applications online.

  17. Open Failover Cluster Management and right-click the RMS application to open the context menu. Select Move this service or application to another node and select the next node in the cluster. Repeat this so that the RMS application is moved to each node of the cluster.

    Important

    The RMS application must be moved and come online successfully on each cluster node to set the state of the services correctly on each node at this time. Do not skip this step.

Clustered RMS setup is complete.

Preparing an Inaccessible Management Server

The following procedure is required only if, in bringing the cluster group online, the output stated that you are required to run the ManagementServerConfigTool.exe tool by using the AddRMSNode action on any of the non-root management server cluster nodes. This is most likely caused by a cluster node that is not accessible when the InstallCluster action was executed or you are adding a new node to the cluster.

To prepare inaccessible management servers

  1. Log on to the computer that hosts the management server as a member of the Administrators group.

  2. Open the services snap-in and if the startup type for the System Center Data Access Service is set to Disabled, change it to Manual.

  3. As an administrator, open a Command Prompt window , change directories to the installation folder, and type the following:

    ManagementServerConfigTool.exe AddRMSNode /vs:<VirtualServerNetbiosName> /Disk:<VirtualServer Disk Resource>

    VirtualServerNetbiosName is the Network Name resource allocated to the same cluster group. The value you enter for VirtualServerNetbiosName must be the value that appears in the Name box on the General tab of the Properties dialog box for the Network Name Cluster resource.

    VirtualServerDiskResource is the disk resource allocated to the cluster group being used to create this Virtual root management server. The Disk location can be found in the results pane of the properties for the RMS application.

Testing the Cluster Installation

Use the following procedure to test the cluster installation.

To test an Operations Manager 2007 cluster

  1. In the Operations console, click Administration.

    Note

    When you run the Operations console on a computer that is not a management server, the Connect To Server dialog box appears. In the Server name text box, type the name of the RMS Server (the cluster virtual server name) that you want the Operations console to connect to.

  2. In the Administration pane, point to Administration, point to Device Management, and then click Management Server.

  3. In the management servers pane, the RMS Server Network Name should appear with a health state of Healthy.

  4. In the Administration pane, click Agentless Managed.

  5. In the Agentless Managed pane, the entry for each node in the cluster should appear with a health state of Healthy.

Uninstalling Operations Manager 2007

Use the following procedure to uninstall Operations Manager 2007.

To uninstall Operations Manager 2007 from a cluster

  1. In Failover Cluster Management, select the RMS application.

  2. In the right page, right-click each of the three System Center services, and then click Take Offline.

  3. In the right page, right-click each of the three System Center services, and then click Delete.

  4. Perform the following steps on every node in the cluster that a management server was installed on:

    1. On the computer, click Start, point to Settings, and then click Control Panel.

    2. In Control Panel, double-click Add or Remove Programs, click System Center Operations Manager 2007 R2, and then click Remove.

    3. Close Control Panel.

    4. Delete the \Program Files\System Center Operations Manager 2007 folder and all subfolders and files.

    5. Delete the following registry keys:

    • HKLM/SOFTWARE/Microsoft/Microsoft Operations Manager

    • HKLM/SYSTEM/CurrentControlSet/Services/HealthService

    • HKLM/SYSTEM/CurrentControlSet/Services/MOM Connector

  5. On the computer that is the active node of the cluster, open Windows Explorer, and on the shared cluster disk resource, delete the three service state folders which are System Center Configuration Service State, System Center Management Service State, and System Center Data Access Service State.

  6. Use Add or Remove Programs to uninstall any Operations Manager database and Operations console that you have installed.

  7. On the Windows desktop, click Start, point to Programs, point to Microsoft SQL Server 2008, and then click SQL Server Management Studio.

  8. In the Connect to Server dialog box, do the following: in the Server Type list, select Database Engine; in the Server Name list, select the server and instance for your Operations Manager database (for example, computer\INSTANCE1); in Authentication list, select Windows Authentication; click Connect.

  9. In the Object Explorer pane, expand Databases, right-click Operations Manager, and then click Delete. Repeat this for any other Operations Manager 2007 R2 databases.

  10. In the Delete Object dialog box, select Close Existing Connections, and then click OK. You are ready to reinstall starting with Installing Operations Manager 2007 R2 Database Components in a SQL Server 2008 Cluster procedures.

    Note

    If you uninstall Server Components of Operations Manager 2007, the Operations Manager event log remains following the uninstall, by design. This causes the Operations Manager installation folder to remain also (default: %ProgramFiles%\Microsoft System Center Operations Manager 2007).