Submit a ticketCall us

Announcing NPM 12.2
With NPM 12.2 you can monitor your Cisco ASA firewalls, to monitor VPN tunnels for basic visibility and troubleshooting tunnels. NPM 12.2 also uses the SolarWinds Orion Installer so you can easily install and upgrade one or more Orion Platform products simultaneously.
See new features and improvements.

Home > Success Center > Patch Manager > Configuring Patch Manager with a Remote SQL Server

Configuring Patch Manager with a Remote SQL Server

Updated December 8th, 2015

Overview

When you are initially configuring Patch Manager with a remote SQL server, the program needs local logon access to the SQL server using the associated service account. This article contains the one-time and ongoing requirements for the SQL Server service account used to start the EminentWare Data Grid Server (EWDGS) service for Patch Manager, along with a workaround for those who do not want to afford ongoing local logon access to that EWDGS service account.

Environment

Patch Manager with Remote SQL Server

 

Detail

Requirements

Patch Manager requires the following to configure and communicate with a remote SQL server. Patch Manager revokes the "one-time" requirement after completing the initial configuration.

  • The service account must have local logon permissions on the remote SQL server (one-time).
  • The service account must be a member of the sysadmin group in SQL Server (ongoing).

Note: Patch Manager does not require the EWDGS service account to have any domain or local administrative permissions.

Workaround

Complete the following procedure if you do not want to afford ongoing local logon access to the SQL Server service account used for Patch Manager.

To configure Patch Manager with a remote SQL server without ongoing local logon access:

  1. Create a temporary service account to use for the initial Patch Manager configuration. Note: Ensure this service account meets both of the requirements previously noted.
  2. Complete the Patch Manager installation wizard, specifying the temporary service account to configure your remote SQL server.
  3. On the last screen of the installation wizard, clear Run EminentWare..., and then click Finish.
  4. Stop the EminentWare Data Grid Server service.
  5. You may delete the temporary service account at this point if you want.
  6. Clear the MEKey and MPKeystrings in the Registry:
    1. Open Registry Editor (regedit).
    2. Expand HKEY_LOCAL_MACHINE\SOFTWARE\EminentWare\Data Grid Service\Roles\Application, and then select Data.
    3. Select MEKey, and then click Edit > Modify.
    4. Clear the Value data field, and then click OK.
    5. Do the same for the MPKey string.
  7. Ensure the permanent SQL service account is listed in the Log on as a service Properties view in Local Security Policy.
  8. Change the account used to start the EminentWare Data Grid Server service:
    1. Go back to the Services window, and make sure you have the EminentWare Data Grid Server service selected.
    2. Click Action, and then select Properties.
    3. Click the Log On tab.
    4. Change the account used for the service here, and then click OK.
  9. Start the EminentWare Data Grid Server service.
  10. Open the Patch Manager/EminentWare console, and then complete the initial console configuration as instructed.

 

Last modified
15:54, 8 Sep 2017

Tags

Classifications

Public