Primary server does not update secondary servers or clients using the VDTM

Article:TECH100441  |  Created: 2003-01-29  |  Updated: 2007-01-26  |  Article URL http://www.symantec.com/docs/TECH100441
Article Type
Technical Solution

Product(s)

Issue



You configure a Symantec AntiVirus Corporate Edition primary server to run LiveUpdate and deliver virus definitions by using the Virus Definition Transport Method (VDTM). The primary server updates its own virus definitions, but it does not update the secondary servers or clients.


Solution



To fix the problem, try each of the following solutions in the order in which they appear. After each solution, test your program to determine whether the problem is fixed.

Update virus definitions by using an .xdb file
This problem can happen if you update the primary server by using the executable Intelligent Updater file. The Intelligent Updater installs virus definitions for the server, but it does not include files for the server to pass to the clients and secondary servers. To solve this problem, update by using the latest .xdb file from the Security Response Web site.
For instructions, read the document for your program version:
Confirm that secondary servers and clients are licensed
Symantec Client Security and Symantec AntiVirus Corporate Edition may include electronic licensing (the Business Pack version), or no licensing may be included.
To find out whether your program version require a license, read the document for your program version:
To find out whether a license has been applied to a client or server, read Determining whether a license has been applied to a Symantec AntiVirus 9.x or later client or server.

To learn how to obtain and apply licenses, read About licensing Symantec Client Security 2.0 or 3.0 Small Business Pack.

To test for incorrect LiveUpdate registry information
  1. On the primary server, start Symantec AntiVirus.
  2. Click LiveUpdate.
  3. In the LiveUpdate dialog box, examine the list of products.

If LiveUpdate lists "Norton AntiVirus Corporate Edition" instead of a product name starting with "Symantec," LiveUpdate has incorrect information in the registry.

To correct LiveUpdate registry information
  1. In the Registry Editor, go to the following registry key:

    HKEY_LOCAL_MACHINE\SOFTWARE\INTEL\LANDesk\VirusProtect6\CurrentVersion\LiveUpdate\CmdLines\CmdLine1

  2. In the CmdLine1 key, modify the following values according to the version of Symantec AntiVirus:
    Value name
    Symantec AntiVirus 8.x Value
    Symantec AntiVirus 9.x Value
    Symantec AntiVirus 10.0 Value
    Symantec AntiVirus 10.1 Value
    ProductLanguageSymAllLanguagesSymAllLanguagesSymAllLanguagesSymAllLanguages
    ProductNameSymantec AntiVirus Corporate ServerSymantec AntiVirus Corporate ServerSymantec AntiVirus Corporate ServerSymantec AntiVirus Corporate Server
    ProductTypeVirusDefVirusDefVirusDefVirusDef
    ProductVersion8.09.010.010.1
  3. In the CmdLine2 key, modify the following values:
    Value name
    Symantec AntiVirus 8.x Value
    Symantec AntiVirus 9.x Value
    Symantec AntiVirus 10.0 Value
    Symantec AntiVirus 10.1 Value
    ProductLanguageEnglishEnglishEnglishEnglish
    ProductNameSymantec AntiVirus Corporate Server NTSymantec AntiVirus Corporate Server NTSymantec AntiVirus Corporate ServerSymantec AntiVirus Corporate Server
    ProductTypeUpdateUpdateUpdateUpdate
    ProductVersion8.09.010.010.1
  4. Exit the Registry Editor.
  5. Run LiveUpdate again to update the server group.
  6. After several minutes, verify that the virus definitions are updating secondary servers and clients by refreshing Symantec System Center.

If you do not see that the virus definitions are updating, there may be a communication problem. For information on troubleshooting communication problems, read the appropriate document from the References section.


References
For information about troubleshooting communication problems, read the document for your product version:




Legacy ID



2003082912294348


Article URL http://www.symantec.com/docs/TECH100441


Terms of use for this information are found in Legal Notices