Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

Changelog for 11.0.1000?

Created: 28 Dec 2007 • Updated: 22 May 2010 | 3 comments

Saw that SEP 11.0.1000 was posted and I am downloading it. Wanted to see if there was a changelog available.

Thanks!

Comments 3 CommentsJump to latest comment

Csring's picture
Symantec Endpoint Protection fixes
    Compatibility with Checkpoint VPN
    Fix ID: 964738
    Symptom: Installation of Checkpoint VPN will either fail or VPN client will not function when Device Control is installed with Symantec Endpoint Protection client.
    Solution: Modified white list to remove incompatible reference to sr_service.exe

    Performance of Outlook e-mail Protection
    Fix ID: 1087587
    Symptom: Performance degradation on system when Outlook Auto-Protect plugin is enabled.
    Solution: Modified the Outlook plugin so that it scans attachment when they are selected for open rather when the message is selected to be read

    Accessing remote network shares after the installation of Symantec Endpoint Protection
    Fix ID: 1124570
    Symptom: Altering the installation of Symantec Endpoint Protection with Network Threat Protection, users cannot access remote network shares.
    Solution: Modified default rule set for the "Self Managed" client to prevent traffic from being blocked.

    Wireless communication blocked by default with stand-alone client
    Fix ID: 1146977
    Symptom: Rule generated that allows EAPOL was set to block by default. Stand-alone client does not have access to set this rule in the UI.
    Solution: Modified the UI so that a stand-alone user can change the EAPOL to allow or block. It is set to allow by default on the stand-alone client.

    Symantec Endpoint Protection client install fails at 75% install
    Fix ID: 1149379
    Symptom: Symantec Endpoint Protection client install fails at 75% install
    Solution: Removed component attempting to stop and restart the service. A reboot prompt will occur when SNAC is installed so that the Wireless Zero Configuration service can stop and start with the operating system rather than having the SNAC install attempt to perform the action.

    Windows NT Event contains many LiveUpdate entries
    Fix ID: 1154429
    Symptom: LiveUpdate Events fill Windows System Log with multiple entries
    Solution: Created a local cache of content sequence numbers logs are not created unless the LiveUpdate product inventory is changed.

    Access to network share are lost after installing Symantec Endpoint Protection client on Windows Server
    Fix ID: 1154729
    Symptom: Access is lost to Windows Server 2003 shares after files are copied to the server that has Symantec Endpoint Protection client installed on it
    Solution: AutoProtect was modified to detect such conditions and prevent the deadlock from occurring

    Symantec Management Client (SMC.exe) uses more cpu when user is not logged into system.
    Fix ID: 1131386
    Symptom: SMC service spikes the CPU then reaches a steady state of 40-50% cpu when the users logs out.
    Solution: SMC spiked the cpu looking for a logged in user. Modified the search function so that it will use less cpu time.

    Importing OU structure from eDirectory LDAP server
    Fix ID: 1129941
    Symptom: Importing OU structure from eDirectory synchronizes the root objects but does not pull objects beneath the root.
    Solution: Modified the search parameters to return the normal and operational parameter as an operational parameter so that objects will be imported correctly.

    Synchronization with Active Directory fails when conflict records exist.
    Fix ID: 1138805
    Symptom: Organizational Units do not import correctly from Active Directory if conflict entries are encountered during the import process.
    Solution: Modified importing code so that invalid entries are skipped. Skipped entries are logged to the debug log.

    Client connecting with Symantec Endpoint Protection Manager
    Fix ID: 1123148
    Symptom: Kernel memory leak in WPS Helper driver prevents IIS from accepting connections.
    Solution: Resolved memory leak

    Floppy drive scanning
    Fix ID: 1161393
    Symptom: Floppy drives are scanned on shutdown even though administrator selects them not be scanned
    Solution: The option will be set correctly to the desired configuration

    Description for Auto-Protect setting was switched.
    Fix ID: 1162823
    Symptom: The Auto-Protect setting "Scan when a file is accessed or modified" was incorrectly switched with the setting, "Scan when a file is accessed".
    Solution: Changed the UI so that each setting has the correct description.

    GroupWise 7.X installation fails with Symantec Endpoint Protection installed.
    Fix ID: 1165265
    Symptom: Installing Symantec Endpoint Protection with Application and Device Control prevents GroupWise 7.x from launching correctly.
    Solution: Modified application and device control policy so that it was using the correct operating system folder.

    Deployment Wizard prompts for username and password on every computer
    Fix ID: 1167447
    Symptom: Deployment Wizard (Client Remote) is prompting for username and password for each computer that is selected to have the client deployed to even when the credentials are the same.
    Solution: Now using the authentication cache to eliminate unnecessary re-entering of user/password info when deploying multiple clients. This is similar to the way that ClientRemote worked in 10.x

    Error when running Configuration Wizard to install an additional site for replication
    Fix ID: 1175545
    Symptom: When running the Management Server Configuration Wizard to install an additional site for replication (using SQL 2005), the wizard interrupts with a data truncation error.
    Solution: Handled DateTime field correctly with French version of SQL

    SEPM no longer downloads definitions after being updated with rapid release .jdb file.
    Fix ID: 1163481
    Symptom: After updating SEPM with a rapid response .jdb file, it would no longer process the newer certified definitions brought down through LiveUpdate.
    Solution: Modified the logic on SEPM so that it processed the .jdb definitions as the newest definitions.

    Protective Threat Protection signatures not updating on client
    Fix ID: 1167523
    Symptom: Symantec Known Application list not updating when client was configure to get content from SEPM.
    Solution: Setting the correct values for LiveUpdate server when client is pulling content from SEPM.

    SEP client is not showing icon in the system tray
    Fix ID: 1145044
    Symptom: The yellow shield icon in the system tray was not being displayed. All users will see is the green circle when the client is communicating with the manager.
    Solution: Corrected logic condition which caused icon to not be displayed.

    Logging into SEPM Console when SEPM is installed on the same system as Backup Exec Continuous Protection Server
    Fix ID: 1142597
    Symptom: Communication error is received when attempting to log into SEPM Console after SEPM is installed on the same computer as Backup Exec Continuous Protection Server.
    Solution: This was caused by a port conflict on 8443. Installation wizard was modified to detect the port in use and to select an alternate port. This Solution will work for any application that has already bound port 8443.

    Compatibility issue with Microsoft SQL profiler tool
    Fix ID: 1146828
    Symptom: Application popup: PROFILER90.EXE - Application Error : The application failed
    to initialize properly (0xc0000005). Click on OK to terminate the application.
    Solution: Resolved compatibility issue with sysplant driver.

    Client User Interface status will show red when the Lotus Notes e-mail protection is not installed.
    Fix ID: 1139886
    Symptom: The status on the main client user interface will display red when the Lotus Notes plugin is not installed with the client.
    Solution: Modified the client status so that it will exclude the Lotus Notes e-mail protection if it is not installed on the client.

    Application Control is disabled when Network Threat Control is disabled
    Fix ID: 1008642
    Symptom: When user selects to disable Network Threat Protection, Application Control protection is disabled.
    Solution: Modified controls so that disabling Network Threat Protection does not disable Application Control

    Device Control is disabled when Network Threat Protection is disabled
    Fix ID: 1008655
    Symptom: When user selects to disable Network Threat Protection, Device Control protection is disabled.
    Solution: Modified controls so that disabling Network Threat Protection does not disable Device Control

    Deploying clients to active directory groups
    Fix ID: 1123131
    Symptom: Deploying client packages to computers appearing in a active directory group appear in the temporary group.
    Solution: Modified the sylink file so that it is not overwritten by an "unmanaged" sylink file.

    Startup Scan running after Migration from SCS to SEP v11.0
    Fix ID: 1127065
    Symptom: A startup scan runs even though it was originally set to disabled prior to the migration.
    Solution: Modified the attribute on migration so that the startup scan would not run if configured to not do so.

    Stand-alone client install does not function when exported from Symantec Endpoint Protection Manager
    Fix ID: 1148518
    Symptom: All files and folders were missing the first character when files are extracted to the temp directory. This prevented the client installation package from executing correctly.
    Solution: Modified path export function to remove extra patch separator so that all files had the correct characters

    Locked Auto-Protect settings do not propagate to client
    Fix ID: 1153011
    Symptom: Client GUI used the read-only attribute to prevent changes from being made rather than displaying a grey state
    Solution: Client GUI will display the proper locked state when access to control is set to lock from the SEPM console.

    Block rule for CD/DVD's no longer functions after migrating SEP v11.0 over SSEP 5.1 server
    Fix ID: 1154818
    Symptom: Block rule for CD/DVD's does not trigger after migrating to SEP v11.0 from SSEP 5.1.
    Solution: Updated the upgrade mechanism to set new domain for devices so that policy is successful migrated.

    Missing Network Threat Protection component when logging in as restricted user
    Fix ID: 1155546
    Symptom: Network Threat Protection does not show up in main client UI after switching from an administrator account to a restricted account.
    Solution: Modified session processing logic so that it was tolerant to error in operating system API.

    Symantec Auto-Upgrade Agent service fails to start
    Fix ID: 1167997
    Symptom: Error Message(s): Service Control Manager popup error: "At least one service or driver failed during system startup"
    Error Event ID 7000 in the Windows system event log.
    Source: Service Control Manager.
    Description: The Symantec Auto-upgrade Agent service failed to start due to the following error: “The system cannot find the file specified."
    Solution: No longer setting the smcinst.exe service to Automatic when the service is already installed

