cancel
Showing results for 
Search instead for 
Did you mean: 
MPK
Level 8
Report Inappropriate Content
Message 1 of 7

Migrating endpoints to MVISION ePO

Hello All,

We just upgraded to MVISION licensing recently and I'm trying to migrate my endpoints from our internal ePO without much joy. As it is a new product there doesn't seem to be much info online about it and the documentation is very basic.

We have ePO 5.9.1 and I have run the Migration tool and successfully cloned the configuration to MVISION. I then selected a group in our system tree with 12 PCs as a test and it now just sits there with a spinning icon whenever I go and look at the status. The scren says they will get migrated during the next agent-server communication but that is not happening. The device names and TAGs show up in MVISION but the records do not contain any data and its obvious they are not talking to each other. If I look at an endpoint and select about it still points to the internal ePO even 24hr later.

I should note that I have generated an installation URL and if I run it on a wiped endpoint and it receives the agent from MVISION and within an hour the endpoint protection is auto deployed so that all works. But I have over 400 endpoints to migrate and I can't rely on users to click on a link to do it.(because they won't!) 

This is what I have tried - 

-wake up agents on devices including ticking force complete policy and task update. (note the devices do have an MVISION Migration tag applied to them by ePO)

- I noticed the one I setup using a link has DXL setup. I thought it might be a pre-requisite (the spare doco does not say anything about this) so I have checked in all the DXL components into our ePO and set it up.

- We use agent 5.5.1 so I also checked in agent 5.6.0 and deployed it to the test devices and confirmed that it also installed DXL client on them and it works.

I'm a bit stumped what to do because unless our endpoints have their config changed to point to MVISION (by our ePO I presume) they will never talk to each other. Its not like MVISION can initiate the communication from outside our network. So somehow the endpoint's ePO server DNS and IP details need to be changed but currently that is not happening.

Anyone succesfully migrated? What am I doing wrong?

 

 

 

 

 

 

6 Replies
jogvan
Level 10
Report Inappropriate Content
Message 2 of 7

Re: Migrating endpoints to MVISION ePO

Hi,

I have just migrated 3.600 clients at at customer site. It was from ePO 5.3.2 to MVISION ePO.

I did like this:

1. Downloaded the McAfee Smart Installer .exe
2. Used EEDK and created a ePO package with the switch "McAfeeSmartInstall.exe -s"
3. Checked the packed in to ePO onpremise
4. Created a Client Task to deploy the Smart Installer package.
5. Then I used Tag to deploy the Smart Installer package.

When installing McAfee Smart Installer, a HTTP connection is done to MVISON ePO and machine is created in System Tree. Then the FramePkg.exe is donwlonade and extracted to %appdata%/local/McAfeeSmartInstall/ . Then installed. For some reason approximatly 15 % of the machines failed to install the McAfee Agent.

regards
jogvan
MPK
Level 8
Report Inappropriate Content
Message 3 of 7

Re: Migrating endpoints to MVISION ePO

Thanks heaps that is a good workaround.

I am curious as to why the migration tool isn't working though so will log a support request first and see how that goes.

 

 

McAfee Employee cdinet
McAfee Employee
Report Inappropriate Content
Message 4 of 7

Re: Migrating endpoints to MVISION ePO

The eedk suggestion is a great workaround, but if you want to know why the migration isn't working, please open a ticket with McAfee.  We would need to look at logs on the epo server and client to determine why it is failing.

Was my reply helpful?
If this information was helpful in any way or answered your question, will you please select Accept as Solution in my reply and together we can help other members?

Highlighted
MPK
Level 8
Report Inappropriate Content
Message 5 of 7

Re: Migrating endpoints to MVISION ePO

Thanks cdinet. I will open a ticket as I am curious as to why the migration tool isn't working.
MPK
Level 8
Report Inappropriate Content
Message 6 of 7

Re: Migrating endpoints to MVISION ePO

Just an update. I have logged a ticket with McAfee support 2 weeks ago but it is still ongoing at this time while the support analyst contacts me once a day to collect the next piece of info the engineers have asked for.

I will update this once we have found the solution in the hope that this thread may then be help to someone else.

IMHO marking a previous post saying to log a ticket as "the solution" is not very helpful to anyone who comes across this thread later.   

McAfee Employee cdinet
McAfee Employee
Report Inappropriate Content
Message 7 of 7

Re: Migrating endpoints to MVISION ePO

I understand that is not helpful, but the reason we log it as solution is because it is something that cannot be fixed on this forum since it involves more detailed analysis.  Posting the fix once support provides a solution will help and you can also mark that as a solution.

Was my reply helpful?
If this information was helpful in any way or answered your question, will you please select Accept as Solution in my reply and together we can help other members?

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