cancel
Showing results for 
Search instead for 
Did you mean: 
jmhj
Level 7
Report Inappropriate Content
Message 11 of 64

Re: Migrating ePO 4.6.6 to 5.0.0 using upgradecompatibility tool.

How long did you have to wait for it to complete?  I just want to make sure I am not being impatient.

Highlighted
Reliable Contributor twenden
Reliable Contributor
Report Inappropriate Content
Message 12 of 64

Re: Migrating ePO 4.6.6 to 5.0.0 using upgradecompatibility tool.

When you say "how long it did it take to complete".

What step are you at?

1. Creating the migrate.zip (on existing 4.6.6 server) took about 15 minutes - it created a 1.6GB zip file which we had to copy to the new Windows 2008R2 server.

2. The 2nd part of importing the migrate.zip took also about 15 minutes.

3. The last part, when you run the ePO 5.0 setup took a lot longer around 30 minutes.

Some of these steps take longer when you have a large database, I believe it warns you about that. In our case our database is small at only about 184MB.

I know the feeling about being impatient as some of the steps don't give yhou much feedback. What you can do is to bring up task manager and look at the cpu usuage to see that the setup etc is still running.

Message was edited by: twenden on 5/23/13 1:36:01 PM CDT
jmhj
Level 7
Report Inappropriate Content
Message 13 of 64

Re: Migrating ePO 4.6.6 to 5.0.0 using upgradecompatibility tool.

Thanks for the reply.  I tried what was in 78121.  The server.xml file was missing the attribute but adding it made no difference.  I called McAfee and they told me that they are aware of the problem and that it is not going to work.  They told me to follow 71078.  What a pain.  For me the source and target are named differently. 

Why not pull the product if they know it is not working?  Would have saved me some time with this.  Watching the thread for awhile just in case someone comes up with a solution.  Fingers crossed.

Re: Migrating ePO 4.6.6 to 5.0.0 using upgradecompatibility tool.

msilveira2,

did you get past the Compressing: 0% problem?

Mario

alexn
Level 14
Report Inappropriate Content
Message 15 of 64

Re: Migrating ePO 4.6.6 to 5.0.0 using upgradecompatibility tool.

Hi all,

After going through whole thread I 'd like to suggest you an easy way of migration which I think will save your time and pain as compared to kb 71078.

I will post if anyone is interested.

Alexn.

jmhj
Level 7
Report Inappropriate Content
Message 16 of 64

Re: Migrating ePO 4.6.6 to 5.0.0 using upgradecompatibility tool.

I am interested.  Thank you.

alexn
Level 14
Report Inappropriate Content
Message 17 of 64

Re: Migrating ePO 4.6.6 to 5.0.0 using upgradecompatibility tool.

Okay JM,

Few Ques and tricks as well.

Is it windows server 2003 32  bit?

Is it ePO server 4.6.x?

how many clents are being managed?

Do you have any type of Distributed Repository?

Any Agnet Handler?

Current SQL DB version?

Do you have MS SQL server Managemnet studio installed?

jmhj
Level 7
Report Inappropriate Content
Message 18 of 64

Re: Migrating ePO 4.6.6 to 5.0.0 using upgradecompatibility tool.

Is it windows server 2003 32  bit?   Win2k3 R2 SP2

Is it ePO server 4.6.x?     4.6.6 Build: 176

how many clents are being managed?     Approx 230

Do you have any type of Distributed Repository?    No

Any Agnet Handler?     No

Current SQL DB version?     MS SQL 2005 Express SP2

Do you have MS SQL server Managemnet studio installed?     Yes

alexn
Level 14
Report Inappropriate Content
Message 19 of 64

Re: Migrating ePO 4.6.6 to 5.0.0 using upgradecompatibility tool.

Download latest RSD sensor 4.7.1.120. Install all extensions and Package.(Best is to run Compatibility tool and see the products which are not compatible, remove them or download their latest packages and install into your epo.Once tool shows all clear then just close this tool.

Log in to your EPO and export products policies under policy catalog.

Export Agent to server Master key showing client number=230.

Close epo console.

Log in  to sql managemnt studio.Detach your Database.

Install ePO 5.0 on new machine with identical name or IP.one thing atleast should be identical.

Access SQL 2008 with SQL Managemnt 20o8.Attach Databsae under MSSQLSERVER.

Import all policies.

Back existing Master key and then remove it. Import the new Agent to server Master key.

Crerat a AD synch task. Wait for some tim to pop up all your machine.

This is really easy way.

jmhj
Level 7
Report Inappropriate Content
Message 20 of 64

Re: Migrating ePO 4.6.6 to 5.0.0 using upgradecompatibility tool.

Ok.  Thanks.  I am going to try this method today.  I can't use the same server name but I can use the same IP.   Any caveats to just using the same IP?  How would the siteList.xml and ServerSiteList.xml files get updated or does it matter?  Can I just make the neccessary changes to the files and then push them out using GP to the clients or will ePO take care of it?

thanks alexn for your help.

More McAfee Tools to Help You

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