Please go through below McAfee KB article for upgrade:
Before Upgrade :
During upgrade :
Do I have to upgrade SQL Server first? Or is that part of the ePO upgrade?
Will there be a problem with the Agent Handlers?
Please go through my previous community post with complete info and pre-cautions before upgrade/migrate.
If you still have any questions, please reply to this post, by answering all the questions as below and make sure, you are ready to use the same host name and IP address on new server ?
1) What is the EPO version with Patch and agent version and patch?
2) What is the sql version and service pack?
3) Is the database full or express version, is the DB on the same machine or on a remote machine?
4) How many machines are managed with EPO ?
5) What are the point products managed with EPO (Ex:VSE, Agent, DLP, EEPC and more) ?
6) What is the operating system and service pack in use, and is it 32 or 64 bit OS?
This helps me to answer the best way to move forward with less impact....
NOTE: As per your last query, for the remote agent handlers, before upgrade, from the EPO console you need to disable the RAH through console and then upgrade epo, and then you need to copy the agent handler folder from the epo 5.x package and then reinstall on remote agent handler machines.
If SQL is running with 2005 than yes, you have to upgrade it to 2008 version.
Absolutely correct, since EPO 5.x supports minimum sql 2008 sp2 or later.
If you want to use sql express version, I suggest to download the sql 2008 R2 sp2 express and perform new install and more details as below.
To download the SQL 2008 R2 SP2 package, the link as below.
The file name is " SQLEXPRWT_x64_ENU.exe" ( 64bit file) and size is 340.5MB...
This file contains the sql 2008 R2 sp2 with management studio.
For more information about supported environment, please go through the KB51569
I'm wondering why anyone would install SQL Server 2008 R2 linked above on a new or upgrade installation of ePO 5.0 or 5.1?
Wouldn't installing 2008 on 5.x be similar to installing SQL 2005 on ePO 4.6 and make it more likely that the database will need to be upgraded again at the next ePO upgrade?
Since they must upgrade anyway, why would they not jump straight to SQL 2012 Express if they have 4.6.6 or newer so that it will have a longer support life and more likely be able to migrate to the next future ePO version without quickly requiring another database upgrade?
Since, the EPO 5.x won't supports the sql 2005, so by the time of upgrade without minimum sql 2008, it can't understand the DB. Hence we need to be with supported versions of sql, EPO before upgrade.
Please go through the KB51569 for more details.
I know the SQL 2005 database needs to be upgraded before ePO can be upgraded, but the question is why not just upgrade from SQL 2005 to 2012 instead of SQL 2005 to 2008 since 2012 is supported on both 4.6 and 5.1? Skipping version 2008 will likely allow a few more years before the database needs to upgraded again.