Export (0) Print
Expand All

Deploying on Windows Server 2003 and SQL Server 2005

Updated: May 22, 2009

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 2003 MSCS clusters.

Before you start

  1. Create domain accounts for the following:

    • Management Server Action Account (MSAA), SDK and Config, Data Reader, Data Warehouse Write Action, and Operations Manager Administrators accounts

      ImportantImportant
      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 2005-based server that hosts the OperationsManager database. For more information, see the Operations Manager 2007 Security Guide.

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

    • Operations Manager Administrators Group

    • Cluster service account

    • SQL Service account

    • Domain groups for SQL Clustered Services, SQL Server, SQL Server Agent, Full-Text Search

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

    noteNote
    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, SDK and Config, and the SQL Service and Cluster service accounts to the Local Administrators group on each node.

  5. Plan network names for the following:

    • Each node in each cluster.

    • A network name by which the cluster can be accessed publicly (cluster name).

    • A network name for the SQL Server cluster (SQL network name).

    • An RMS network name.

  6. Plan IP addresses for the following:

    • The public-facing network adapter in each cluster node.

    • The private or heartbeat network adapter in each cluster node.

    • The cluster IP address.

    • 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:

High-level order of installations

  1. Install SQL Server 2005 Enterprise Edition database services in a two-node MSCS cluster.

    TipTip
    For more information about the types of cluster configurations that are supported, see the Operations Manager Supported Configurations at: http://go.microsoft.com/fwlink/?LinkID=144400

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

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

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

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

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

  7. Install ACS on a stand-alone server.

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

High-Level SQL Cluster Install Guidance

The following procedure provides high-level guidance for installing SQL Server in a cluster and is not a replacement for the SQL Server 2005 Online Books. It assumes that you already have access to a healthy two-node MSCS cluster that is dedicated to hosting the OperationsManager and Data Warehouse databases.

To install SQL Server in a cluster

  1. Log on to the active cluster node with an account that has local administrator rights.

  2. On the SQL Server 2005 Enterprise Edition (or SQL Server 2005 Standard Edition) installation media, double-click Splash.hta.

  3. Click Install SQL Server.

  4. Proceed through the Welcome and End User License Agreement screens, selecting the appropriate responses.

  5. Address any issues that are found by the System Configuration Check, and complete the product registration page.

  6. On the Components to Install page, select the SQL Server and Workstation components, Books Online and development tools options. When you select the SQL Server option, the Create a SQL Server failover cluster check box is enabled, and you must select this.

  7. On the Virtual SQL Server name page, type a unique instance name for your installation. This name will be used to identify the failover cluster on your network. This name must be different than the host cluster name.

  8. On the Virtual SQL Server Configuration page, enter one IP address for each network that is configured for client access.

  9. On the Cluster Group Selection page, select the group that contains the drive that you want to use for SQL Server from the Available Cluster Groups. This is where the SQL Server virtual SQL Server cluster resources are placed.

  10. On the Cluster Node Configuration page, select all nodes that are to be included in the failover cluster.

  11. On the Remote Account Information page, specify an account that has administrative rights on all cluster nodes.

    noteNote
    SQL Server will be installed on all cluster nodes and, therefore, only has to be run once.

  12. On the Service Accounts (Clusters) page, specify the user name and password for the SQL Service account.

  13. On the Domain Groups for Clustered Services page, provide a DomainName\GroupName for each clustered service that is being installed. In this case, for SQL Server, SQL Server Agent, and Full-Text Search.

  14. Select Windows Authentication.

  15. Accept the default values for the Collation Settings.

  16. Proceed through the Error and Usage Reporting Settings page, making the appropriate selections.

  17. On the Ready to Install page, click Install.

For more information about preparing and installing SQL Server 2005 in a failover cluster, see the "Before Installing Failover Clustering" topic and "How to: Create a New SQL Server 2005 Failover Cluster (Setup)" topic in the SQL Server 2005 Books Online.

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