Csring's picture
Client Group information in the Troubleshooting section displays the client group name only
Fix ID
: 1168861
Symptom: The entire path of the client group is not displayed in the troubleshooting section.
Solution: Modified the display so that the entire client group path will be shown.

Schedule Scans not running when user is logged off
Fix ID: 1169275
Symptom: On windows 2000 systems, schedule scans were not running when user logged off, if configured to do so.
Solution: Modified logon code to check for smcgui rather than vptray.

Client UI would not display new definition date
Fix ID: 1171767
Symptom: On Windows Vista, SEP Client UI would not update virus definition date after they were downloaded
Solution: Modified check for VirusDefs so that the directory change notification was received correctly

Exporting client troubleshooting data
Fix ID: 1054802
Symptom: Information that appeared in the client Troubleshooting section could not be exported
Solution: The ability to export troubleshooting data has been added to the SEP client

Displaying clients in the Virus Definition Distribution table
Fix ID: 1104932
Symptom: Clients that did not have Network Threat Protection module installed are listed in the Virus Definition Distribution Table.
Solution: The report correctly filters out clients that should not be displayed if the technology is not installed

Configuring missed LiveUpdate events
Fix ID: 1105014
Symptom: Client UI did not include the setting to allow a LiveUpdate event to be run when the computer was off during the scheduled time.
Solution: The client scheduled LiveUpdate UI was updated to include the missed event option.

