Windows Authentication for Commvault SQL Server Connections

You can change the default authentication mode from mixed mode to Windows authentication mode.

Symptoms

Your business needs require you to use Windows authentication mode, and you installed Commvault packages that included databases. The following Commvault packages include databases: CommServe, Metrics Reporting Server, Web Server, and Workflow Engine.

Agent packages and the MediaAgent package do not include a database.

Note: The Index Store and Content Extractor packages must be installed on a separate machine other than the CommServe machine where Windows authentication mode is enabled, as the Commvault services for these packages run with the network service account.

Resolution

1. From the Commvault Process Manager, stop all Commvault services.
2. Change all Commvault Services to use a domain system administrative account instead of a local system administrative account. For instructions, see "To configure how a service is started using the Windows interface" in the Microsoft TechNet article Configure How a Service Is Started. For step 5, follow the To specify another account substep. Note: When you upgrade the Commvault software to a new version or a new service pack, you must change all Commvault services to use a domain system administrative account.
3. On all computers that have a Commvault database, create the following registry key:
   • Location: HKEY_LOCAL_MACHINE\SOFTWARE\CommVault Systems\Galaxy\Instance001\Database
   • Name: nSQLAuthType
   • Type: DWORD
   • Values: 1 Note: 0 is SQL authentication (the default value), and 1 is Windows authentication.
4. On all computers that have Commvault database packages, complete the following steps to configure the Commvault system data sources to use Windows authentication:
   1. Open the ODBC Data Sources Administrator (64-bit) program.
   2. On the System DSN tab, complete the following steps to update each system data source: Note: The available installed Commvault databases are AppStudioDB, AuditDB, CacheDB, CommServ, CVCloud, DM2, HistoryDB, ResourceMgrDB, TemplateDB, and WFEngine.
      1. Double-click the data source. The configuration dialog box appears.
      2. Click Next. TheHow should SQL Server verify the authenticity of the login IDpage appears.
      3. Select With Integrated Windows authentication.
      4. Click Next until the Finish button is available, and then click Finish. The ODBC Microsoft SQL Server Setup dialog box appears.
      5. Click Test Data Source.
      6. After the test is successful, return to the list of system data sources and configure the remaining data sources.
   3. After you configure all the data sources, click OK to close the ODBC Data Source Administrative (64-bit) program.
5. On all computers that have a Commvault database, complete the following steps to update the application pools:
   1. Open the Internet Information Services (IIS) Manager.
   2. In the Connections pane, expand the Commvault client, and then click Application Pools.
   3. In the Application Pools pane, right-click ConsolesAppPool, and then click Advanced Settings.
   4. Under Process Model, click Identity, and then click the ellipsis (...). The Application Pool Identity dialog box appears.
   5. Click Custom Account, and then click Set. The Set Credential dialog box appears.
   6. Enter the domain system administrative account credentials, and then click OK.
   7. Click OK twice to return to the Application Pools pane.
   8. Repeat the preceding steps for WebSearchProxyApplicationPool.
   9. From the command line, run the iisreset command.
6. Update the SQL Server to Windows authentication mode. For instructions see the Microsoft article Change Server Authentication Mode.
7. Open services.msc, and then restart all SQL Server services.
8. From the Commvault Process Manager, restart all Commvault services.