Infrastructure

Moving an ePO 4.0 database.

Solution

IMPORTANT:
These instructions are intended to be used by ePO administrators. You are responsible for preventing any adverse effects as a result of following these instructions. Before proceeding, McAfee strongly recommends that you back up the MSDE or SQL database and verify that the backup will restore successfully. For information related to backing up the ePO database using the dbbak.exe utility, command line, or SQL Enterprise Manager, see: KB59562.

 
 

Step 1 – Stop services on ePO server

  1. Click Start, Run, type services.msc and click OK.
  2. Right-click on the following services and select Stop:

    For ePO 4.0
    -McAfee ePolicy Orchestrator 4.0.0 Application Server
    -McAfee ePolicy Orchestrator 4.0.0 Server
    -McAfee ePolicy Orchestrator 4.0.0 Event Parser
     
     

Step 2 – Back up the ePO database on existing SQL/MSDE server using one of the various methods listed below

KB59562 – How to back up the ePO/PrP databases using OSQL commands
KB52126 – How to back up and restore the ePO/PrP databases using Enterprise Manager/ Management Studio
KB57240 – How to back up and restore the ePO/PrP databases using the DBBak.Exe utility
KB59855 – How to back up and restore the ePO database using SQLCMD commands (for SQL 2005 and SQL 2005 Express)

 

Step 3 – Restore the newly created backup on the new SQL server using one of the various methods listed below

KB52126 – How to back up and restore the ePO/PrP databases using Enterprise Manager/ Management Studio
KB57240 – How to back up and restore the ePO/PrP databases using the DBBak.Exe utility
KB59855 – How to back up and restore the ePO database using SQLCMD commands (for SQL 2005 and SQL 2005 Express)
 

 

Step 4 -Delete registry values on the ePO server

IMPORTANT:
Only implement this step if you migrate the database from a local SQL server or MSDE server to a remote SQL server or MSDE server. 

 

CAUTION: This article contains information about opening or modifying the registry.

  • The following information is intended for System Administrators. Registry modifications are irreversible and could cause system failure if done incorrectly.
  • Before proceeding, McAfee strongly recommends backing up your registry and understanding the restore process. For more information, see: http://support.microsoft.com/kb/256986
  • Do not run a .REG file that is not confirmed to be a genuine registry import file.

 
 

For ePO 4.0:

  1. Click Start, Run, type: regedit, and click OK.
  2. Navigate to the following registry key: [HKLM\System\Current ControlSet\Services\MCAFEEEVENTPARERSRV]
  3. Right-click the value DependOnService and select Delete.
  4. Navigate to the following registry key: [HKLM\System\Current ControlSet\Services\MCAFEEAPACHESRV]
  5. Right-click the value DependOnService and select Delete.
  6. Navigate to the following registry key: [HKLM\System\Current ControlSet\Services\MCAFEETOMCATESRV]
  7. Right-click the value DependOnService and select Delete.

Step 5 – Create the ePO SQL-Jobs on new SQL server

  1. Copy SQL-Jobs.sql from the ePO installation directory (…\Program Files\Network Associates\ePO\3.6.x) to your desktop.
  2. Open SQL-Jobs.sql in Notepad.
  3. Replace all instances of SERVERNAME_ePO to ePO DatabaseName.
  4. Save and close SQL-Jobs.sql.
  5. Run the new SQL-Jobs.sql through Query Analyzer (SQL 2000) or Management Studio (SQL 2005).

NOTE: When SQL-Jobs.sql is run on SQL 2005 Management console you might see messages similar to the following one. These are warning messages only and can be ignored.

(1 row(s) affected)
Msg 207, Level 16, State 1, Line 2
Invalid column name ‘name’.
Msg 207, Level 16, State 1, Line 2
Invalid column name ‘name’.
Msg 207, Level 16, State 1, Line 2
Invalid column name ‘name’.
Msg 207, Level 16, State 1, Line 2
Invalid column name ‘name’.
Msg 207, Level 16, State 1, Line 2
Invalid column name ‘name’.
Msg 207, Level 16, State 1, Line 2
Invalid column name ‘name’.

The script successfully runs and creates the epo_compliance_comparison.job as intended. To check if this was successful:

  1. Open SQL 2005 Management Console.
  2. Expand the Server to reveal all sub objects.
  3. Expand SQL Server Agent object and then Jobs.
  4. Verify epo_compliance_comparison is present. 

 

Step 6 – Verify and change the SQL port to the port that the new SQL server is using, if necessary

  1. Verify the SQL port that the new server is using against what the ePO server is currently configured to use.
    NOTE:
    If moving an MSDE database to a remote SQL server, the SQL ports will most likely be different and must be changed.

    SQL 2005:

    1. Click Start , All Programs, Microsoft SQL Server 2005, Configuration Tool and then SQL Server Configuration Manager.
    2. Click on SQL Server 2005 Network Configuration, Protocols for MSSQLSERVER (MSSQLSERVER is the instance name).
    3. Right-click on TCP/IP and select Properties.
      NOTE:
      TCP port 1433 displays in the Default port: field by default.

  2. If the ports are different, change the SQL port on the new SQL server to the port that the new SQL server is using, per the methods listed in article KB58019.


Step 7 – Open CfgNaiMs.Exe on ePO server and change the servername entry to the new SQL server

For ePO 4.0:

Use the following procedure to open the Database Configuration page for ePO 4.0 using a web connection:

  • Launch Internet Explorer.
  • To open the Configure Database Settings page, go to: https://<servername>:8443/core/config

    NOTE:
    If you do not use the default port (8443), substitute the console login port you configured. A specific server name can be used in the example above only if you can resolve that name in your environment.
     

  • Under Configure Database Settings, modify the following entries, as required:
    • Database server
    • Server instance
    • Database name
    • Authentication type
    • User name
    • User password

      NOTE:
      If you make any changes to these entries, ensure that you click Test Connection (bottom right corner) to verify the connection to the database is successful with the new settings before continuing.

  • Click Apply.

 

Step 8 – Open the installation registry key on the ePO server and modify the listed entries

CAUTION: This article contains information about opening or modifying the registry.

  • The following information is intended for System Administrators. Registry modifications are irreversible and could cause system failure if done incorrectly.
  • Before proceeding, McAfee strongly recommends backing up your registry and understanding the restore process. For more information, see: http://support.microsoft.com/kb/256986
  • Do not run a .REG file that is not confirmed to be a genuine registry import file.
  • Click Start, Run, type regedit, and click OK.
  • Navigate to the following registry key:

    For ePO 4.0: [HKLM\Software\Microsoft\Windows\CurrentVersion\Uninstall\{AF05AA5C-1B53-45DE-9FFD-8F37F329A4BC}]
     

  • Modify the following entries:
     
    • DatabaseInstanceName – if the new server is using a default instance, change it to MSSQLSERVER. Otherwise, specify just the instance name it is using. (Example: Specify only instancename, not servername\instancename)
    • DatabaseServer – type the new SQL server name.
    • DatabaseUsername – if different, enter new user name (account configured in SQL with DBO rights to the database. See KB45632
      for additional information on required SQL permissions.
    • IsUsingMSDE – set value to 0.
    • SQLAccount – if using SQL authentication, value should be 1. If NT authentication is being used, value should be 0.
    • SQLPort – new port #.


Step 9
– Restart the ePO server

You must restart your system for the removed dependencies to take effect, otherwise the ePO services will not start.

NOTE:
After the restart, MSDE can now be uninstalled, if required.

Leave a Reply