I'd recommend following these instructions from McAfee site:
Although this doesn't fully cover using a different servername.
You mention you can't use the old name for the server. Is this because it is to be used elsewhere on your network ? If not, and you have local DNS, consider creating an A record pointing the name at the appropriate IP address.
Also, you don't mention how many clients/epo agents you have on your network.
Hi Matt, thanks for your answer.
Yes, I already saw this KB, but it implies repushing all the agents which I would like to avoid, if possible.
The DNS name cannot be re-used for inventory reasons, but it will not be used on the network, so I can make both the old DNS name and the new DNS name point to the same IP address.
We have ~1000 agents, on we only use the ePO / McAfee Agent / VirusScan products. We don't use RSD or other products.
1 of 1 people found this helpful
the article only mentions redeploying the agent to the epo server itself
"Deploy the ePO agent only to the ePO server.
This replaces the new agent keys on the ePO server with the restored ones from the previous installation. All other existing agents on the network will retain the proper keys and will not need to re-deployed."
If you can setup DNS to point the old name at the new server, then even though you are re-using the IP address, it should mean the existing agents can talk to the new server so you don't need to re-deploy the agent to everything.
Ok, that's what I secretly hoped
And for the other aspects (files to modify after copying the "ePolicy Orchestrator" folder, reg keys, patches, extensions...) do you have any idea ?
Will the ePO instance on Server02 automatically have the patch 6, as well as all extensions that the previous server had?
Or are there some registry keys that I need to backup/restore first ?
Are there files located in "Program Files\McAfee\ePolicy Orchestrator" that I should edit to specify the new server name ("Server02") instead of the previous one ?
Any Update? Did this work successfully for you?
Hi, I haven't tried yet since I need to be really sure that I can simply copy-paste the whole "Program Files\ePolicy Orchestrator" folder from one machine to the other, or if I will then need to edit some files...
I tried and it worked.
All I needed to do was to first generate/add a new serverkey (that reflects the new ePO server's DNS name), then overwrite the whole "Program Files\ePolicy Orchestrator" folder from the old to the new machine, then edit the db.properties and server.ini files (to also reflect the ePO/SQL server DNS name).