Windows operating systems
32-bit systems:

Windows 2000 Professional, Server, Advanced Server, Datacenter Server, Small Business Server with Service Pack 3 or later
Windows XP Professional Edition with Service Pack 1 or later
Windows Server 2003 Standard Edition, Enterprise Edition, Datacenter Edition, Storage Edition, Web Edition, Small Business Server
Windows Vista (all versions x86 and service packs)
Windows 7 (all versions x86)
Windows Server 2008 Standard, Enterprise, Windows Server 2008 Datacenter, Windows Web Server 2008 (R2 is supported and all service packs)

64-bit systems:

Windows XP Professional Edition with Service Pack 1 or later
Windows Server 2003 Standard Edition, Enterprise Edition, Datacenter Edition, Storage Edition, Small Business Server
Windows Vista (all versions x64 and service packs)
Windows 7 (all versions x64).
Windows Server 2008 Standard, Windows Server 2008 Enterprise, Windows Server 2008 Datacenter, Windows Web Server 2008 (R2 is supported and all service packs).
Windows Essential Business Server 2008 Standard Edition and Premium Edition (R2 is supported and all service packs).
Windows Small Business Server 2008 Standard Edition and Premium Edition (R2 is supported and all service packs).

Hardware
32-bit systems:

256 MB RAM (1 GB recommended) for Windows XP, Windows XP Embedded and Windows Fundamentals for older computers
1 GB RAM minimum (2-4 GB recommended) for Windows Vista, Windows 7, Windows Server 2003 (all versions) and Windows Server 2008 (all versions)
600 MB hard disk space

Mac OS X

Mac OS X 10.4-10.6 (Only 32-bit versions)
256 MB RAM (512 MB recommended) for Mac OS X 10.4
512 MB RAM for Mac OS X 10.5
1 GB RAM for Mac OS X 10.6
300 MB of disk space for Mac

Operating system Linux (32 - and 64-bit)

Red Hat Enterprise Linux 3.x, 4.x, 5.x
SuSE Linux Enterprise (server / desktop) 9.x, 10.x
Novell Open Enterprise Server (OES/OES2)
VMWare ESX 2.5, 3.x
Ubuntu 7.x, 8.x
Debian 4.x

The management server
Processor

Note: Itanium is not supported
Intel Pentium processor or compatible architecture (32 - or 64-bit)

Windows operating systems
32-bit systems:
Windows 2000 Server, Advanced Server, Datacenter Server, Small Business Server with Service Pack 3 or later
Windows XP Professional Edition with Service Pack 1 or later
Windows Server 2003 Standard Edition, Enterprise Edition, Datacenter Edition, Storage Edition, Web Edition, Small Business Server
Windows Server 2008 Standard, Windows Server 2008 Enterprise, Windows Server 2008 Datacenter, Windows Web Server 2008 (R2 is supported and all service packs)

64-bit systems:
Windows XP Professional Edition with Service Pack 1 or later
Windows Server 2003 Standard Edition, Enterprise Edition, Datacenter Edition, Storage Edition, Web Edition, Small Business Server
Windows Server 2008 Standard, Windows Server 2008 Enterprise, Windows Server 2008 Datacenter, Windows Web Server 2008 (R2 is supported and all service packs)
Windows Essential Business Server 2008 Standard Edition and Premium Edition (supports all service packs)
Windows Small Business Server 2008 Standard Edition and Premium Edition (supports all service packs)

Hardware
32-bit systems:

1 GB of RAM (2-4 GB recommended)
4 GB of free disk space for server plus 4 GB for the database

64-bit systems:

1 GB of RAM (2-4 GB recommended) no less than 4 GB of RAM for all versions of Windows Small Business Server 2008 and Windows Essential Business Server 2008
4 GB of free disk space for server plus 4 GB for the database; Small Business Server 2008: 60 GB for the server; Essential Business Server 2008: 45 GB for the server

Control console
Processor

Note: Itanium is not supported
Intel Pentium processor or compatible architecture (32 - or 64-bit)

Windows operating systems
32-bit systems

