But if LiveUpdate is not already installed on the target machine, the package will fail to install because LiveUpdate is required by Symantec AntiVirus. The driver has been updated. Symantec AntiVirus Corporate Edition 8.1.1 Release MR2, Build 319 New Fixes and Enhancements Symptom: When running an audit that requires authentication, providing the domain, user name and password in the respective At this time, the communications that occur in a local discovery to contact Symantec AntiVirus servers take place. weblink
To update information in Symantec System Center Start Symantec System Center. The logon account information is set once the correct account is reported. LANDesk has now included a new configuration section specifically for our unmanaged clients. Resolution: A previous change addressed the problem of the total number of viruses addressed not matching between Symantec System Center, the main user interface, and the Security Response Web site. https://support.symantec.com/en_US/article.TECH101171.html
If you recently changed a parent server's IP address, or if your parent server has more than one Network Interface Card, first read the documents that apply to your situation: Clients In order to allow Symantec AntiVirus to communicate, you must create exceptions for the correct services. The reason the snap-Ins were not initialized correctly was that their path names were saved incorrectly and in a form that they couldn't be accessed to be initialized. Resolution: Added a check for a valid buffer return from WinSock before attempting to use the buffer.
Double-click the RemoveSymantecMacFiles.command file. Each time a parent sends a packet to the client, you should see the following: Got client packet Reply from
For details, read the document Ports used for communication in Symantec AntiVirus 10.x and Symantec Client Security 3.x. Solution: AMS now detects the configuration file if it is hidden, unhides it, writes to it and marks it Hidden again. The code was modified to perform a binary XOR operation on all MAC addresses in the system to generate a more unique value. You type something in, and your search results don’t always match what you are looking for, or it doesn’t actually work at all.
Symantec AntiVirus does not check the NetWare version before copying files Symptom: Symantec AntiVirus overwrites the Norton AntiVirus Corporate Edition files on a NetWare 4.x server on an update. Symptom: Client LiveUpdate Schedule can only be modified from Configed.exe. On NetWare it causes an ABEND; on Windows platforms, it causes a Dr Watson error. The internal SMS account is reported as the shell account at login, but after a few seconds the right account is reported.
Right-click My Computer, and click Properties. https://support.norton.com/sp/en/us/home/current/solutions/v62547710_EndUserProfile_en_us Registry values ClientExpirationTimeout and PurgeQuarantine are overwritten on server upgrade Symptom: When the Symantec AntiVirus server is upgraded to a new version the registry values ClientExpirationTimeout and PurgeQuarantine under VirusProtect6 get VPN access causes clients to be dropped from server because of changing IP addresses Symptom: When a client logs in through a VPN, there is a possibility that the IP address Resolution: Symantec System Center was modified to check for the proper definitions on the source server when it is selected.
For help, read the "Checking permissions on an NTFS drive" section in Troubleshooting Symantec AntiVirus Corporate Edition installations: Checking rights and permissions. have a peek at these guys Make sure that the Symantec AntiVirus client works correctly Follow these steps on the affected clients. Resolution: Added a check in CleanupKeys to signal waiting threads before the key is deleted. The code has been corrected to resolve this problem.
Resolution: Upgraded to the latest Decomposer to resolve the issue. This information includes any server groups that have already been discovered through other discovery methods. Make sure that the Symantec AntiVirus server and client communicate correctly Often, you can restore client communication with the parent server by dropping a copy of the parent's Grc.dat file on check over here Assigning simple products to configurable: We assigned simple products… Magento E-Commerce Advertise Here 643 members asked questions and received personalized solutions in the past 7 days.
Scan omissions when scanning certain files in a long path Symptom: Scan omissions occur when scanning certain files in a long path. Changes in settings are not able to be saved in this situation. The location in the registry is: HKEY_LOCAL_MACHINE\Software\Intel\Landesk\VirusProtect6\CurrentVersion\AddressCache No network communications are initiated for this discovery method.
Resolution: This only affects Windows NT; all other supported platforms ship with an acceptable version of MMC. AOL WAN adapter) have the same MAC address for all clients. Resolution: The snap-in was selecting the current item (node) before initialization was fully finished, causing memory corruption and causing crashes during cleanup. MAC address displayed incorrectly in Symantec AntiVirus log files Symptom: MAC addresses are displayed incorrectly in the Symantec AntiVirus log files.
Resolution: If the scan of .jar file is aborted due to user request, the error message is not logged. After Upgrading to 8.1.1, Errors occur when running Outlook (cannot load plug-in .dll) Symptom: After upgrading to Symantec AntiVirus 8.1.1 and running Outlook, you see an error message that the plug-in Don't have a SymAccount? http://deftmag.com/symantec-antivirus/symantec-antivirus-could-not-communicate-with-the-selected-computer.html The event will not run on those clients.
For more information on configuring these options, read the document Configuring Windows Security Center alerts using Symantec AntiVirus Corporate Edition or Symantec Client Security. This has been corrected. This document is written so that the most recent product builds appear at the beginning of the document. An error occurred while initializing SSL-based communication.
Certain files infected by [email protected] are not detected during a manual scan in the Corporate Edition products Symptom: When a Manual Scan is run, the [email protected] worm is not detected for For every List command called, the code added duplicate data. Check Update virus definitions from parent server. Resolution: Changed the condition so that the system is not restarted when Packager passes the ReallySuppress switch.
In addition, code was added to determine whether AMS was already installed remotely and to launch the AMS install appropriately (/I or /fv) by deploying either amsremote.dat or amsover.dat. Parent server name change is not completely updated in the registry Symptom: The parent server name is changed. For more information, read Best practices for managing laptop and mobile clients with Symantec AntiVirus Corporate Edition. The communication between clients and servers does not work correctly.
© Copyright 2017 deftmag.com. All rights reserved.