cancel
Showing results for 
Search instead for 
Did you mean: 

upgrade 4.6 to 5.3

I have EPO 4.6 on windows 2003 x86, with sql on the same server, virtual

I want to create a new 5.3 EPO with the same name without affecting the old one

I used the compatibility migration tool to migrate the settings to the new server, 2012 r2 with sql 2012 R2,

Then took the new server offline renamed to the same name

Installed sql 2012

restored the old DB into the new SQL

and ran the migrate to target and

then did the EPO software install,

problem how do I get it update the old db recently restored? , if I point the install at the old db it says sorry need a version 5.3 db not 4.6

I'd like to check the new EPO in a bubble before I turn off the old and join the new to the domain with the OLD name.

thanks

15 Replies
mmcgary
Level 12
Report Inappropriate Content
Message 2 of 16

Re: upgrade 4.6 to 5.3

Do you have a supported 2008+ sql version on your old 4.6 server so that the db is already upgraded? I've never done it the way you're doing it but I imagine the edits in the sql migration KB should work fine: McAfee KnowledgeBase - Recommended procedure for migrating or moving an ePO database to a new SQL se...

Re: upgrade 4.6 to 5.3

I know how to move the database .. the question is how do I get the upgrade process to upgrade the schema to 5.3 of a different DB

I want leave the old server alone

Why did mcafee create an entire migration tool and then leave the DB migration completely blind?

mmcgary
Level 12
Report Inappropriate Content
Message 4 of 16

Re: upgrade 4.6 to 5.3

The reason we didn't include the db migration in the tool is because the database is hosted on a Microsoft product and migrating a database is a Microsoft-supported function. If something went wrong during the database migration process we would be expected to support that which we can't do.

The new server that has the migrated EPO directories, reg keys and service still points to the 4.6 database that is listed in the db.properties file and registry location so it doesn't matter where it is as long as it is reachable according to the information. If the upgrade doesn't see it then you will get errors similar to what you are getting.

Re: upgrade 4.6 to 5.3

I wasn't requesting that the tool moved the database

Merely that it prompted for which database to upgrade, instead of assuming that people want to upgrade their old db in situ .. hence burn their old server and restore the db should there be issues

I have restored the 4.6 db to the new server I just want to upgrade that one.. all offline

mmcgary
Level 12
Report Inappropriate Content
Message 6 of 16

Re: upgrade 4.6 to 5.3

A specific EPO file system is tied to its specific EPO database. I'm not sure what you mean by "...it prompted for which database to upgrade, instead of assuming that people want to upgrade their old db". You have to upgrade the database that's associated with the file system on the server that you're running the upgrade from. If you want to migrate the database before you upgrade you need to make absolutely sure the database is reachable at the locations specified in the db.properties and registry. The steps for migrating a database are the same regardless of how many copies you have of the same database in different locations.

Re: upgrade 4.6 to 5.3

I know what DB I want to upgrade, The tool should have somewhere where you say which db to upgrade, is that hard to understand ?

Is there a way I can leave my old 4.6 EPO server running and on a new offline server run through the upgrade ? Please list the steps

mmcgary
Level 12
Report Inappropriate Content
Message 8 of 16

Re: upgrade 4.6 to 5.3

The tool doesn't touch your database so why would it ask you which database to upgrade?? The tool copies your EPO file system, disables the old EPO services, extracts the file system to a different server, adds a few registry keys and a Tomcat service. That's it. Other than the services being stopped and disabled on your old server you will still have a fully functional 4.6 server and database. As I said before the upgrade itself uses the db.properties file and registry location to determine the location of the database. As long as you modify the locations from the db migration KB you never have to touch your old production database.

Re: upgrade 4.6 to 5.3

From the 5.3 install guide :

To reuse an existing 32-bit McAfee ePO database:

1 Use the Upgrade Compatibility Utility to convert an existing 32-bit McAfee ePO server configuration

to the new 64-bit server configuration and start a McAfee ePO custom installation. See 32-bit

Upgrade Compatibility Utility overview for details.

2 During the upgrade, the existing 32-bit McAfee ePO SQL database is configured by default.

Can you explain step by step how to create a new 64 bit EPO server, without affecting the old one

I have a 32 bit windows server with a 32 bit SQL db

I have a new 64 bit 2012R2 server with SQL 2012 it is to be the same name as the old server when confirmed all is ok while offline

mmcgary
Level 12
Report Inappropriate Content
Message 10 of 16

Re: upgrade 4.6 to 5.3

1 Use the Upgrade Compatibility Utility to convert an existing 32-bit McAfee ePO server configuration

to the new 64-bit server configuration and start a McAfee ePO custom installation. See 32-bit

Upgrade Compatibility Utility overview for details.

Server, not database

2 During the upgrade, the existing 32-bit McAfee ePO SQL database is configured by default.

During the "Upgrade", not "Upgrade Compatibility Utility"

Again the "Upgrade Compatibility Utility" and the "Upgrade" are 2 totally different processes. The tool does not modify the database in any way so you could run the tool on the source machine, run it on the target machine, enable the old EPO services that were disabled and continue using EPO 4.6 on the old server without issue and forget about your new migrated server forever. The upgrade upgrades the database and file system and will render your EPO 4.6 unusable if you go through with the upgrade AFTER migrating. As long as you modify the db.properties and registry per the DB Migration KB AFTER the migration but BEFORE the upgrade, the upgrade will upgrade the database you have specified. The steps from the DB Migration KB are the steps you would use when migrating a database for whatever reason. If you migrate EPO with the utility to your new server, migrate the database to the new server per the sql migration kb and then run the upgrade you no longer have any ties to your old EPO server or database.

Want to Ask a Question?

Community Help Hub

    New to the forums or need help finding your way around the forums? There's a whole hub of community resources to help you.

  • Find Forum FAQs
  • Learn How to Earn Badges
  • Ask for Help
Go to Community Help

Join the Community

    Thousands of customers use the McAfee Community for peer-to-peer and expert product support. Enjoy these benefits with a free membership:

  • Get helpful solutions from McAfee experts.
  • Stay connected to product conversations that matter to you.
  • Participate in product groups led by McAfee employees.
Join the Community
Join the Community