Windows 2000 Server, Advanced Server, Datacenter Server, Small Business Server with Service Pack 3 or later
Windows XP Professional Edition with Service Pack 1 or later
Windows Server 2003 Standard Edition, Enterprise Edition, Datacenter Edition, Storage Edition, Web Edition, Small Business Server
Windows Vista (all versions x86)
Windows 7 (all versions x86)
Windows Server 2008 Standard, Windows Server 2008 Enterprise, Windows Server 2008 Datacenter, Windows Web Server 2008 (R2 is supported and all service packs)

64-bit systems
Windows XP Professional Edition with Service Pack 1 or later
Windows Server 2003 Standard Edition, Enterprise Edition, Datacenter Edition, Storage Edition, Web Edition, Small Business Server
Windows Vista (all versions x64)
Windows 7 (all versions x64)
Windows Server 2008 Standard, Windows Server 2008 Enterprise, Windows Server 2008 Datacenter, Windows Web Server 2008 (R2 is supported and all service packs)
Windows Essential Business Server 2008 Standard Edition / Windows Essential Business Server 2008 Premium Edition (R2 is supported and all service packs)
Windows Small Business Server 2008, Standard Edition, Premium Edition (R2 is supported and all service packs)

Hardware
32-bit system: 1 GB of RAM (2-4 GB recommended) 64-bit system: 1 GB of RAM (2-4 GB recommended) no less than 4 GB of RAM for all versions of Windows Small Business Server 2008 and Windows Essential Business Server 2008
15 MB of hard disk space

Database
Comes with a built-in database. Additionally supports the following systems:
32-bit systems:
Microsoft SQL Server 2000 with Service Pack 4 or later.
Microsoft SQL Server 2005 Service Pack 2.
Microsoft SQL Server 2008.

64-bit systems:
Microsoft SQL Server 2000 with Service Pack 3 or later
Microsoft SQL Server 2005 Service Pack 2
Microsoft SQL Server 2008

HDD
At least 4 GB

Release Update 7 Maintenance Patch 3 (RU7 MP3)
The LiveUpdate log file size does not save the default size setting in the settings.liveupdate file
Fix ID: 2516181
Symptom: As the size of file log.liveupdate increases, the default size setting is not saved in the settings.liveupdate file.
Solution: Fixed a cleanup call that was not invoked correctly.

Updating Symantec Endpoint Protection Manager from RU5 to RU7 fails
Fix ID: 2565649
Symptom: After you download the RU7 LiveUpdate definitions, event IDs 11328 and 1023 appear in the Symantec Endpoint Protection Manager log.
Solution: Older versions of MSIMSP sometimes create incompatible patches. Updated MSIMSP to the correct version.

Heuristic scans detect and block the application
Fix ID: 2587958
Symptom: A streamed virtualized application does not launch on the client. You can see an incorrect hash value for that application in the Symantec Endpoint Protection Manager log.
Solution: Fixed the issue by making sure that scans now correctly detect and allow a virtual application.

Symantec Endpoint Protection takes a long time to compile the profile for client groups
Fix ID: 2607064
Symptom: PackageTask takes a long time to compile the profile for client groups.
Solution: Improved the performance of XML serialization and handling multiple threads.

An email message that is based on a saved email is replaced by a draft email message
Fix ID: 2635881
Symptom: After users send a previously saved and scanned email that includes an attachment, the saved email is deleted and replaced by an identical draft of the saved email message.
Solution: The problem was caused by properties being added after the saved email was scanned. The properties caused the saved email to be unrecognized. Corrected.

Large database files are cloned for scans
Fix ID: 2642450
Symptom: Server becomes unresponsive or is brought down after scheduled scan leaves behind large number of. Tmp files.
Solution: Fixed the issue by changing when database files are cloned.

Threats delivered through email in a non-modifiable container are not deleted
Fix ID: 2646790
Symptom: A threat that is delivered through email in a non-modifiable container, such as. Rar or. Cab, is detected but not deleted, regardless of the Antivirus and Spyware policy action for the threat. You can only clean the threat after you save and unzip it to the hard disk.
Solution: Fixed the issue by quarantining the email.

The Symantec Endpoint Protection firewall interferes with Microsoft Direct Access
Fix ID: 2653542
Symptom: Microsoft Direct Access does not work after you upgrade to Symantec Endpoint Protection RU7 (11.0.7000.975).
Solution: Fixed the issue by appending an Ethernet header into that packet.

