Submit a ticketCall us

Get a crash course on Network Monitoring delivered right to your inbox
This free 7-day email course provides a primer to the philosophy, theory, and fundamental concepts involved in IT monitoring. Lessons will explain not only how to perform various monitoring tasks, but why and when you should use them. Sign up now.

Home > Success Center > Patch Manager > Migrate a local or remote Patch Manager database to a remote SQL server

Migrate a local or remote Patch Manager database to a remote SQL server

Created by Interspire Import, last modified by Rodim Suarez on Apr 20, 2017

Views: 483 Votes: 5 Revisions: 18

Overview

This article provides steps on how to migrate a Patch Manager database from the Patch Manager server to a remote Microsoft SQL server.

Requirements

  • Microsoft SQL Management Studio for the version of Microsoft SQL you are using.
  • A domain account to be assigned as the service account for the EminentWare Data Grid Server service. Initially, this account should have the SQL SysAdmin role.
  • The following versions of these Microsoft components:
    • Microsoft SQL Server 2005 Native Client 
    • Microsoft SQL Server 2005 Management Objects Collection

 

To verify orobtain the correct version of Microsoft SQL Management Studio:

  1. Determine the version and edition of the Microsoft SQL Server you are running. For additional information, see this MSDN article.  (© 2016 Microsoft available at https://www.microsoft.com/en-us/, obtained on May 4, 2016.)
  2. Find the version number associated with the version and edition that you are running using this reference page(© 2016 SQLTeam Publishing, LLC available at http://www.sqlteam.com/, obtained on May 4, 2016.)
  3. Use the version number to find the appropriate version of Microsoft SQL Management Studio.

Note: Patch Manager installs Microsoft SQL Server 2005 Express Edition SP 3 (9.00.4035) by default. If you are using the default version of Microsoft SQL Server, download Microsoft SQL Server Management Studio Express SP 3 here.  (© 2016 Microsoft available at https://www.microsoft.com/en-us/, obtained on May 4, 2016.)

 

Note:

Migration of a Patch Manager server is not a supported activity. This will require installation of a new Patch Manager server on the Windows server .

As a workaround:

  1. Install the new Patch Manager server in Evaluation mode and get everything configured (except for the 3rd Party Updates catalogs).
  2. Deactivate the original Patch Manager server license (this will put it back in Evaluation mode, and you should have 30 days to wrap up its use).
  3. Activate the new Patch Manager server and configure the 3rd Party Updates catalogs.

Environment

All Patch Manager versions

Steps

  1. Close the Patch Manager/EminentWare console.
  2. Stop the EminentWare Data Grid Server service.
  3. Open SQL Management Studio. If you do not have SQL Management Studio, see the Requirements section..
  4. Connect to the .\EMINENTWARE database instance, and then detach the Patch Manager/EminentWare database. For additional information, see this MSDN article. (© 2016 Microsoft available at https://www.microsoft.com/en-us/, obtained on May 4, 2016.)
  5. Clear the MEKey and MPKey registry strings on the Patch Manager server:
    1. Open Registry Editor.
    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.
  6. Change the account used to start the EminentWare Data Grid Server service to the domain account identified in the Requirements section:
    Note: For same domain accounts on a new server, the account can be left the same for the login tab of the 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 here, and then click OK (Make sure that the account is set in the form DOMAIN\AccountName).
  7. Change the ConnectionString registry string on the Patch Manager server:
    1. Go back to Registry Editor.
    2. Select HKEY_LOCAL_MACHINE\SOFTWARE\EminentWare\Data Grid Service.
    3. Select ConnectionString, and then click Edit > Modify.
    4. Change the Value data field to address the remote SQL server. The default value is Data Source=serverName\EMINENTWARE;Initial Catalog=EminentWare;Integrated Security=True, where serverName is the name of the SQL server.
    5. Click OK.
  8. Back in SQL Management Studio, connect to the new database instance, and then attach the Patch Manager/EminentWare database. For additional information, see this MSDN article. (© 2016 Microsoft available at https://www.microsoft.com/en-us/, obtained on May 4, 2016.)
  9. Run DBHelper.exe on the Patch Manager server to specify the new SQL server location and credentials.  The default path is: C:\Program Files\SolarWinds\Patch Manager\Server.
    1. Open a Command Prompt as an administrator.
    2. Change directories to C:\ProgramFiles\SolarWinds\Patch Manager\Server.
    3. Enter dbhelper.exe /s newSQLServerName\instance /p createlogins /u domainName\username /o c:\output.ini, where:

      newSQLServerName is the name of your new SQL server,

      instance is the name of your new database instance,

      domainName is the domain for the domain service account, and

      username is the username for the domain service account.

  10. Start the EminentWare Data Grid Server service.
  11. Open the Patch Manager/EminentWare console and update all of the stored credentials. See the Changing the account or password used for the EminentWare Data Grid Server service article and make sure to apply all the necessary updates.

 

Disclaimer: Please note, any content posted herein is provided as a suggestion or recommendation to you for your internal use. This is not part of the SolarWinds software or documentation that you purchased from SolarWinds, and the information set forth herein may come from third parties. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment.  You elect to use third party content at your own risk, and you will be solely responsible for the incorporation of the same, if any.

 


 

Last modified
20:50, 19 Apr 2017

Tags

Classifications

Public