cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
twenden
Reliable Contributor
Reliable Contributor
Report Inappropriate Content
Message 1 of 2

McAfee ePO On premise migration to Mvision ePO questions

Jump to solution

Got several questions about possible migration of our McAfee ePO On-Premise server to MVision ePO.

 

1. The doc seems to mentions that the migration will fail if you have even one inactive agent. I am assuming this means an agent that has not talked back to ePO in awhile. Is this correct as in our environment we could get systems that don't get turned on for say 6 months.

2. Our system tree structure, setup years ago, is configured by IP address group. For example we might have a building listed as a group and configured with the IP range for that building. This way system in that building move to that group. Does this scenario migrate to MVision ePO or does your system tree need to be setup via AD?

3. Currently we have SQL server running on the ePO server. What doe you do with the SQL server as I guess it doesn't migrate. I guess it still has to run on-premise is that correct?

 

4. Are there any good reasons that I could give to management that supports the advantages of using MVision ePO instead of On-Premise. 

 

5. Is the migration a one time deal. What do you do with systems that say communicate to the on-premise server months after you have migrated to MVision ePO?

 

Thanks

1 Solution

Accepted Solutions
rgc
McAfee Employee
McAfee Employee
Report Inappropriate Content
Message 2 of 2

Re: McAfee ePO On premise migration to Mvision ePO questions

Jump to solution

By default inactive means if it is not reporting more than 30 days, and if you say for few months it wont contact to ePO, then those can't be migrated to MV-ePO, so for those systems you can go to MV-ePO and copy the smart installer URL and you can run the URL once you get that system access, so MA will be reinstalled and it will report to your tenant in MV-EPO.

If you want to install with force then mcafeesmartinstaller.exe /f will help to force install MA to remove existing MA reporting to on-prem

The migration sequence is been documented here

https://docs.mcafee.com/bundle/mvision-epolicy-orchestrator-product-guide/page/GUID-DAAA333B-E035-4B...



Are there any good reasons that I could give to management that supports the advantages of using MVision ePO instead of On-Premise. 


Answer: Hassle free maintenance, since you have the tenant, which you login via URL to access mvision ePO and clients installed with MA and point product like: ENS will be reporting to this MV-ePO tenant and you have nothing to worry about new package, new build of ePO is released, since its taken care.

Moreover, the master repository, you will have always updated build.... and no fallback or older build leading to problem state.


Was my reply helpful?
If you find this post useful, Please give it a Kudos! Also, Please don't forget to select "Accept as a solution" if this reply resolves your query!


Raghavendra GC - [RGC]

View solution in original post

1 Reply
rgc
McAfee Employee
McAfee Employee
Report Inappropriate Content
Message 2 of 2

Re: McAfee ePO On premise migration to Mvision ePO questions

Jump to solution

By default inactive means if it is not reporting more than 30 days, and if you say for few months it wont contact to ePO, then those can't be migrated to MV-ePO, so for those systems you can go to MV-ePO and copy the smart installer URL and you can run the URL once you get that system access, so MA will be reinstalled and it will report to your tenant in MV-EPO.

If you want to install with force then mcafeesmartinstaller.exe /f will help to force install MA to remove existing MA reporting to on-prem

The migration sequence is been documented here

https://docs.mcafee.com/bundle/mvision-epolicy-orchestrator-product-guide/page/GUID-DAAA333B-E035-4B...



Are there any good reasons that I could give to management that supports the advantages of using MVision ePO instead of On-Premise. 


Answer: Hassle free maintenance, since you have the tenant, which you login via URL to access mvision ePO and clients installed with MA and point product like: ENS will be reporting to this MV-ePO tenant and you have nothing to worry about new package, new build of ePO is released, since its taken care.

Moreover, the master repository, you will have always updated build.... and no fallback or older build leading to problem state.


Was my reply helpful?
If you find this post useful, Please give it a Kudos! Also, Please don't forget to select "Accept as a solution" if this reply resolves your query!


Raghavendra GC - [RGC]

View solution in original post

You Deserve an Award
Don't forget, when your helpful posts earn a kudos or get accepted as a solution you can unlock perks and badges. Those aren't the only badges, either. How many can you collect? Click here to learn more.

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