Windows Firewall messages are not disabled in the Symantec Endpoint Protection Manager System log
Fix ID: 2656231
Symptom: The System log contains messages about the Windows Firewall, even after logging is disabled. The Windows Firewall service starts after the smc service starts. Therefore, the smc service cannot find the Windows Firewall server, and considers the Windows Firewall to be disabled.
Solution: Fixed the issue by having the smc service wait for the Windows Firewall service to start.

Client downloads content from Symantec Endpoint Protection Manager even when policy indicates it should obtain content from the Group Update Provider (GUP)
Fix ID: 2660859
Symptom: When the client switches from a GUP location to an external LiveUpdate location, sylink.xml tries to download content from Symantec Endpoint Protection Manager.
Solution: Before content is downloaded, the LiveUpdate thread in sylink.xml checks whether the "SEPM channel" has been disabled. If disabled, the moniker is deleted from the queue.

The time stamp changes on restored quarantined files
Fix ID: 2661232
Symptom: The original time stamp on a file changes after being restored from the quarantine.
Solution: Fixed an issue where the time stamp and the attribute of a file are modified after being restored from the quarantine.

Mismatch between reported clients in the Unmanaged Detector report
Fix ID: 2663136
Symptom: The total number of clients on an Unmanaged Detector report does not match the actual number of devices listed.
Solution: The Unmanaged Detector report now includes the total number of detected unknown devices and the unique number of unknown devices.

Reporting server hangs
Fix ID: 2697341
Symptom: Accessing the reporting server from a web browser hangs.
Solution: The problem is caused because Internet Explorer cannot find the HTML body before the web page is loaded. Fixed the issue by modifying the body-checking mechanism, which results in lower CPU consumption.

Server logs show that the Antivirus and Spyware policy was corrupt after migration from SAV 10.x
Fix ID: 2699388
Symptom: The log file states that the Antivirus and Spyware policy is corrupt when it is not.
Solution: Fixed the issue, which was caused because some Antivirus and Spyware policies did not have the necessary Auto-Protect actions. This generated a log entry in Symantec Endpoint Protection Manager.

Time lag in copying Risk log
Fix ID: 2702682
Symptom: Risk logs are transferred to the external Syslog Server with a delay of between 15 minutes to 2 hours.
Solution: Fixed the code that caused the delay.

The management server does not remove the database backup files
Fix ID: 2703417
Symptom: The "Remove the database backup files during uninstall" feature doesn't work if the server data folder has been moved.
Solution: Fixed by deleting the current data area in conf.properties when the data and backup folders are deleted.

Errors are generated due to disabled loopback adapter
Fix ID: 2704835
Symptom: "Authentication failure. Please try again" errors are generated by securitynotifytask or scheduledreportingtask when the owner / creator of the notification or report is valid.
Solution: Fixed the code to allow the IP request from the local computer.

Folder exclusions for scans does not work
Fix ID: 2705877
Symptom: Exclusions for a folder in the format of \ foldername works for Auto-Protect but fails for manual and scheduled scans.
Solution: Fixed by expanding the folder exclusions for all possible drives. Folder exclusions now work for manual scans.

Notification not logged in notification view
Fix ID: 2712563
Symptom: "Single Risk Event" notification is not logged in the notification view in Symantec Endpoint Protection Manager when the event was triggered.
Solution: When a single risk event occurs, Symantec Endpoint Protection Manager now writes it to the database, where you can view it by clicking Notifications> View notifications.

Connection pool timeout on Symantec Endpoint Protection Manager
Fix ID: 2713908
Symptom: Cannot connect the Symantec Endpoint Protection Manager console with the database.
Solution: Deleted the unnecessary database connections that do not close.

Clients do not update definitions downloaded from Symantec Endpoint Protection Manager
Fix ID: 2715989
Symptom: After the clients come out of standby, the definitions are not updated until after Symantec Endpoint Protection Manager is restarted.
Solution: Fixed so that LiveUpdate restarts after the client computer recovers from standby.

