Moved to ePO for better support.
I'm assuming the traffic is not open for that workgroup. ePO can manage any machine that has the proper comms open to it, most likely you just need to open the necessary ports for communication.
I have opened them now (well a few minutes after posting this). Just now need to see if the ports are open and if so - how do I get the EPO to re-establish the connection?
Do a wake up call to that agent from ePO and see if it responds.
Otherwise you can log on locally to that server in the workgroup and open the McAfee agent status monitor and watch the logs to see what the issue is. The error logs are located locally here: C:\ProgramData\McAfee\Common Framework\DB
Just tried that, but still saying unmanaged.
So the EPO on the domain is saying it's still unmanaged.
Gone to that location, do you know which logs show the attempt for wake up agent?
There are a couple things I would look at locally to make sure of:
1. Open the mcafee agent status monitor and try to collect/send props on that workgroup server, what error does it give when trying to connect?
2. Then go to C:\ProgramData\McAfee\Common Framework\DB and open the Agent_computername.log; within here it should show the error from above and the IP/port it is trying to connect to. Is the IP/port correct? Also look at the _error.log and see if that gives more information. If the ip/port is correct, its still a comm issue.
You could also try to uninstall/reinstall the agent with the Framepkg.exe from the ePO if you wanted, but probably won't help.
Just for awareness, you can also take a look at these files in C:\ProgramData\McAfee\Common Framework:
SiteList.xml - lists ePO and repositories the agent will try an comm with, make sure the "master" is correct
Agent.ini - lists the agents comm ports which will change once it has communicated with ePO if you are using custom ports