Export (0) Print
Expand All

How to Install Configuration Manager Using a Clustered SQL Server Instance

Applies To: System Center Configuration Manager 2007, System Center Configuration Manager 2007 R2, System Center Configuration Manager 2007 R3, System Center Configuration Manager 2007 SP1, System Center Configuration Manager 2007 SP2

The Configuration Manager 2007 site database can be installed using a clustered virtual Microsoft SQL Server instance during setup by using the following procedures.

noteNote
During Configuration Manager 2007 Setup, the Volume Shadow Copy Service (VSS) writer will be installed on each physical computer node of the Microsoft Windows Server cluster to support the Backup Site Server maintenance task.

To install Configuration Manager using a clustered SQL Server instance to host the site database

  1. Create the virtual SQL Server cluster to host the site database on an existing Windows Server cluster environment.

  2. Add the machine account of the primary site server machine to the Local Administrators group of each Windows Server cluster node computer. This is required to allow the site server to install and configure settings later.

  3. In the virtual SQL Server instance, assign the sysadmin SQL Server role to the user account running Configuration Manager Setup. After setup completes, both the user account that runs setup, and the site server computer account, must retain sysadmin rights to SQL Server. It is not supported to remove the sysadmin rights from these accounts.

  4. Start Configuration Manager Setup, and select to install Configuration Manager using custom settings.

  5. On the Configuration Manager Database Server page of the Configuration Manager Setup Wizard, enter the name of the clustered virtual SQL Server instance to host the site database and the name for the site database to be created on that instance by setup.

    ImportantImportant
    During setup, you must enter the name of the virtual SQL Server cluster instance, and not the virtual Windows Server name created by the Windows Server cluster. Installing the site database using the Windows Server cluster virtual instance name will result in the site database being installed on the local hard drive of the active Windows Server cluster node, and it will prevent successful failover if that node fails.

To verify that the site database was installed successfully

  1. Verify that Configuration Manager 2007 Setup completed successfully by reviewing the ConfigMgrSetup.log file located at the root of the system drive on the primary site server computer.

  2. In the SQL Server 2005 Management Studio console, verify that the site database was created successfully.

  3. In the SQL Server 2005 Management Studio console, verify that the following roles were created for the site database:

    • smsdbrole_MP

    • smsdbrole_SLP

    • smsdbrole_RP

    • smsdbrole_PSP

    • smsdbrole_DMP

    • smsdbrole_siteprovider

    • smsdbrole_siteserver

  4. Verify that the following SQL Server database roles for the site database have been assigned with the appropriate machine accounts:

    • smsdbrole_MP (if management point installation was selected)

    • smsdbrole_siteprovider (the site server or remote provider that was specified)

    • smsdbrole_siteserver (the primary site server computer)

See Also

For additional information, see Configuration Manager 2007 Information and Support.
To contact the documentation team, email SMSdocs@microsoft.com.
Was this page helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft