McAfee / NAI ePO Agent
Hi,
Has anyone here managed to repackage McAfee's ePolicy Orchestrator agent into an MSI? Some of the XML files generated during the install contain the machine's name, so I'm not certain that mass deployment of this would be a good thing.
Yes, I know ePO can deploy the agent, however catching a machine when it's on and running the deployment task can be tricky - unless I've missed some sort of setting that'll take care of this for me.
Cheers,
Torren
Has anyone here managed to repackage McAfee's ePolicy Orchestrator agent into an MSI? Some of the XML files generated during the install contain the machine's name, so I'm not certain that mass deployment of this would be a good thing.
Yes, I know ePO can deploy the agent, however catching a machine when it's on and running the deployment task can be tricky - unless I've missed some sort of setting that'll take care of this for me.
Cheers,
Torren
0 Comments
[ + ] Show comments
Answers (7)
Please log in to answer
Posted by:
psomeren
20 years ago
The "Agent_[ComputerName].XML" and "Agent_{ComputerName].Log" files are created by a service called "Frameworkservice" installed and started during installation. The "PrdMgr_[ComputerName].log" file is created by a process called "naPrdMgr.exe" and is started by the "Frameworkservice" after you computer starts/reboots.
Only leave the file "Frameworklog.xls" in its place (C:\Documents and Settings\All Users\Application Data\Network Associates\Common Framework\Db), the rest will be re-created by the "Frameworkservice". Be sure to create/start this service in you MSI-package.
Only leave the file "Frameworklog.xls" in its place (C:\Documents and Settings\All Users\Application Data\Network Associates\Common Framework\Db), the rest will be re-created by the "Frameworkservice". Be sure to create/start this service in you MSI-package.
Posted by:
JillBA
20 years ago
Posted by:
craig16229
20 years ago
Torren,
Consider getting support directly from NAI concerning workstations that are difficult to catch online.
I am a big advocate of repackaging in most cases, but be careful here. I have not dealt with NAI for a couple of years, however: you don't want to find yourself in a situation where they decide not to support your environment because you deployed the agent in a fashion they consider "non-standard". Just food for thought.
Also consider the possibility of having your login script call the .exe.
Craig --<>.
Consider getting support directly from NAI concerning workstations that are difficult to catch online.
I am a big advocate of repackaging in most cases, but be careful here. I have not dealt with NAI for a couple of years, however: you don't want to find yourself in a situation where they decide not to support your environment because you deployed the agent in a fashion they consider "non-standard". Just food for thought.
Also consider the possibility of having your login script call the .exe.
Craig --<>.
Posted by:
cdupuis
20 years ago
Posted by:
craig16229
20 years ago
Posted by:
cdupuis
20 years ago
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.