Installation guide

Installation Guide 103
Migrating Existing Databases to SQL Server 2000
Installing SQL Server 2000
Now that you have successfully backed up the ePolicy Orchestrator 3.0 databases,
you can install SQL Server 2000. Use the installation or upgrade procedure that is
recommended by Microsoft. At press time, the SQL Server and Microsoft
Developer Network (MSDN) home pages were located at:
SQL Server home page:
http://www.microsoft.com/sql/default.asp
MSDN home page:
http://msdn.microsoft.com/default.asp
NOTE
You can move the ePolicy Orchestrator database to a different
computer, but the name of the computer on which the ePolicy
Orchestrator server resides cannot change. If you move the
database, you will need to change the server configuration to
use the new location. For information on this procedure, see
Configuring the ePolicy Orchestrator server on page 103.
Configuring the ePolicy Orchestrator server
If you moved the ePolicy Orchestrator database to a different computer, you need
to change the server configuration to use the new location before you can connect
to it from ePolicy Orchestrator.
1 Start the Server Configuration program (CFGNAIMS.EXE). The default location
is:
C:\PROGRAM FILES\NETWORK ASSOCIATES\EPO\3
2 In the Server Configuration dialog box on the SQL Server tab, select the desired
SQL server name and Database name.
3 Click OK to save the current entries.
Starting the ePolicy Orchestrator server service
Before you can begin using ePolicy Orchestrator, you need to restart the ePolicy
Orchestrator server service (
McAfee ePolicy Orchestrator 3.0 Server). Depending on
the operating system that you are using, this procedure varies. For instructions, see
the Microsoft product documentation.