Symantec SAV10.1.4/SCS3.1.4 MP1

cryopig

downloads
ftp://ftp.symantec.com/public/en ... ._mp1_allwin_en.zip
ftp://ftp.symantec.com/public/en ... ._mp1_allwin_en.zip


http://service1.symantec.com/SUP ... id/2006050314483048

Maintenance Patch 1 for Maintenance Release 4 (MR 4 MP 1)
This section describes the fixes in Maintenance Patch 1 for Maintenance Release 4 of Symantec AntiVirus 10.1 and Symantec Client Security 3.1. This patch can be applied only to computers that run Symantec AntiVirus 10.1.4 or Symantec Client Security 3.1.4. To learn how to obtain and apply the patch, read Applying Maintenance Patch 1 for Symantec Client Security 3.1 and Symantec AntiVirus 10.1 Maintenance Release 4.

Symantec AntiVirus Corporate Edition 10.1.4.4010-1


Shared Components

Shared Component Version Build
Symantec AntiVirus 10.1.4 4010-1
Quarantine Server 3.5.4 56
AMS 6.12.0 142
Auto-Protect 9.7.1 4
Behavior Blocking 2.2.0 7
Decomposer 3.2.14 10
LiveUpdate 3.0.0 160
NAVAPI 4.2.0 8
SymEvent 12.0.3 1
Common Client 104.0.11 1



New fixes

Server Group Server Tuning Options do not propagate to secondary servers
Fix ID: 1-5R7DVU
Symptom: After you create a primary server and enable legacy support at the server group level, the settings do not propagate to secondary servers.
Resolution: Added the Server Tuning Options settings to the GRCSrv.dat file, which is distributed to secondary servers.

Virus definitions do not update until the Symantec AntiVirus service restarts
Fix ID: 642963
Symptom: After LiveUpdate runs, the Definfo.dat file is updated, but the Usage.dat file is not updated until the Symantec AntiVirus service restarts.
Resolution: Minor change to the code to correct this issue.

Symantec AntiVirus service (Rtvscan.exe) does not start
Fix ID: 631839
Symptom: In some specific environments, the Symantec AntiVirus service (Rtvscan.exe) does not start.
Resolution: Fixed in Common Client 104.0.11.1.

Improved handling of Rapid Release definitions
Fix ID: 769756
Symptom: You apply Rapid Release virus definitions to a Symantec AntiVirus server. After the server pushes the new virus definitions to its clients, the server then pushes a full virus definition set to its clients. The use of Rapid Release virus definitions requires more network traffic than the use of other virus definitions.
Resolution: Symantec AntiVirus servers can now deploy Rapid Release virus definitions without pushing a full virus definition set to clients. This change reduces the amount of network traffic that is needed to use Rapid Release virus definitions in a managed environment.


Symantec Client Security 3.1.4.4010-1

Shared Components

Shared Component Version Build
Symantec Client Security 3.1.4 4010-1
Symantec Client Firewall 8.7.4 84
Symantec Client Firewall Administrator 8.7.4 84
Ad Blocking 2005.3.0 30
SymNetDrv 6.0.3 303
SymSentry 2.1.0 101
IPS (SymIDSCo) 6.2.2 2


New fixes

User permissions are not applied to ALEScan
Fix ID: 1-5EOPZ5
Symptom: Restricted users can run ALEScan. A restricted user should not be able to run ALEScan.
Resolution: Changed the code to check user permissions when ALEScan runs. A restricted user sees the alert, \"You do not have privileges to run this program.\"

Messaging for Exchange does not work properly with Symantec Client Firewall
Fix ID: 1-5LB0S3
Symptom: When you use MSN 2.x to send messages to another MSN 2.x client through an Exchange 2000 server, the messages do not arrive.
Resolution: SymNetDrv filters the port that MSN uses to log on and prevents the completion of the logon process. Fixed in SymNetDrv version 6.0.3.

New clients do not receive policy files from the parent server
Fix ID: 1-5V1707
Symptom: When a Symantec Client Security 3.1 client checks in with its parent server for the first time, the client does not automatically download the policy file after the first reboot.
Resolution: Changed the code to allow the policy file to be downloaded under a certain set of conditions which were previously causing the client update to fail.

SSIM SMNP traps sometimes do not have the MAC and/or IP addresses for Symantec Client Firewall events
Fix ID: 632290/ 632271
Symptom: The MAC and/or IP address sometimes does not appear in the event information that the client sends to the SSIM appliance.
Resolution: Added additional methods to obtain the MAC address and IP address to ensure that the addresses are always discovered and sent with the event.