Pushing out the Agent again to these machines will not break any of the products you have mentioned.
As long as you have removed the Regkey AgentGUID under "HKEY_LOCAL_MACHINE\SOFTWARE\Network Associates\ePolicy Orchestrator\Agent" rather than modifying it to empty, then a reboot and restart of the service will fix the problem, so maybe you have another issue.
Have you re-deployed the agent to a problem machine and this has worked?
Exactly how did you remove the guid on client machines? You have to remove the entire AgentGUID value from the registry, not just the value's data...
The GUID was removed via reg delete CMD. ex.
reg delete "\\COMPUTERNAME\HKEY_LOCAL_MACHINE\SOFTWARE\Network Associates\ePolicy Orchestrator\Agent" /f
Key was verified as deleted after logging onto the machine. the wierd thing is, on the couple that i tested (one at a time). everything worked out fine. rebooted and the guid was regenerated. i ran a batch file with the above cmd for 900 or so machines. verified the guid was gone, then ran a batch file to reboot all those machines that night. next day i did the check and you know the rest.
Okay, that's a bit weird. Can we confirm that command? The one you posted will remove the entire HKEY_LOCAL_MACHINE\SOFTWARE\Network Associates\ePolicy Orchestrator\Agent key, not the agentguid value. If that's the case then the agentis pretty much dead as all its keys are gone