I have been tasked with migrating my company’s ePO server (Virtual Server, windows 2003 x86 SP2, ePO version 4.5.7) to a new Virtual server running Windows 2008 R2 x64 running ePO 5.0.1.
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 126.96.36.199 (VSEMAS870000) - no known compatible version
GroupShield for Lotus Domino 7.0.1105.104 (GSD7REPORTS) - no known compatible version
Host IPS 188.8.131.52 (HOSTIPS_META) - no known compatible version
Host IPS 184.108.40.2068 (HOSTIPS_8000) - requires Host IPS 220.127.116.111
Host IPS 18.104.22.1688 (HostIpsAdv) - requires Host IPS 22.214.171.1241
Host IPS 126.96.36.1998 (HostIPSLicense) - requires Host IPS 188.8.131.521
McAfee VirusScan Enterprise for Linux Reports 1.0.115 (LYNXSHLDPARSER) - requires McAfee VirusScan Enterprise for Linux Reports 184.108.40.2061
Policy Auditor 220.127.116.11 (BenchmarkEditor) - no known compatible version
Policy Auditor 18.104.22.168 (Findings) - no known compatible version
Policy Auditor 22.214.171.124 (PACore) - no known compatible version
Policy Auditor 126.96.36.199 (PARollup) - no known compatible version
Policy Auditor 188.8.131.52 (PolicyAuditor) - no known compatible version
Policy Auditor Engine 184.108.40.206 (AUENGINEMETA) - no known compatible version
Rogue System Detection 220.127.116.11 (rsd) - requires Rogue System Detection 18.104.22.168
Security for Mac (Anti-Malware) 22.214.171.124.189 (VSCANMAC8610) - no known compatible version
SiteAdvisor Enterprise 126.96.36.199 (SITEADV_1500) - no known compatible version
SiteAdvisor Enterprise 188.8.131.52 (SAE_META) - no known compatible version
Spam Killer for Lotus Domino 7.0.1105.104 (SMDWIN__7000) - no known compatible version
Spam Killer for Microsoft Exchange 2.1.1350.108 (SKE2REPORTS) - no known compatible version
Spam Killer for Microsoft Exchange 2.1.1350.108 (SPAMKILR2100) - no known compatible version
Virex (EOL) 1.0.138 (VIREXREPORTS) - no known compatible version
VirusScan Enterprise 184.108.40.206 (VIRUSCANREPORTS) - requires VirusScan Enterprise 220.127.116.11
VirusScan Enterprise 18.104.22.168 (VIRUSCAN8700) - no known compatible version
VirusScan Enterprise 22.214.171.124 (VIRUSCAN8800) - requires VirusScan Enterprise 126.96.36.1998
VirusScan Enterprise for Linux 188.8.131.52 (LYNXSHLD1500) - no known compatible version
VirusScan Enterprise for Linux 184.108.40.206.153 (LYNXSHLD1510) - no known compatible version
VirusScan for Mac (EOL) 220.127.116.11 (VIREXUB_8500) - no known compatible version
ePO may be upgraded with the below products installed, but their management extension will be disabled and should be upgraded when ePO starts after setup:
SiteAdvisor Enterprise 18.104.22.168 (SITEADVMETA) - requires SiteAdvisor Enterprise 22.214.171.124
SiteAdvisor Enterprise Web Filtering for Endpoint 126.96.36.199 (SITEADVCFMETA) - requires SiteAdvisor Enterprise Web Filtering for Endpoint 188.8.131.52
… my question is what are the next steps to start the migration process ? If I upgrade certain packages will there be an impact on the business ???
I apologise if these are basic questions but I really do not know were to start.
Thank you all in advance for taking the time to read this post and I appreciate your advice.
Hi smoggy333, the first thing you need to do is checking which products you're using at your company beaucse on older ePO versions a lot of extensions were added by default.
Once you know which ones you're using then you can remove unused extensions, then you'll have to test new prodcut versions on some computers prior to upgrade all of them.
I know it can be a long road but I think it will be the best way (at least more secure) to prepare the migration.
Thank you so much for taking the time to provide feedback.
I have since removed all extensions that we no longer require or can not be upgraded and already the compatibility checker is looking a lot better.
Does the migration tool migrate the database ? or does this have to be backed up in SQL and imported to the new server ???
Thank you in advance for taking the time to review this topic and provide valuable advice.
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..
Not had a look at ePO 5 yet, so can't help on that side of things.
Thank you for the advice Jane,
I was hoping the migration tool would do most of that work for me ?
Problem is I am very new to ePO and am trying to get this upgrade done the easiest way possible.
I will look into maybe going to 4.6 before v5.0.1.
The main issue is that your current server is x86 and epo 5 is x64.
there is this document- but i read quite a few posts that it didn't work in, so i discounted it.
How to migrate ePO 4.5 or ePO 4.6 from a 32-bit system to a 64-bit system (or to a different installation path)
You could always backup your virtual server, try it then if it doesn't work, bring the working one back online.
Don't know what the migration tool is as i have not looked at it yet.
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.
Thank you everyone for the replies.
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 ?
Thank you for your assistance.
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.
For more information check the KB78519 and direct link as below.
Then ran the upgrade compatibility tool and then extract the "Migrate.zip" on new server.
>> The upgrade compatibility tool just does the same as per KB71078, and for some reason if you failed to perform this task, I suggest to follow the KB71078 and direct link below.
>> By following this Kb, you have install the same version of EPo on new server and follow the article.
>> This helps to move the existing EPo to move from 32 to 64 bit OS.
>> If you follow the article, with each and every option as suggested, you won't get any errors and we tried internally couple of times and it is successful as per the article.
NOTE: Attached the pdf with some scenarios for the upgrade /migrate epo from 4.x to 5.x, please check the pdf for more information and complete details.
Raghavendra GCMessage was edited by: rgc on 9/11/13 12:53:21 AM CDT