Setting policy to allow user to modify LU schedule
Fix ID: 1110115
Symptom: Setting the option "Allow the user to manually launch LiveUpdate", would not enable this feature on the client
Solution: Setting the option in the Console will allow the end user to modify the LiveUpdate schedule

Firewall does not enable when changing locations
Fix ID: 1139747
Symptom: Firewall does not enable when it computer changes to a new location if the user disabled it in the old location
Solution: Firewall will be enabled when it detects a new location

System Lockdown generates a large amount of log events that are forwarded to the management server
Fix ID: 1139876
Symptom: A large number of the same events will appear in the control logs when System Lockdown is configured in log only mode. Most of these events will be for the same files.
Solution: A damper control has been added which will prevent identical log entries from displaying if they occur within the same 60 seconds.

RTVScan.exe application error
Fix ID: 1162150
Symptom: An error dialog appears with the following information; RTVscan.exe Application Error - Unknown exception (0xc00000fd) occurred in the application at location 0x65ec9abc
Solution: Modified shutdown thread to wait for proper termination rather than depend on a delay cycle

Client updates definitions from quarantine location
Fix ID: 1053078
Symptom: Client does not switch to using LUA to download definitions when it is in a quarantine location
Solution: Client will successfully switch the policy to allow it to pull definitions from LUA

Auto-Protect option is not set correctly on the client
Fix ID: 1108152
Symptom: Enabling the option to "Check floppies when the computer shuts down" would disable the feature on the client.
Solution: Modified settings for the configuration file so that it was applied correctly at the client

Showing the correct status on the client UI for AntiVirus and antispyware
Fix ID: 1117515
Symptom: When a restricted user opens the main client UI, they see red X's for AntiVirus and antispyware status as well as protective threat protection
Solution: Since restricted users do not have the rights on the system to change the status, the red X' are not displayed.

Report "Clients with Latest policy" does not show clients with older policies
Fix ID: 1158086
Symptom: Report "Clients with Latest policy" does not show clients with older policies.
Solution: Added the latest policy serial number as a reference so that all policies would be displayed.

Viewing reports with the time range, "Past 24 hours" results in an error message
Fix ID: 1159662
Symptom: On the first of the month, if any log or report is selected with the time range set to "Past 24 hours" the user will get a message, " Your Start Date must be greater than the end date."
Solution: Modified logic in the filter to correctly adjust for the shift in days

Symantec Network Access Control fixes
    Incompatibility with Symantec Network access control and L2TP VPN connection
    Fix ID: 1158037
    Symptom: Incompatibility with Symantec Network access control and L2TP VPN connection
    Solution: SNAC was modified to detect whether PPTP or L2PT VPN connections are being used so that original EAP dll’s are used rather than SymRasMan.dll for authentication
lautamas's picture
Anybody mind sharing the update file and upload to a public server such as rapidshare?