"Definitions out of date" notification is not triggered
Fix ID: 2726085
Symptom: The notifications for "Definitions out of date" do not trigger if the "Computer name" filter is applied.
Solution: Fixed an issue where the SQL parameter "Computer name" was not set.

Virus definitions use too much disk space
Fix ID: 2733222
Symptom: Virus definitions are not removed after updates, which use a large amount of disk space.
Solution: Cleaned up definitions directories that were caused by a failure from integrating definitions.

Registry value not cleaned up
Fix ID: 2733251
Symptom: Some registry keys were left behind after uninstalling the client.
Solution: Fixed by deleting the registry keys that were added after initial installation.

Some system files are not visible in the unmanaged client user interface
Fix ID: 2740080
Symptom: Unable to exclude VMMS.EXE and VMWP.EXE in W2K8R2 in an unmanaged SEP 11.0 RU7 MP1 client.
Solution: Fixed the issue by calling an API that allows the viewing of all system files.

Remote push install of Symantec Endpoint Protection 11 RU7 MP1 with Lotus Notes email plug-in displays an error
Fix ID: 2743085
Symptom: When other users attempt to log on to the computer during a remote push of the client with the Lotus Notes plug-in, the following error message appears: "The User Profile Service failed the logon user profile cannot be loaded."
Solution: Added an API to retrieve the correct environment variable to correctly set the path in the registry key.

With Lotus Notes plug-in, the existing user can log on but new user gets error message
Fix ID: 2757734
Symptom: Limited admins can log on to the management server, but get the following error message: "Symantec Antivirus has stopped working." The nlnvp.dll is not loaded in nlnotes.exe and is not included in notes.ini file.
Solution: Fixed an issue that was not making the correct calls.

Older definitions are not removed
Fix ID: 2765535
Symptom: Virus definitions are sometimes not removed after being updated.
Solution: Fixed by allowing the removal of older definitions per customer settings.

. Err files are not cleaned up
Fix ID: 2767546
Symptom: Files with the. Err extension are produced but not cleaned up. This causes the parsing of events to be missed by Symantec Endpoint Protection Manager.
Solution: Fixed the code to bypass the error. Symantec Endpoint Protection Manager will continue to process the log and log the error line.

Limited admins cannot see LiveUpdate policy
Fix ID: 2770776
Symptom: The LiveUpdate policy does not appear correctly for limited administrators.
Solution: Fixed the issue by displaying the user selection for the limited administrator even if the checkbox is read-only.

Many *. Tmp files are created under Common Client folder
Fix ID: 2775251
Symptom: After an Auto-Protect remediation and client restart, some. Tmp files may remain in the \ alluser \ symantec \ CommonClient folder.
Solution: Fixed the issue by adding a registry key to control the Auto-Protect thread exit time threshed (60 seconds by default).

Smc service crashes when using the Group Update Provider (GUP)
Fix ID: 2777440
Symptom: The GUP crashes in an environment without the bypass list in the current user's proxy settings.
Solution: Fixed by adding a null pointer check when copying the settings.

Symantec Endpoint Protection Manager Scan log status is not updated
Fix ID: 2778391
Symptom: The scan status of the Scan log doesn't get updated when an administrator-defined scheduled scan is suspended and then completed.
Solution: Fixed by adding the suspended event into a list of known events that the management server will process.

Scan time is not reported
Fix ID: 2782191
Symptom: The Symantec AntiVirus for Linux client does not report the last scan time to Symantec Endpoint Protection Manager.
Solution: Fixed by updating the LAST_SCAN_TIME in the table when processing the Security log from the Symantec AntiVirus Linux client.

Incorrect grouping in Symantec Endpoint Protection Manager reports
Fix ID: 2783830
Symptom: The Group by field in Symantec Endpoint Protection Manager reports always groups by the "Risk Severity" category. The correct Group by appears in edit mode.
Solution: Fixed by correcting the "group_by" string values.

RADIUS settings not saved for the Enforcer
Fix ID: 2791090
Symptom: The management server does not save the Enforcer RADIUS settings.
Solution: Fixed by removing a broken or unused management server list. When you edit the Enforcer properties, the broken or unused management server list is now skipped.

