CMA (agent) patch 7

[Sephir0th]

you can download it from here

http://sdownload.nai.com/products/protected/hotfix/CMA3127.Zip

issues solved...

RESOLVED ISSUES

1. ISSUE:
Installation of Common Management Agent version
3.1.2 Patch 6 would not complete on some Windows
95 systems.

RESOLUTION:
This issue has been fully resolved in this
release.

2. ISSUE:
Emailing a web page from some versions of
Internet Explorer would cause Outlook to stop
responding when the "Send" button was clicked.

RESOLUTION:
This issue has been fully resolved in this
release.

3. ISSUE:
There was a potential security issue with URIs
sent to the agent when they contained a dot
character.

RESOLUTION:
This issue has been fully resolved in this
release. McAfee would like to thank Robert W.
Baird for identifying this issue, and working
with us to resolve it in a professional and
timely manner.

4. ISSUE:
In previous releases, it was possible to deploy
a site list that contained invalid information
for a network, causing remote agents to be
orphaned and unable to communicate to any
ePolicy Orchestrator server. This would usually
require manual intervention to resolve.

RESOLUTION:
This release of the Common Management Agent
includes a new feature that allows the agent to
keep track of the last good known ePolicy
Orchestrator connection in the system registry.
If a site list is deployed to the agent that
contains a list of sites that it cannot connect
to, it will make an attempt to connect to this
saved ePolicy Orchestrator site to retrieve
another site list that may have corrected data.
This feature aids system administrators in
recovering from deployments of site lists that
contain invalid information.

5. ISSUE:
Sitelist.xml files that contained "Type=Server"
references would not be overwritten or modified,
even if a new site list is downloaded from the
ePolicy Orchestrator server. This mainly
affected VirusScan Enterprise 7.0 customers
migrating from an unmanaged environment to one
managed by ePolicy Orchestrator.

RESOLUTION:
This release of the Common Management Agent
correctly modifies a sitelist.xml file if it
contains "Type=Server" and new site list
information has been retrieved from the ePolicy
Orchestrator server.

 

[bfralia]

You might want to hold up on that patch for the moment. What was the agent version? I downloaded it last Thursday before doing a 3.01 to 3.02a upgrade and ended up with agent 3.1.2.242 which causes framework services to max out. I think it came from that patch. I can't find anything in the readme that says what the installed agent version is.

McAfee is checking on this now as I type.

 

[Sephir0th]

i installed it in my test environment and the version reported is

3.1.2.283

so it´s newer than the version that you claim that has problems

cheers

 

[VictorySabre]

I also installed it on my test environment and it is reported to be 3.1.2.283.

 

[jfp23]

I have it in my production environment without issue as version 3.1.2.283

 

[bfralia]

Good, I'm glad it's not the evil one I got. Now the question is where did the one I have come from?

I just didn't want anyone to share the same problems I had and am having.

I you look in the readme when you unzip that agent, you'll notice at the bottom of the problem/resolution section they omitted the part where it says what the installed version will be. If you look at CMA3126, you'll notice it says 3.1.2.273 so this patch should be a higher number.

 

[VictorySabre]

Did you apply the CMA patch before the ePO 3.0.2a upgrade? Have you updated ePO 3.0.2 to the latest patch #6 as well? If not, give them a try first and then upgrade the CMA to this new version and see how it goes. I haven't seen any problems with this new CMA version with my test PCs, but I'll just wait a little more before upgrading my production environment.

 

[Sephir0th]

here´s some info on the server and agent version, according to NAI, and depending on the version installed
hope you can solve your inquiry

3.0.2.287 ePolicy Orchestrator 3.0.1 SP2 and Patch 6

3.0.2.280 ePolicy Orchestrator 3.0.1 SP2 and Patch 5

3.0.2.276 ePolicy Orchestrator 3.0.1 SP2 and Patch 4

3.0.2.274 ePolicy Orchestrator 3.0.1 SP2 and Patch 3

3.0.2.236 ePolicy Orchestrator 3.0.1 SP2


----

3.1.2.283 ePolicy Orchestrator 3.0.2 (Patch 7 for CMA 3.1.2a)

3.1.2.273 ePolicy Orchestrator 3.0.2 (Patch 6 for CMA 3.1.2a)

3.1.2.268 ePolicy Orchestrator 3.0.2 (Patch 5 for CMA 3.1.2a)

3.1.2.266 ePolicy Orchestrator 3.0.2 (Hotfix 4 for CMA 3.1.2a)

3.1.2.265 ePolicy Orchestrator 3.0.2 (Patch 3 for ePO 3.1.2a)

3.1.2.264 ePolicy Orchestrator 3.0.2 (Hotfix 2 for CMA 3.1.2a)

3.1.2.260 ePolicy Orchestrator 3.0.2 (Hotfix 1 for CMA 3.1.2a)

3.1.2.257 ePolicy Orchestrator 3.0.2 (Hotfix CMA 3.1.2a)

3.1.2.242 ePolicy Orchestrator 3.0.2 (Service Pack 2)

 

[Sephir0th]

here´s some information from NAI about the agent and server versions depending on the patch/hotfix installed
hope it´s of some utility

3.1.3.106 Protection Pilot 1.0

3.1.2.283 ePolicy Orchestrator 3.0.2 (Patch 7 for CMA 3.1.2a)

3.1.2.273 ePolicy Orchestrator 3.0.2 (Patch 6 for CMA 3.1.2a)

3.1.2.268 ePolicy Orchestrator 3.0.2 (Patch 5 for CMA 3.1.2a)

3.1.2.266 ePolicy Orchestrator 3.0.2 (Hotfix 4 for CMA 3.1.2a)

3.1.2.265 ePolicy Orchestrator 3.0.2 (Patch 3 for ePO 3.1.2a)

3.1.2.264 ePolicy Orchestrator 3.0.2 (Hotfix 2 for CMA 3.1.2a)

3.1.2.260 ePolicy Orchestrator 3.0.2 (Hotfix 1 for CMA 3.1.2a)

3.1.2.257 ePolicy Orchestrator 3.0.2 (Hotfix CMA 3.1.2a)

3.1.2.242 ePolicy Orchestrator 3.0.2 (Service Pack 2)

----

3.0.2.287 ePolicy Orchestrator 3.0.1 SP2 and Patch 6

3.0.2.280 ePolicy Orchestrator 3.0.1 SP2 and Patch 5

3.0.2.276 ePolicy Orchestrator 3.0.1 SP2 and Patch 4

3.0.2.274 ePolicy Orchestrator 3.0.1 SP2 and Patch 3

3.0.2.236 ePolicy Orchestrator 3.0.1 SP2

 

[bfralia]

I finally traced 3.1.2.242 back to the service pack 2a. Odd thing is that when i check in the package for CMA3127 and deploy it to one machine, it comes up as 3.1.2.257 which as least it doesn't run away! I've re-checked the package in and am waiting for a test workstation to load just in case I did something wrong.

VictorySabre:

I did the upgrade, then applied 3.02a patch 6 then applied the agent.

I traced the problem back to the 3.1.2.242 agent coming with the 3.0.2a upgrade. The deployment task was enable and 162 computers were updated to the runaway patch BEFORE I was able to apply patch 6 and check in the latest agent! Love them giga bit ports.

Odd thing is that McAfee was almost yelling at me about where I got the agent from. Claim they took the agent off their website. It was a bad release according to them but my fault because it's in the service pack.