Lost policies with PrP15->ePO4 upgrade

[brentil]

I recently did a test upgrade from PrP 1.5 P1 to ePO4, I followed the directions in the upgrade articles which said I had to do PRP15P1->ePO361->ePO4. I hit several snags along the way but worked through them. At one point the ePO361 would fail to install with no really useful errors in the log, it ended up being WhatsUp running on the same server using one of the ports Tomcat wanted to use (WhatsUp uses TomCat for its internal web server too). So I had ePO361 up and running, I looked around a little to make sure it was running correctly then started the ePO4 upgrade. I then ran in to both the complex password and long file naming issues which I got both resolved and got ePO4 running.

When I went in to it to start using it I noticed all my policies from PRP15 were all gone. The couple of test machines connected to this test upgrade all were deployed the default policies once they finally hit back. Was there something I was supposed to do before upgrading to export my policies, did something go wrong along the way, or are policies just always lost from a PRP->ePO upgrade?

I unfortunately did not think to look at the policies when ePO361 was running so I do not know if they were lost going to ePO361 or to ePO4.

[brentil]

I've gone back and done some testing on some virtual machines and it seems the policies are lost going from ProPilot to ePolicy 3.6. When I load up ePolicy 3.6 after the migration it is missing the policy information for VirusScan Enterprise 8.5 so all the machines don't have a reference for their policies anymore. I had to take and reimport the VSE 8.5 NAP file to get ePolicy 3.6 to recognize machines had it installed. Of course all of the policies were wiped out.

[brentil]

Is there some way to export the policies from ProPilot to import them in to ePolicy, or some sort of conversion program? I've tried several upgrade paths and each time I loose my policies.

[brentil]

Figured it out! 😄

I had the NAP files installed for VSE 8.5 P1 but I had patch 4 installed. So I had to take and import the patch 4 version of the NAP. I also took and installed CMA360P3 and installed the newest NAP file for it as well. Unless the newest NAP file is installed for a patched version the policy WILL fail during the upgrade process.

[Former Member]

I'm having the same problem that you had. Can you explain in more detail the order & which program you did the NAP installations in?

Thanks,
Eric

[brentil]

The way I tackled this issue is I went into the Software area and wrote down everything that was there and it's version number. I then went and re-downloaded from the MySupport portal and Grants download area the install files and the patch files I had for them. I think imported the NAP files for the main installer files for each software package I have so I was at the baseline for each one. After that you have to go into each update package and get the NAP files from them for each patch installer.

The NAP version HAS to be the correct one for the software package you have installed. So if you have VSE 8.7 P2 you have to have the Patch 2 NAP installed. If you have any software package that it's NAP is out of date it will cause this issue to happen. I have two machines we upgraded from PP 1.5 to ePO 4.0 and with the first one we ran into this problem and I eventually got it resolved. Once I knew what to do though the 2nd machine went without any issues once I had updated all the NAPs to the exact version.

[Former Member]

Shouldn't PP already have all of the correct NAP versions? Or am I missing something as to where you are loading them?

How can you tell in PP, what Patch is installed?

Thanks,
Eric

[brentil]

In most cases unless you loaded the NAP file then you're missing them, which is where this issue arises from. You would assume it would have the correct NAP, but the way McAfee puts them in place you don't... When you're in the area where it shows the software packages you have checked in you should have something like VSE 8.5 Installer which means you have the bass installer. Then if you've checked in patches you should have another item listed like VSE 8.5 P8 Updater or Installer I forget what they're tagged as. If you have a patch installer like that in your PP then you have to have it's corresponding NAP file installed as well or you get the issue. The NAP files for patch installers are not automatically checked in so you have to do it manually. In the example above you would want to go download again the VSE 8.5 P8 files if you don't have them around still. Decompress the zip file, and inside of it will be the updated NAP file that corresponds to that patch installer. Take and check that into your PP and then do that for every other product and patch installer.

You will continue to have to do the same type of extracting of Extensions for ePO 4/4.5 as you do with NAP files in PP.