cancel
Showing results for 
Search instead for 
Did you mean: 

Point Agent 4.0 to a new epo Server

Jump to solution

We have recently installed and moved across to a new server after installing epo 4.5 patch 1, after deploying the mcafee agent 4.5 to all machines management has been moved across to the new server for all clients except for two.

We have two 2000 Servers that the 4.5 agent obviously cant deploy to (found out after) and I was wondering if there is an easy wasy I can point them to the new epo 4.5 server for their management?

1 Solution

Accepted Solutions
McAfee Employee
McAfee Employee
Report Inappropriate Content
Message 2 of 5

Re: Point Agent 4.0 to a new epo Server

Jump to solution

Depends on the agent version they are running, but assuming it's MA4, the easiest method is probably to check the MA4 package into the Evaluation branch of the master repo. You ca then manually add system tree entries for the two systems, and then push the agent to them: when pushing the agent you'll be able to select the MA4 package.

Alternatively:

1) On the 4.5 server, export the master agent-to-server key. From the exported zip file, extract srpubkey.bin and reqseckey.bin to a temp folder.

2) Copy the sitelist.xml from the DB folder to the temp folder containing the key files.

3) Copy the temp folder to the client machines (c:\tempkeys, for example.)

4) On the client machine, locate frminst.exe (..\Program Files\McAfee\Common Framework by default)

5) From the command line execute the following:

frminst.exe /install=agent /siteinfo=c:\tempkeys\sitelist.xml

That should point the client at the new server and give it the new keys.

Regards -

Joe

4 Replies
McAfee Employee
McAfee Employee
Report Inappropriate Content
Message 2 of 5

Re: Point Agent 4.0 to a new epo Server

Jump to solution

Depends on the agent version they are running, but assuming it's MA4, the easiest method is probably to check the MA4 package into the Evaluation branch of the master repo. You ca then manually add system tree entries for the two systems, and then push the agent to them: when pushing the agent you'll be able to select the MA4 package.

Alternatively:

1) On the 4.5 server, export the master agent-to-server key. From the exported zip file, extract srpubkey.bin and reqseckey.bin to a temp folder.

2) Copy the sitelist.xml from the DB folder to the temp folder containing the key files.

3) Copy the temp folder to the client machines (c:\tempkeys, for example.)

4) On the client machine, locate frminst.exe (..\Program Files\McAfee\Common Framework by default)

5) From the command line execute the following:

frminst.exe /install=agent /siteinfo=c:\tempkeys\sitelist.xml

That should point the client at the new server and give it the new keys.

Regards -

Joe

Re: Point Agent 4.0 to a new epo Server

Jump to solution

Thanks Joe, the first way wont let me check the package into anything other than the Current as Previous and Evaluation are greyed out.

Will give the second way a go, it'll be nice to see the servers in the console again!

Re: Point Agent 4.0 to a new epo Server

Jump to solution

That worked perfectly thanks Joe

McAfee Employee
McAfee Employee
Report Inappropriate Content
Message 5 of 5

Re: Point Agent 4.0 to a new epo Server

Jump to solution

Oops, forgot that if you want to check packages into the Eval branch you have to enable the "allow check in for any branch" setting (under the "repository packages" server setting.) Sorry

Glad it's OK now though

Joe