I am a noob when it comes to ePO, we have no real experience in-house, what I would like advice about is I have built the new 2008 server and I have run the McAfee compatibility check on the old server and here are the results…

McAfee ePolicy Orchestrator Product Compatibility Check

************

These products are incompatible with ePO version 5.0; they must be removed or upgraded before ePO setup can continue:

Anti-Spyware Enterprise 8.7.0.107 (VSEMAS870000) - no known compatible version

GroupShield for Lotus Domino 7.0.1105.104 (GSD7REPORTS) - no known compatible version

If you are going from x86 to x64 then you would transfer your systems from 4.5.7 to 5.0.1

You import the epo v 5 keys into v4 and (page 124 of ePO 5 product guide) register the server. Then 'transfer systems' to the new one.

I'm currently doing something similar- 4.5.4HF1 (x86) to 4.6.6 (x64) in preperation for upgrading to epo 5. I exported all my policies and tasks and imported them into the new EPO sever. When i transferred the systems they picked up the correct policies.

However, it doesn't transfer assigned encrypted users on machines that are encrypted (calling out for a product enhancement there!) so beware of any encrypted machines you have.

I sent up the same structure and assigned the tasks and policies to teh correct groups first, then tested a couple of machines to see how it went..

The migration tool will do this for you - but to answer your earlier question, it won't move the database for you. If the DB is currently on the same machine as the 4.5 server and you're intending to move it to the ePO 5 server, then I would move the DB to the ePO 5 server first, then run the migration tool. Something like this:

Install SQL on the ePO 5 server

Stop the ePO 4.5 services

Back up the ePO DB

Copy the backup file to the ePO 5 server and restore the DB

Start the 4.5 services

Use the config page to configure the ePO 4.5 server to use the DB on the ePO 5 server

Restart the ePO 4.5 services to apply the change

Make sure that ePO 4.5 is functioning correctly.

Assuming everything's OK, you can now use the migration tool to migrate ePO itself to the ePO 5 server.

Sorry if this is a basic question, but if I have to backup the database from my old 4.5 ePO server and import it on the new 5.0.1 server will that server have to have the same name for the database to import without issues or can the server have a new unique name ?

Note: before looking the steps, if you are using the EEPC product, please don't go for upgrade process, since the EPO 5.x not supported any version of EEPC for now.

Before moving the db to new server 2008 R2 64bit machine, please make sure, what is the sql version you are going to install on new server.

Let me explain briefly with step by step as below.

1) I need complete answers for the questions as below.

>> EPO 4.5.7 and what is the SQL version and SP and the SQL is full or express edition ?

>. What is the EPO db size ?

>> What are point products managed with existing EPO server ( Ex: VSE, Agent and so on ) ?

>> How many machines are managed with existing EPO server ?

>> What is the Agent version and patch and VSE version and patch and if any other products please share the versions details.

2) Based on the above information I can guide you the right way and easiest path to move EPO 5.0.1.

3) The minimum environmnet supported with EPO 5.x as below.

Windows 2008 R2 64bit OS.

SQL 2008 R2 or later. Full /Express.

Minimum ePolicy Orchestrator upgrade versions

Only these existing ePolicy Orchestrator versions can upgrade to ePolicy Orchestrator 5.0:

• ePolicy Orchestrator 4.5 Patch 6 or later

• ePolicy Orchestrator 4.6 Patch 4 or later

4) Based on the minimum environment supproted, as you are with EPO 4.5.7 and planning to move to epo 5.x on new server wih windows 2008 R2.

But, I'm not sure the sql version for existing EPO server.

>> Install the sql 2008 R2 express/full version on new server for EPo 5.x, and from existing EPO, you can open the sql management studio and do the EPO DB dettach and then copy the mdf and ldf file to new server and click on attach and browse the files path.

>> This will move the DB to new server, but here we have update epo configuration file to point the new server IP and ports using for communication and the credentails to access DB to contact db on remote server.

>> This task is bit tricky, as you may face atleast some errors or may miss some options, so I suggest to follow the attached document with screenshots for step by step procedure.

>> The document will help to follow the complete steps to move the DB to remote or local server, as steps are same as per document.

>> Once the db is accessible and epo is contacting to remote server for db connection, then I suggest to check the number of files in "ePOlicy Orchestrator" folder.

Note: If you right click on "ePolicy orchestrator" Folder and if the files are more than 65000, then you have to delete files and make sure the number is not exceed before running the migration tool.