Reinstall of ePO

[Former Member]

All,

Looking for some advice on the steps needed to complete a reinstall of ePO whilst maintaining all of the existing configuration and policies.

Am running ePO Version 4.0.0

The reason for the reinstall is we have just identified a conflict with running ePO and WSUS on the same server. Both require port 80. (Even though WSUS can use a configurable port for distributing patches (i.e. not port 80) it still requires port 80 for the 'self update tree'.

The idea therefore is to reinstall epO using a different port for agent-to-server communication.

My tasks therefore is to produce a plan detailing how this can be achieved and in what order. On first glance it looks like the following will have to be done prior to the reinstall.

1. Back up the SQL 2005 Express DB
2. Export all policies for each product
3. Export the Repository List (SITEMGR.XML)
4. Backup security keys (Can I use the agent -server key even though I will be changing the port - I assume so)
5. Anything else???????

What order would I then have to restore the above data?

Thanks
Gerry

[Former Member]

Why reinstall if you can "simply" change the port: https://knowledge.mcafee.com/SupportSite/search.do?cmd=displayKC&docType=kc&externalId=614037&sliceI...

[Former Member]

Hi Metalhead,

I only found out about this issue today and was hoping there would be a reg fix. I have to thank you once again for pointing me in the right direction and saving me lots of research time.

Many thanks.

I will post the outcome of the change when I have implemented and tested it.

Regards
Gerry

[Former Member]

Just a small note to your procedure above - exporting the policies and reimporting them will loose all policy assignments.

[Former Member]

Metalhead,

Are you advising that I still follow the steps I outlined in my first post just in case there are issues with changing the port in the McAfee procedure you supplied or was your last post purely for information. I suppose its best practise to complete the backups prior to making a change of this nature.

I am just glad that we have identified this before our client roll out as the note at the bottom could have meant even more work.

NOTE: If agents were deployed to client systems previously, the CMA / ePO agent must be reinstalled on all client computers using a /forceinstall to overwrite the existing Sitelist.xml file.

Thanks
Gerry

[Former Member]

It was just a general note happy So I would follow the McAfee suggestion.

[Former Member]

Well metalhead,

Not sure if you're looking in today but I followed the McAfee document and it appears to have worked. The new port for agent-to-server communication is now showing in th ePO console

The only issue now seems to be with the sitelist.xml file. Their are a number of Sitelist.xml files on the ePO server in the following locations

C:\Program Files\McAfee\ePolicy Orchestrator\DB
C:\Program Files\McAfee\ePolicy Orchestrator\DB\Software\Current\EPOAGENT3000\Install\0409
C:\WINDOWS\Temp\unz34D.tmp
C:\WINDOWS\Temp\unz34F.tmp
C:\

Some of these contain the new port setting and some the old port setting. Which sitelist does the client download during the agent installation?

Also can I manually change the ones with the old port setting?

Thanks

[Former Member]

I would change all ports manually to get sure.
AFAIK the client gets the SITELIST from the DB folder.

[Former Member]

:confused:

Have edited all the sitelist files on the ePO master server and the sitelist.xml files on the distributed repository and still the client downloads sitelist.xml, serverlist.xml and sitemaplist.xml all with the old port settings?

[Former Member]

Fixed! 😉

1.Renamed the EPOAGENT3000META folder in directory below to EPOAGENT3000META.old

C:\Program Files\McAfee\ePolicy Orchestrator\DB\Software\Current\

2. Checked in the Agent package again - This created a new EPOAGENT3000META folder.
3. Created a new Framepkg.exe