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
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
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.
Answered 05/28/2004 by: psomeren
Senior Yellow Belt

Please log in to comment
0
This would be a big ditto for psomeren.
Answered 06/21/2004 by: jdelgadillo
Senior Yellow Belt

Please log in to comment
0
We had a problem with this and finally decided that we would use the setup.exe supplied by NAI and send it out via SMS silently. We were unable to capture the entire installation as there were a number of bits that were not captured by Wise Package Studio.
Answered 06/22/2004 by: JillBA
Senior Yellow Belt

Please log in to comment
0
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 --<>.
Answered 06/22/2004 by: craig16229
Third Degree Brown Belt

Please log in to comment
0
We have dealt with this exact issues with NA and they do not support repackaging the install, they will tell you that. End of phone call. Hope this helps. Be aware that version 8.0i is out in July, maybe wait until then, they may have packaged it in MSi form.
Answered 06/22/2004 by: cdupuis
Third Degree Green Belt

Please log in to comment
0
We have dealt with this exact issues with NA and they do not support repackaging the install, they will tell you that. End of phone call.

cdupuis,

That's what I thought. Thanks for the confirmation.

Craig --<>.
Answered 06/22/2004 by: craig16229
Third Degree Brown Belt

Please log in to comment
0
Has anyone tried doing a setup conversion with a tool like the Installshiled Repackaging wizard? We didn't have those tools back then, now we do, but we have it all deployed already.
Answered 06/22/2004 by: cdupuis
Third Degree Green Belt

Please log in to comment
Answer this question or Comment on this question for clarity