Did you have a complete backup including sql of the system prior to reinstall?
ePO has unique keys that are required for various tasks- including agent communication.
If you have not installed any new clients with the new system then i would blow that install away and follow a correct restore procedure listed here:
ePO 4.5 and 4.6 server backup and disaster recovery procedure
Thanks for the KB links - they have explained a lot!
I don't believe there was any backup (that's what the server was) but it was not (at the time) considered important and the client was wanting a fresh install.
ePO is installed and disaster recovery option were not able to be followed. I have been trying to do a test deploy agent with forceinstall, but it seems to fail. Can you explain (or link with KB) wether I should be doing this remotely via ePO or manually on the workstation? I've tried to do it on the workstation but get the message 'Another version of this product is already installed..."
What version of ePO and agent are you are running?
How were the agents deployed in the first place?
I'm guessing that none currently exist in the console?
If you take the framepkg.exe from C:\Program Files\McAfee\ePolicy Orchestrator\DB\Software\Current\EPOAGENT3000\Install\0409 (or appropriate language code) and run that framepkg.exe /install=agent /forceinstall it should change the config for the new server and connect.
If doing on W7- run from an administrative command prompt.
Thanks again for the help
The server version is ePO 4.5. Workstations are running VirusScan Enterprise 220.127.116.117. Unfortunatey a previous IT company handled the original deployment so I can't tell you how it was originally done.
When I try to run that command, I get the following error
"Another version of this product is already installed. Installation of this version cannot continue. To configure or remove the existing version of this product, use Add/Remove Programs on the Control Panel"
I've tried this on 2 different stations. On one of them, I did manage to remove the agent but I still get the same message.
What patch version of 4.5?
what agent version? (easiest way is to right click- properties and get the file vsersion number of the framepkg.exe from that location.)
to uninstall the agent from managed mode try this:
from an administrative command prompt (if windows7), navigate to c:\program files (x86)\mcafee\common framework(x64) or c:\program files\mcafee\common framework (x86)
This should remove the agent and set the machine in unmanaged mode then you can use the new framepkg to install the agent.
Thanks again, feel like progress is being made! (Been at this for days!)
ePO version is 4.5 with build 937 and Agent version is 18.104.22.1680. I've run the two commands as you've asked (in administrative mode) and when trying to install the new agent, I get the same error again. I've attached a screenshot
Thats a windows installer error- maybe remnants in registry-
Have a look at these KB articles to manually uninstall the agent.
Thanks again! Getting closer
I was able to remove the Agent properly and have tried to reinstall. Different error this time, one related to the keys being invalid but after following the KB link on it, I was able to generate some new keys.
The great news is that manually deploying the agent (after removing it) works! My test workstation is now talking to the ePO server. Thank you so much!
These machines are all managed by AD and GPOs, so is there a way I could remove the old agent and install the new one (now the ePO is working properly)?
It is possible to push the epo agent from the ePO console if you have appropriate admin acces on the devices like a domain admin account you could use.
You could sync ad to epo and in the configuration for the AD sync, you can push the agent to an unmanaged device. (Ssytem Tree, My Organization, Group Details, Synchronization Type)
In ePO you could also use Rogue System Sensors to identify devices and use that to push the agent to those devices, if you prefer not to sync to AD
You could install the agent using a startup script in AD.