This procedure assumes that you have access to a dedicated, healthy SQL Server 2005 cluster. The Database services and the Workstation components, Books Online and development tools components have been installed. The SQL Server installation must be at the level of SQL Server 2005 SP1, SQL Server 2005 SP2, or SQL Server 2005 SP3 with the kb918222 hotfixes for the database and tools components applied. To obtain the hotfixes for each platform (x86, x64, I64), see article 918222 in the Microsoft Knowledge Base (http://go.microsoft.com/fwlink/?LinkId=78950).

To check prerequisites for OperationsManager and Data Warehouse database installation

  1. Log on to Node 1 of the SQL Server 2005 Cluster with the Operations Manager Administrator account credentials.

  2. In the Cluster Administrator tool, ensure that the Cluster Group that hosts all the SQL Server Cluster resources is owned by Node 1.

  3. From your Operations Manager 2007 installation media, double-click SetupOM.exe to start the System Center Operations Manager 2007 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 Operational Database and Data Warehouse options, and then click Check.

    noteNote
    When the Operational Database and Data Warehouse components are selected, the Prerequisite Viewer checks for presence of 2048-MB Physical Memory, Windows Server 2003 SP1, SQL Server 2005 SP1, SQL Server 2005 SP2, or SQL Server 2005 SP3.

    noteNote
    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.

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

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

This section shows you how to install the OperationsManager and Data Warehouse databases onto a SQL Server 2005 MSCS cluster. It assumes that the MSCS cluster 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 2005 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 Operations Manager 2007 Start page, in the Prepare area, click the Check Prerequisites link to open the Prerequisite Viewer.

  4. In the Components box, select the Operational Database and Data Warehouse components, and then click Check.

  5. A status of Passed should be returned in the lower pane. If a status of Warning or Failed is returned, click More next to the status for information on why the prerequisite returned that status. Resolve the issues that are identified there and then rerun the prerequisite check. Repeat this process until all prerequisites achieve a passed status.

    noteNote
    By selecting the Operational Database and Data Warehouse components, the Prerequisite Viewer checks for the presence of Windows Server 2003 Service Pack 1 and Microsoft SQL Server 2005 Service Pack 1. These are minimum requirements; if you are running later versions of either of these, a status of passed will be returned.

  6. Click Close.

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

  8. On the Welcome page click Next.

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

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

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

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

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

  14. In the Configure Operations Manager Administrators area, click Browse to open the Select group search tool and type 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 click Check Names. When the group name is confirmed (becomes underlined), click OK.

  15. Click Next.

  16. 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.

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

  18. Click Next.

  19. On the Database and Log File Options page, accept the default value of OperationsManager for the SQL database name or change it as wanted. 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 the starting database size that you want. For more information about calculating a starting database size, see the Operations Manager 2007 Design guide at http://go.microsoft.com/fwlink/?LinkId=104550. The minimum starting database size is 500 MB.

  20. Click Next.

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

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

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

  24. 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, 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 OperationsManager database.

  4. Close SQL Server Management Studio

To install the Data Warehouse database

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

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

  3. On the 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 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 to 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 you want. If you decide to specify a different name, do not include a ”-” in the 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 the starting database size that you want. . For more information about calculating a starting database size, see the Operations Manager 2007 Design guide at http://go.microsoft.com/fwlink/?LinkId=104550. The minimum starting database size is 500 MB.

  13. Click Next.

  14. On the Microsoft Update page, optionally choose whether 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 completes successfully, click Finish on the Completing the System Center Operations Manager 2007 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 Log Shipping in the SQL Server 2005 documentation.

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

To set up transaction log shipping to a secondary server, see http://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.

noteNote
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 2005 cluster that was created in the ”Installing the OperationsManager and Data Warehouse Database in a SQL Server 2005 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 cluster group 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.

    noteNote
    If the RMS encryption keys were 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 earlier in this topic.

  • Optionally running SetSPN.exe if it did not succeed while running the InstallCluster action earlier in this topic.

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 and that the Cluster service account is a member of the domain Operations Manager Administrators security group.

    noteNote
    Having the Cluster service account in the Operations Manager Administrators group is necessary for creating the clustered configuration of RMS.

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

    • Windows Server 2003 SP1 or SP2

    • MDAC version 2.80.1022.0

    • .NET Framework version 2.0

    • .NET Framework version 3.0 components

    • WSMAN v 1.1

  3. Add the SDK and Config service accounts 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 Cluster Administrator tool from Administrative tools or by selecting Start - Run and running CluAdmin.

  6. If this is the first time that the Cluster Administrator tool has been run, you will be prompted to connect to a cluster. Select the Open connection to 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 Cluster Administrator tool, right-click the Groups folder to open the context menu, select New , and then select Group.

  8. On the New Group page, enter a name for the cluster group in the Name field, enter a description, and then click Next.

    noteNote
    For this procedure, the cluster group that is created will be called RMSClusterGroup, although you can rename it as you want to.

  9. On the Preferred Owners page, select all computers listed in the Available nodes list and Add them to the Preferred owners list. Then click Finish. You should see a dialog box that says, “Cluster group '<clustergroupname>' created successfully”. Click OK.

  10. In the Cluster Administrator tool, right-click RMSClusterGroup to open the context menu and select New -> Resource.

  11. On the New Resource page, create an IP Address resource with the following configuration and click Next.

    • Name RMS IP Address

    • Description This is the IP Address of the RMS Server.

    • Resource type IP Address

    • Group RMSClusterGroup

  12. On the Possible Owners page, ensure that all cluster nodes are listed in the Possible owners list, and then click Next.

  13. On the Dependencies page, click Next.

  14. On the TCP/IP Address Parameters page, enter a TCP/IP address for the RMSClusterGroup that is on the same subnet as the publicly accessible network adapters that the cluster nodes are using in the Address field. This is the IP address that will be registered for the RMS server in DNS.

  15. Enter the same value in the Subnet mask field that the cluster node publicly accessible network adapters are using. This field might be automatically populated.

  16. Select the publicly accessible network from the Network drop-down list. This might automatically populate.

  17. Ensure that the Enable NetBIOS for this address check box is selected, and click Finish.

  18. In the RMS cluster group, create a new Physical Disk resource (as in step 11) with the following configuration and click Next.

    • Name RMSPhysicalDisk

      noteNote
      RMSPhysicalDisk is being used for this procedure only, although you can rename this resource anything you want to.

    • Description This is the shared cluster disk resource that the RMS will use.

    • Resource type Physical Disk

    • Group RMSClusterGroup

  19. On the Possible Owners page, ensure that all cluster nodes are listed in the Possible owners list, and then click Next.

  20. On the Dependencies page, click Next.

  21. On the Disk Parameters page, select the drive letter of the dedicated RMS disk, and then click Finish.

    noteNote
    The disk partition that is used for this must already exist, be included as an available cluster resource, and be accessible by all cluster nodes.

  22. In the RMSClusterGroup, create a new Network Name resource (as in step 10) with the following configuration and click Next.

    • Name RMSNetworkName

      noteNote
      RMSNetworkName is being used for this procedure only, although you can rename this resource whatever you want to.

    • Description This resource defines the network name that the RMS server will be known by. It will be registered in DNS.

    • Resource type Network Name

    • Group RMSClusterGroup

  23. On the Possible Owners page, ensure that all cluster nodes are listed in the Possible owners list, and then click Next.

  24. On the Dependencies page, select the IP Address resource from the Available resources list, and click Add to place it in the Resource dependencies list. Click Next.

  25. On the Network Name Parameters page, enter a valid NetBIOS name in the Name field. Ensure that the DNS Registration Must Succeed and the Enable Kerberos Authentication check boxes are selected. Click Finish.

    ImportantImportant
    The value that is entered in the Name field is the server name that is used for the RMS server. It will be registered in DNS as an A record along with the value you entered in the IP Address resource.

  26. In Cluster Administrator, right-click the RMSClusterGroup object to open the context menu and select Bring Online.

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 cluster group is owned by the node that you are logged on to. For example, in a two-node cluster, log on to node 1, open Cluster Administrator, and select the Groups folder in the details pane. The value in the Owner column for the RMS cluster group should be the node that you are logged on to. If it is not, right-click the RMS cluster group, and select Move Group.

  3. On your installation media, start SetupOM.exe. This starts the System Center Operations Manager 2007 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.

    noteNote
    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.

    noteNote
    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 Pass 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 Setup Wizard on the Start page.

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

  4. On the Setup Wizard 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 Prerequisite Checker page, click Next.

  9. On the SQL Server Database Instance page, enter the SQL Server name and database instance in the SQL Database Name box. This is in the format of SQL Server\SQL Instance. Because 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 2005 in the cluster.

    noteNote
    To find the value, open Cluster Administrator on the SQL Server cluster, select the Resources folder, in the details pane, select the SQL Network Name resource and open its properties. Navigate to the Parameters tab. The value is in the Name field.

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

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

    noteNote
    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.

  12. Click Next.

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

    noteNote
    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. For more information about agent installation, see "Agent Deployment" in the Operations Manager 2007 Operations Guide.

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

    noteNote
    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.

    noteNote
    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.

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

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

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

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

    ImportantImportant
    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.

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

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

  20. On the Backup or Restore page, select Backup the Encryption Key, and click Next.

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

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

  22. 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.

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

noteNote
Be sure to copy the encryption key to a location that is accessible to 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.

noteNote
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 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 cluster group with an account that has administrative rights.

  2. In Cluster Administrator, right-click the RMSClusterGroup to open the context menu, select New, and then select Resource. This starts the New Resource Wizard.

  3. Create a Generic Service Cluster resource for the System Center Management service with the following settings:

    • Name RMS Management Service

      noteNote
      You can choose to name this resource anything you want, but for ease of use make it simple and descriptive.

    • Resource type Generic Service

    • Group RMSClusterGroup

  4. Click Next.

  5. On the Possible Owners page, ensure that all cluster nodes are listed in the Possible owners box. If they are not, then select the appropriate node in the Available nodes box and click Add to add them to the Possible owners box. Click Next.

  6. On the Dependencies page, select the RMSPhysicalDisk and RMSNetworkName resources from the Available resources box, click Add to move to the Resource dependencies box, and then click Next.

  7. On the Generic Service Parameters page, in the Service name field, enter HealthService

    ImportantImportant
    HealthService is the exact name of the service; this cannot be modified.

  8. Leave the Start parameters field empty.

  9. Select the Use Network Name for computer name check box, and then click Next.

  10. On the Registry Replication page, leave the Root Registry Key field blank, and then click Next to end the wizard.

  11. Repeat the same process for the System Center Management Configuration service and the System Center Data Access service using the following values:

    • For the Configuration service: Name RMS Configuration Service, Resource typeGeneric Service, Group RMSClusterGroup, Possible owners all nodes, Resource dependencies RMSPhysicalDisk and RMSNetworkName, Service NameOMCFG, select the Use Network Name for computer name, Root Registry Key blank.

    • For the Data Access Service: Name: RMS DataAccess Service, Resource typeGeneric Service, Group RMSClusterGroup, Possible owners all nodes, Resource dependencies RMSPhysicalDisk, RMSNetworkName, Service nameOMSDK, select the Use Network Name for computer name check box, Root Registry Key blank.

      ImportantImportant
      Do not bring the Management, the Configuration, or the Data Access resources online at this time.

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.

  2. Make sure that the Cluster service account has been added to the Operations Manager Administrators Global Security group.

Creating the Virtual RMS

To create the virtual Root Management Server

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

  2. On the Operations Manager 2007 installation media, locate the SecureStorageBackup.exe and the ManagementServerConfigTool.exe files in the \SupportTools folder.

  3. Copy these files to the installation folder for Operations Manager (typically Program Files\System Center Operations Manager 2007) on the RMS owning node if they are not already there.

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

  4. On the RMS owning node, 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.

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

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

    noteNote
    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.

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

  7. At a command prompt on each secondary management server, type cd <path to Operations Manager installation directory> and then press ENTER.

  8. To restore the key to each secondary management server, type the following, where <fileshare> is a share accessible by all cluster nodes:

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

    noteNote
    This will launch the Encryption Key Backup or Restore Wizard. Select the Restore option, and enter the path to the encryption key file. You must provide the same password that you entered to encrypt the file on the RMS node.

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

  10. In Cluster Administrator, expand the cluster, and then click Groups. In the results pane, make sure that the computer that is hosting the root management server appears in the Owner column. If the computer hosting the root management server does not appear as the owner, in the navigation pane, right-click the Operations Manager group and select Move Group to move the RMSClusterGroup to the node that is the RMS.

  11. 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.

    ImportantImportant
    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.

  12. On the RMS server, open a command prompt, type cd <path to Operations Manager installation directory>, and then press ENTER.

  13. 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 text box located on the Parameters tab of the Properties dialog box for the network name resource.

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

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

  14. In the Cluster Administrator, right-click the RMSClusterGroup to open the context menu and select Bring Online to bring all the RMSClusterGroup services online.

    noteNote
    If you did not run ManagementServerConfigTool.exe InstallCluster as an administrator account, go to step 15; otherwise, skip to step 16.

  15. If you are not running the ManagementServerConfigTool under the account that is running the Cluster service or is an administrator account, you must manually run the SetSPN utility. Disregard the SetSPN commands that appear in the ManagementServerConfigTool output, and instead use the following command—where <domain>\<user name> is the account that the Cluster service is running under, where the value for <VirtualManagementServerFQDN> is the same name you use for <VirtualManagementServerNetbios> with the domain extension appended, and where the value for <VirtualManagementServerNetbios> must be the value that appears in the Name box on the Parameters tab of the Properties dialog box for the network name resource:

    runas /user:<domain>\<user name> "SetSPN.exe -A MSomHSvc/<VirtualManagementServerFQDN> <VirtualManagementServerNetbios>"

    noteNote
    The SetSPN utility is available in the Windows 2000 Resource Kit (http://go.microsoft.com/fwlink/?LinkId=80094).

    noteNote
    Later, when you are installing stand-alone management servers, if they are not able to establish a secure Kerberos channel with the RMS, you should run the SetSPN command to ensure that the SPN has been set correctly. It is critical that the parameter MSomHSVC be used exactly as it is spelled because the System Center Management service on the stand-alone management servers establish a connection only with this object.

  16. Open the Cluster Administrator tool and right-click the RMSClusterGroup to open the context menu and select Move group. Repeat this so that the RMSClusterGroup is moved to each node.

    ImportantImportant
    The RMSClusterGroup must be moved and successfully come online 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 using the AddRMSNode action on any of the non-root management server cluster nodes. This is most likely caused by a cluster node not being 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. At a command prompt, 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 Parameters 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 on the Parameters tab of the Properties dialog box for the Disk Resource.

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.

    noteNote
    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 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 results 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 Cluster Administrator, point to Groups, and then click the Operations Manager group.

  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, 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 2005, 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 the Authentication list, select Windows Authentication; click Connect.

  9. In the Object Explorer pane, expand Databases, right-click Operations Manager, and then click Delete.

  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 Database Components in a SQL Server 2005 Cluster procedures.

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

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft