Resolved issues from McAfee Common Management Agent 3.5.0 patch 2
Goal and/or Problem Description
Resolved issues from McAfee Common Management Agent 3.5.0 patch 2
CMA3502.ZIP
Framework service fails to start
Slow log off
Slow log on
Randomized tasks start at the same time
Quotes around imagepath
Updating from a disabled repository
RSSENSOR.EXE crash
Problem Environment
McAfee Common Management Agent
Changes affecting this Problem
Change information is not available for this solution
Cause of this Problem
Cause information is not available for this solution
Solution 1:
IMPORTANT:
The patch listed above can be downloaded directly without contacting Technical Support. It is located at the following location: You must be registered with Prime Support Service Portal and have a valid Grant number for this product to access the patch. If you do not have a valid Grant number, please contact Customer Service at 800-338-8754 As of the time of this posting, this patch was the latest patch available for the product and issues listed above. If this patch is no longer present, please check for a newer version.
Solution 2:
PREVIOUSLY RESOLVED ISSUES
1. ISSUE:
The Framework service fails to start if the
sitelist.xml file does not contain an FTP or an
HTTP repository.
RESOLUTION:
The Framework service now starts, even if the
sitelist.xml file does not contain an FTP or an
HTTP repository.
2. ISSUE:
The Common Management Agent is not added to the
Microsoft Windows Firewall whitelist on
installation.
RESOLUTION:
The Common Management Agent is now added to the
firewall whitelist on installation.
3. ISSUE:
The Framework service fails to start if the
sitelist.xml file includes a large number of
repositories.
RESOLUTION:
This problem was caused when the Framework
service would ping the repositories on service
startup. The Windows Service Control Manager
would time out before all the repositories could
be contacted. Now the Framework service does not
ping all of the repositories in the sitelist.xml
file prior to startup.
4. ISSUE:
The Framework service fails to start and
generates a 1920 error in some environments.
RESOLUTION:
The Framework service "image path" now contains
quote marks. This allows the Framework service
to start without error.
5. ISSUE:
The Common Management Agent did not support a
503 (server busy) response code. This event type
was added with McAfee ePolicy Orchestrator 3.0.2
patch 8 and later.
RESOLUTION:
The Common Management Agent now supports this
response code and will retry at a later date if
it receives this return when contacting the
server.
6. ISSUE:
McAfee GroupShield Exchange 6.0 could lock files
in use by the Common Management Agent, causing
the Common Management Agent to fail to upgrade.
RESOLUTION:
The Common Management Agent now successfully
upgrades even if the files are locked by McAfee
GroupShield Exchange 6.0.
7. ISSUE:
Slow logon or logoff occurred, due to roaming
profiles and the Common Management Agent?s use
of Microsoft?s WININET.DLL.
RESOLUTION:
The Common Management Agent now releases
WININET.DLL after each use. This allows faster
logon and logoff for users with roaming
profiles.
8. ISSUE:
Agent-to-server communication fails.
RESOLUTION:
Improvements have been made to the
agent-to-server communication in the Common
Management Agent.
9. ISSUE:
Microsoft Windows 95 and Windows 98 clients are
locked out of the domain when the Common
Management Agent is trying to update on certain
domain environments.
RESOLUTION:
The Common Management Agent now does not cause
lock out for Windows 95, Windows 98, or Windows
ME clients from the domain.
10. ISSUE:
User names that included characters under 032
ASCII would cause the event files from the
Common Management Agent to be discarded.
RESOLUTION:
User names that include a character under 032
ASCII now are displayed as "N/A".
11. ISSUE:
The Common Management Agent did not respond to
an HTTP error code 416 correctly, which would
lead to an error downloading the System
Compliance Profiler installer.
RESOLUTION:
The Common Management Agent now handles an HTTP
416 error code correctly.
12. ISSUE:
Randomized scheduled tasks start at the same
time for multiple clients.
RESOLUTION:
The Common Management Agent randomization has
been improved so that tasks now run at different
times on different clients.
Solution 3:
RESOLVED ISSUES
1. ISSUE:
Remote System Sensor product version not displayed properly.
RESOLUTION:
Remote System Sensor product version is now displayed correctly.
2. ISSUE:
The date format in the engine plugin key cause Checkpoint software to fail.
RESOLUTION:
The date format has been modified to work with Checkpoint software.
3. ISSUE:
A user defined sitelist.xml containing a large amount of disabled repositories before an enabled repository could cause an update from a disabled repository.
RESOLUTION:
The framework service now dynamically generates the buffer size needed to hold the entire sitelist.xml. The framework service will not try to update from a disabled repository.
4. ISSUE:
RSSENSOR.EXE crashes
RESOLUTION:
A timing issue in the framework service has been corrected that was causing the crash in RSSENSOR.EXE.
5. ISSUE:
UPDATERUI.EXE running multiple times on a terminal server.
RESOLUTION:
UPDATERUI.EXE will now only run on the local server. UPDATERUI.EXE will not run on terminal server clients.
Goal and/or Problem Description
Resolved issues from McAfee Common Management Agent 3.5.0 patch 2
CMA3502.ZIP
Framework service fails to start
Slow log off
Slow log on
Randomized tasks start at the same time
Quotes around imagepath
Updating from a disabled repository
RSSENSOR.EXE crash
Problem Environment
McAfee Common Management Agent
Changes affecting this Problem
Change information is not available for this solution
Cause of this Problem
Cause information is not available for this solution
Solution 1:
IMPORTANT:
The patch listed above can be downloaded directly without contacting Technical Support. It is located at the following location: You must be registered with Prime Support Service Portal and have a valid Grant number for this product to access the patch. If you do not have a valid Grant number, please contact Customer Service at 800-338-8754 As of the time of this posting, this patch was the latest patch available for the product and issues listed above. If this patch is no longer present, please check for a newer version.
Solution 2:
PREVIOUSLY RESOLVED ISSUES
1. ISSUE:
The Framework service fails to start if the
sitelist.xml file does not contain an FTP or an
HTTP repository.
RESOLUTION:
The Framework service now starts, even if the
sitelist.xml file does not contain an FTP or an
HTTP repository.
2. ISSUE:
The Common Management Agent is not added to the
Microsoft Windows Firewall whitelist on
installation.
RESOLUTION:
The Common Management Agent is now added to the
firewall whitelist on installation.
3. ISSUE:
The Framework service fails to start if the
sitelist.xml file includes a large number of
repositories.
RESOLUTION:
This problem was caused when the Framework
service would ping the repositories on service
startup. The Windows Service Control Manager
would time out before all the repositories could
be contacted. Now the Framework service does not
ping all of the repositories in the sitelist.xml
file prior to startup.
4. ISSUE:
The Framework service fails to start and
generates a 1920 error in some environments.
RESOLUTION:
The Framework service "image path" now contains
quote marks. This allows the Framework service
to start without error.
5. ISSUE:
The Common Management Agent did not support a
503 (server busy) response code. This event type
was added with McAfee ePolicy Orchestrator 3.0.2
patch 8 and later.
RESOLUTION:
The Common Management Agent now supports this
response code and will retry at a later date if
it receives this return when contacting the
server.
6. ISSUE:
McAfee GroupShield Exchange 6.0 could lock files
in use by the Common Management Agent, causing
the Common Management Agent to fail to upgrade.
RESOLUTION:
The Common Management Agent now successfully
upgrades even if the files are locked by McAfee
GroupShield Exchange 6.0.
7. ISSUE:
Slow logon or logoff occurred, due to roaming
profiles and the Common Management Agent?s use
of Microsoft?s WININET.DLL.
RESOLUTION:
The Common Management Agent now releases
WININET.DLL after each use. This allows faster
logon and logoff for users with roaming
profiles.
8. ISSUE:
Agent-to-server communication fails.
RESOLUTION:
Improvements have been made to the
agent-to-server communication in the Common
Management Agent.
9. ISSUE:
Microsoft Windows 95 and Windows 98 clients are
locked out of the domain when the Common
Management Agent is trying to update on certain
domain environments.
RESOLUTION:
The Common Management Agent now does not cause
lock out for Windows 95, Windows 98, or Windows
ME clients from the domain.
10. ISSUE:
User names that included characters under 032
ASCII would cause the event files from the
Common Management Agent to be discarded.
RESOLUTION:
User names that include a character under 032
ASCII now are displayed as "N/A".
11. ISSUE:
The Common Management Agent did not respond to
an HTTP error code 416 correctly, which would
lead to an error downloading the System
Compliance Profiler installer.
RESOLUTION:
The Common Management Agent now handles an HTTP
416 error code correctly.
12. ISSUE:
Randomized scheduled tasks start at the same
time for multiple clients.
RESOLUTION:
The Common Management Agent randomization has
been improved so that tasks now run at different
times on different clients.
Solution 3:
RESOLVED ISSUES
1. ISSUE:
Remote System Sensor product version not displayed properly.
RESOLUTION:
Remote System Sensor product version is now displayed correctly.
2. ISSUE:
The date format in the engine plugin key cause Checkpoint software to fail.
RESOLUTION:
The date format has been modified to work with Checkpoint software.
3. ISSUE:
A user defined sitelist.xml containing a large amount of disabled repositories before an enabled repository could cause an update from a disabled repository.
RESOLUTION:
The framework service now dynamically generates the buffer size needed to hold the entire sitelist.xml. The framework service will not try to update from a disabled repository.
4. ISSUE:
RSSENSOR.EXE crashes
RESOLUTION:
A timing issue in the framework service has been corrected that was causing the crash in RSSENSOR.EXE.
5. ISSUE:
UPDATERUI.EXE running multiple times on a terminal server.
RESOLUTION:
UPDATERUI.EXE will now only run on the local server. UPDATERUI.EXE will not run on terminal server clients.