Migrating ePO 4.6.6 to 5.0.0 using upgradecompatibility tool.

[Former Member]

Although Agent to server communications keys will  do the job. Let you know how communication 'd take place.Client machines tries to connect to ePO by its Name 2nd Netbios  3r ip and updates its sitelist.xml file.secure communication took over 443 and non secure over 8080 with spipe protocole.once the communicatons started both epo and clients updatedc their sitelists.No caveats to using the same ip and no need to deploy files with GP.epo will do it.

[Former Member]

Thank you very much.  Will give it a go and let you know the result.

[Former Member]

Well.  I was able to attach the DB but the services will not start.  Did you rename the files or tell SQL to attach it as a different name?

[Former Member]

Hello All,

I am new to ePo as our last ePo "expert" was promoted and bestowed this "gift" on me. We are currently on version 4.6.6 and I am in the process of upgrading all of our users to VirusScan 8.8 from 8.7 as I learned that 8.7 is not compatiable in ePo 5.0. Once all users are upgraded to 8.8, I will begin the upgrade to ePo 5.0 and am starting to research this process as we will be doing this within the next 2 weeks. I found this thread and am VERY interested in an easy way to complete this migration. Any help at all would be greatly appreciated.

Is it windows server 2003 32 bit? Windows Server 2008 R2 64bit

Is it ePO server 4.6.x? ePo server 4.6.6

how many clients are being managed? 950

Do you have any type of Distributed Repository? Yes

Any Agnet Handler? Yes - One

Current SQL DB version? SQL Server 2008 R2(x64)

Please let me know if any additional info is required... and thanks again!

[Former Member]

Jmjh,

We need Hostname or ip (your server ip or name

Database server instance like EPOSERVER

Database name like ePO4_WIN-2008R2

Database server port  

Do you have or should I tell you from where to get?

[Former Member]

The old server name is utl01

The new server name is utl02

The old instance name is EPOSERVER

The old DB name is ePO4_UTL01

I cannot use the old name as the old server has other roles in the environment.  I have changed the new servers IP to that of the old server and gave the old server a new IP.

[Former Member]

After attaching DB to youe SQL 2008 sP1 to the default instance named MSSQLSERVER    

was you able to connect SQL with SQL Dtudio Management utility successfully?

Q.After installing SQL 2008S! and attaching DB you run ePO 5.0 setup and it finished successfully?

[Former Member]

I installed ePO first and then attached the DB.  That was in your original instructions.  Should I start the process again and install SQL first the attach and then install ePO or can I just rerun the ePO installed and it will setup everything correctly?

Message was edited by: jmhj on 6/5/13 4:14:36 PM CDT

[Former Member]

Check db.properties and make changes as server name + instance name= etc.then try only starting application service.Im inhurry now and will fix it tomorrow.no worries we can fix it.

[Former Member]

Location for DB is C:\Program Files (x86)\McAfee\ePolicy Orchestrator\Server\conf\orion