File or folder exclusions do not appear in the client
Fix ID: 2798801
Symptom: With Windows Server 2008 R2 Core and Symantec Endpoint Protection 11 RU7 MP1 or MP2, you could not add a folder or file exception in the Symantec Endpoint Protection client.
Solution: Fixed the issue by removing the flag that displays the browse dialog correctly.

Unmanaged client appears in the Symantec Endpoint Protection Manager console
Fix ID: 2800124
Symptom: When you create and deploy a client installation package using the default group policy settings but with the Use Group Communication Settings setting turned off, an unmanaged client is installed.
Solution: Fixed an issue to remove the location-level communication settings in the exported package.

Symantec AntiVirus for Linux logs are not replicated
Fix ID: 2804484, 2915591
Symptom: Symantec AntiVirus for Linux logs do not get replicated to remote sites.
Solution: Fixed an issue where legacy clients were deleted from some tables during replication.

Replication failed
Fix ID: 2810324
Symptom: The replication fails continuously. The data.zip file is generated and transferred, but replication is not successful.
Solution: Fixed this issue by cloning the default management server list in the Enforcer's policy.

End user can stop administrator-defined scans
Fix ID: 2823247
Symptom: Normally, when an administrator-defined scan runs and the scan dialog appears, users are not allowed to stop the scan. However, users can still stop the scan by pressing the Return key.
Solution: Fixed so that the admin setting is correctly processed if a user tries to stop a scan.

Clients do not communicate with Symantec Endpoint Protection Manager after a failed migration
Fix ID: 2823318
Symptom: After a failed migration from a 32-bit management server to a 64-bit management server, some clients stop communicating with the management server. To work around this issue, you could reimport the sylink file.
Solution: Fixed the issue by synchronizing the certificate between the database and the disk.

GUP list is reset
Fix ID: 2823881
Symptom: The GUP list is reset at midnight during database maintenance.
Solution: Fixed an incorrectly used operator in the SQL query.

Cannot log filename or directory name with "L SC" option
Fix ID: 2825062
Symptom: vpdebug.log cannot log the. Dbcs file name and directory name with the "L SC" option. This happens on files or folders that contain unicode characters.
Solution: Fixed the issue by converting the unicode character to a multi-byte character in the function.

Lotus Notes scan records are left on the client computer
Fix ID: 2834021
Symptom: The default behavior is for scan records for Lotus Notes to remain on the client computer. You had to change the default value on each computer manually.
Solution: The default setting in the registry for Lotus Notes Auto-Protect is now "NotLeaveScanRecords = 1."

OEMxx.inf files are deleted
Fix ID: 2838172
Symptom: The oem13.inf and oem14.inf files are deleted when uninstalling the client.
Solution: Fixed the issue by checking whether files are Symantec drivers before the files are deleted.

When Application and Device Control is enabled, Firefox hangs when user accesses pages with Flash content
Fix ID: 2877820
Symptom: When Application and Device Control is enabled, and the user accesses Flash-based content with Firefox 13.0.1 and the Flash player plug-in 11.3.300.242, the browser hangs and the user must kill the process manually.
Solution: Fixed the issue that caused the hang.

The Symantec Endpoint Protection Manager service crashes
Fix ID: 2883310
Symptom: The management server service crashes when you use a different version of the Java remote console.
Solution: Fixed the issue by adding a product version check (excluding the build number) between the console and the management server.

Performance impact with Limited Admin rights
Fix ID: 2885818
Symptom: The Home page and the client groups take a long time to load in the Symantec Endpoint Protection Manager Java remote console when you are logged on with a limited administrator account.
Solution: Improved the limited administrator performance issues and reduced the number of times the administrator context is reloaded.

Scan status in the Scan log is not getting updated
Fix ID: 2887476
Symptom: Scan status in the Scan log doesn't get updated when an administrator-defined scheduled scan is suspended and then completed.
Solution: Fixed an issue where the suspended status and scan complete info was not recorded correctly.

Pie chart rendering failure with error ezcGraphInvalidDataException
Fix ID: 2898439
Symptom: There is a pie chart rendering failure on the Symantec Endpoint Protection Manager Monitor tab> Comprehensive Risk Report> Risk Distribution graph.
Solution: Fixed an issue to deal with the computed percent value if it is <0.