********************************************************************** LiveUpdate Administration Utility (Version 1.5.3) Readme.txt Copyright (c) 2001 Symantec Corporation October 2001 ********************************************************************** HOW TO USE THIS DOCUMENT ********************************************************************** To view this file in Notepad or WordPad, maximize the Notepad or WordPad window. To print this file from Notepad or WordPad, click the File menu and select Print. If you use a different word processor, select the entire document text and format the text in 10-point Courier before printing to ensure proper spacing. To print from the MS-DOS prompt, type COPY LUAU.TXT PRN: and press Enter. ********************************************************************** CONTENTS ********************************************************************** This Luau.txt file describes the LiveUpdate Administration Utility from Symantec. The following topics are discussed: * About the LiveUpdate Administration Utility * Installing the LiveUpdate Administration Utility * Configuring the LiveUpdate client for the LiveUpdate Administration Utility * Creating a LiveUpdate host file for client workstations * Configuring and implementing LiveUpdate UNC support * TCP/IP by location * Update retrieval process * Updating the LiveUpdate Administration Utility * Automatic/silent package retrieval * Rolling out an updated version of the LiveUpdate client * Using custom updates in the LiveUpdate Administration Utility * Logging * Known issues * Recent fixes ********************************************************************** ABOUT THE LIVEUPDATE ADMINISTRATION UTILITY ********************************************************************** LiveUpdate is the Symantec technology that permits an installed Symantec product to connect to a Symantec server automatically for program and virus definition updates. The connection is made through either an Internet connection or, in the case of a corporate site, a network connection. For corporate sites, this utility addresses two possible issues: * Network traffic: Administrators want to reduce external traffic by having users download from an internal site. * Security: An administrator can download updates to one machine and test with them before rolling them out to the entire user base. Note that the downloads via LiveUpdate Administrator establish a TCP/IP connection to a Symantec server. In some cases you may be required to modify your firewall software to allow communication from the machine running LiveUpdate Administrator. You can set up either an intranet FTP or HTTP server. You can also set up a directory on a standard file server to handle all LiveUpdate packages for your network. Users connect to an internal server to retrieve updates instead of connecting to external Symantec servers. To set up a LiveUpdate intranet server, you must do the following: * Install the LiveUpdate Administration Utility. * Create a custom host file (Liveupdt.hst) that points client computers to the internal server using the LiveUpdate Administration Utility (Luadmin.exe). * Distribute the host file (Liveupdt.hst) to all workstations that use LiveUpdate. * Download update packages from Symantec to the internal server using the LiveUpdate Administration Utility (Luadmin.exe). These steps are discussed in detail in the following sections. ********************************************************************** INSTALLING THE LIVEUPDATE ADMINISTRATION UTILITY ********************************************************************** The LiveUpdate Administration Utility is distributed as a self-extracting, compressed archive (Luau.exe). To install the LiveUpdate Administration Utility, run Luau.exe. This is a self-extracting installation program. Wizards will lead you through the entire installation process. The LiveUpdate Administration Utility also has an uninstaller. You can access it through Add/Remove Programs in the Control Panel. ********************************************************************** CONFIGURING THE LIVEUPDATE CLIENT FOR THE LIVEUPDATE ADMINISTRATION UTILITY ********************************************************************** The LiveUpdate Administration Utility uses the normal LiveUpdate client to retrieve updates. If you need special proxy (or other) settings to run LiveUpdate from the workstation on which you are running the LiveUpdate Administration Utility, you may have to configure the LiveUpdate client settings. Do this from the LiveUpdate applet in the Control Panel. See the Readme.txt file installed in the LiveUpdate client installation folder (\Program Files\Symantec\ LiveUpdate). ********************************************************************** CREATING A LIVEUPDATE HOST FILE FOR CLIENT WORKSTATIONS ********************************************************************** Liveupdt.hst (located in the C:\Program Files\Symantec\LiveUpdate folder) is the host file that controls LiveUpdate operation on client workstations. You must create a new Liveupdt.hst file that points to an internal server, and replace the existing Liveupdt.hst file on each workstation. There are three types of hosts that can be created within a host file: * HTTP: If you use an internal HTTP server. * FTP: If you use an internal FTP server. * LAN: If you use a UNC directory. Modem host types should be ignored. The order in which the host entries appear in the host file is important if you are supporting both HTTP and FTP. Whichever host type (HTTP or FTP) is specified first becomes the default connection type. NOTE: When you are upgrading your existing LiveUpdate clients using Lusetup.exe, the client installer will NOT overwrite the existing Liveupdt.hst file if the Name fields in the Description area of the Host File Editor in either the first or second entries of the customized Liveupdt.hst host file have been modified. When LiveUpdate client versions that are >= 1.6 read in a custom host file they merge its contents with their local LiveUpdate client settings file and delete the Liveupdt.hst file. ***Creating a Custom Host File for HTTP*** To create a custom host file entry for HTTP: 1. Run Luadmin.exe. 2. Click Host File Editor. 3. Click the File menu, and click Open. 4. Select Sample.hst, located in the current directory. 5. Enter the following information: Description group box --------------------- Name: Displayed when users connect to the internal server. Country/Area: Country where your server is located. Login group box --------------- Name: User name for the HTTP server. All users use the same name. Password: Password for the specified user name. Connection group box -------------------- URL: Either the IP address of the server or an Internet- style name (URL) for the server. Type: HTTP Subnet: ---.---.---.--- Subnet Mask: ---.---.---.--- Refer to "TCP/IP by location" for more details on Subnet and Subnet Mask. NOTE: The 32-bit radio button is selected by default. HTTP-based hosts are not available to 16-bit clients. If you choose 16-bit, you are given the option of having the utility convert the host into an FTP host. If you choose Yes, you will need to review the host and, if necessary, modify it. 6. Click the File menu, and click Save As. 7. Save the customized file as Liveupdt.hst. ***Creating a Custom Host File for FTP*** To create a custom host file entry for FTP: 1. Run Luadmin.exe. 2. Click Host File Editor. 3. Click the File menu, and click Open. 4. Select Sample.hst, located in the current directory. 5. Enter the following information: Description group box --------------------- Name: Displayed when users connect to the internal server. Country/Area: Country where your server is located. Login group box --------------- Name: User name for the FTP server. All users use the same name. Password: Password for the specified user name. Connection group box -------------------- URL: Either the IP address of the server or an Internet- style name (URL) for the server. Type: FTP Subnet: ---.---.---.--- Subnet Mask: ---.---.---.--- Refer to "TCP/IP by location" for more details on Subnet and Subnet Mask. 6. Click either 32-bit or 16-bit. The 32-bit radio button is selected by default. If you are creating a host file for 16-bit LiveUpdate clients, click 16-bit. If the 16-bit version of LiveUpdate is installed, then the DLLs in the LiveUpdate directory will have names starting with S16. If the 32-bit version is installed, the file names will start with S32. NOTE: The 16-bit and 32-bit host files are not compatible with each other. 7. Click the File menu, and click Save As. 8. Save the customized file as Liveupdt.hst. ***Creating a Custom Host File for LAN*** To create a custom host file entry for a UNC directory: 1. Run Luadmin.exe. 2. Click Host File Editor. 3. Click the File menu, and click Open. 4. Select Sample.hst, located in the current directory. 5. Enter the following information: Description group box --------------------- Name: Displayed when users connect to the internal server. Country/Area: Country where your server is located. Login group box --------------- Name: A user name with access rights to the server. If this field is left blank, LiveUpdate will attempt to connect using the current user name logged in to the system. Password: The password which corresponds to the user name. If this field is left blank, LiveUpdate will use the password for the current user logged in to the system. Connection group box -------------------- Directory: The UNC path to the server directory containing the packages. Type: LAN NOTE: The 32-bit radio button is selected by default. LAN-based hosts are not available to 16-bit clients. 6. Click the File menu, and click Save As. 7. Save the customized file as Liveupdt.hst. For a LiveUpdate client to use your customized host file, the file must be named Liveupdt.hst. When the Liveupdt.hst file is ready for distribution, copy it to the C:\Program Files\Symantec\LiveUpdate folder on the user workstations. Typically, you modify your network login scripts to perform the copy automatically. Note that when the LiveUpdate Administration Utility attempts to retrieve packages as requested by an administrator, or when it attempts to retrieve updates to itself, it uses the setting "Host File Used for Update Retrieval" as specified on the Retrieve tab (click the Tools menu, and click Options). ********************************************************************** CONFIGURING AND IMPLEMENTING LIVEUPDATE UNC SUPPORT (LAN TRANSPORT) ********************************************************************** Configuration: The current version of LiveUpdate supports the downloading of packages from an internal server using UNC support without the need for an HTTP or FTP server. The support consists of 2 components: * A LiveUpdate DLL, which supports UNC download (S32luhl1.dll). * A customized host file created by the LiveUpdate Administration Utility. This file points to the internal server. By default, the UNC DLL becomes the exclusive transport when it is present. The intent is to prevent users from using HTTP or FTP when the administrator has determined that it is better for them to use a UNC path. Under Windows 95/98 and Windows NT 4.0 it is possible for versions of LiveUpdate 1.4x, 1.5x, and later to have "Network" available as one of the connection options in the LiveUpdate wizard. The following registry entry needs to be made under HKEY_LOCAL_MACHINE\Software\Symantec\LiveUpdate\Preferences: Name: All Transports Available Type: DWORD If this entry is nonzero and S32luhl1.dll is present in the LiveUpdate directory, then Network will be an available connection option. This feature could be used, for example, so that a host file could contain an entry for an internal UNC location, as well as for the Symantec HTTP and FTP. This would be an ideal setup for mobile professionals who use laptops. NOTE: Only the 32-bit version of LiveUpdate supports UNC. Implementation: After creating the host file, copy it along with the new UNC DLL (S32luhl1.dll) to the LiveUpdate directory on the client computers. The default directories are: \Program Files\Symantec\LiveUpdate for Windows 95/98/NT 4.0 \Win32app\Symantec\LiveUpdate for Windows NT 3.51 NOTE: A special issue exists for Windows 95/98 systems connecting to a server running Windows NT. Windows 95/98 users need to have access rights to the resource. LiveUpdate on LAN connections will ignore a user name and password when supplied in the host file. The solution is to create a shared resource on a server which all users are authorized to access. ********************************************************************** TCP/IP BY LOCATION ********************************************************************** Within the host file, if an entry is to be enabled for TCP/IP by location, then it will need both a valid subnet and subnet mask. LiveUpdate will apply the subnet mask of the host entry to the IP address of the client workstation and then will try to match the resulting IP address with the Subnet of the same host entry. If both the masked IP address and subnet match, LiveUpdate will use that particular host to access the LiveUpdate server defined within that host. If the IP address with subnet mask applied does not match the subnet defined within the same host entry, LiveUpdate will proceed to the next host entry and repeat the same process. Sample host configuration: Host entry URL/IP: myserver.liveupdate.com Host entry subnet: 155.64.159.0 Host entry subnet mask: 255.255.255.0 IP address of client workstation: 155.64.159.20 In this sample, the client workstation IP address with the subnet mask applied will be 155.64.159.0. This is then matched with the subnet of the host entry. Because these two IP addresses are identical, LiveUpdate will now use this host to connect to the specified LiveUpdate server. If the client workstation IP address is 155.64.155.80 and the subnet mask is applied (resulting in 155.64.155.0), the subnet and resulting masked IP address will not match; LiveUpdate will proceed to the next host entry and repeat the same process. If no matching host entries are found, the LiveUpdate session will fail. We recommend having a default host entry that does not contain either subnet or subnet mask information as the last entry in the host file. ********************************************************************** UPDATE RETRIEVAL PROCESS ********************************************************************** The list of products that is displayed in the Retrieve Updates dialog box is dynamically generated from a product list. This list is downloaded automatically from the Symantec LiveUpdate server at the end of every download session. This occurs whether or not updates are retrieved. Here is the sequence of events after the Administrator clicks the Retrieve button: 1. A temporary download directory is created. 2. Available updates for the product you chose are retrieved and placed in the temporary download area. 3. The index files are updated and incompatible updates are removed. 4. All downloaded product updates and updated index files are moved from the temporary area to the download directory. 5. The product list is updated. 6. Custom updates are re-merged. 7. The utility checks for updates to itself. LiveUpdate packages should be placed on your LiveUpdate server in the location specified in the host file by the URL, IP address, or directory. In addition to the downloaded packages, the LiveUpdate Administration Utility retrieves index files called Symtri.zip, Livetri.zip and Symtri16.zip. These files are required by different versions of LiveUpdate. To retrieve update packages: 1. Run Luadmin.exe. 2. Click Retrieve Updates. 3. Select the desired language(s) for download packages. 4. Check the Symantec products that will be supported. Because all installed Symantec products that use LiveUpdate now point to your intranet server, it is always safer to check all products that are used in your organization. If you want to individually select products from a particular Symantec product line, then select the product line you desire, click the Details button, and in the Product Line Details dialog box, check both the Language(s) and Product(s) that you want to download. Note that by individually selecting product components to update, you run the risk of missing an available update for a component. 5. Specify the download directory. This is the location where the update packages and support files will be stored when downloaded from Symantec. It can be a temporary "holding" area or it can be the HTTP, FTP, or UNC location specified in the host file. 6. Click Retrieve to begin the administrator LiveUpdate. Follow the instructions on each succeeding panel to retrieve the packages. NOTE: If for any reason the LiveUpdate Administration Utility does not successfully download all of the packages that you originally selected for download, then none of the packages will appear in the download directory. 7. Copy the entire contents of the download directory to the location of your LiveUpdate server as specified in the host file by the URL, IP address, or directory. The next time users click LiveUpdate on their workstations, they will receive the packages from your internal server, not Symantec's external server. The LiveUpdate Administration Utility knows if a download is interrupted. When you restart the download, assuming that no application settings have changed, the utility restarts where it left off and integrates all packages downloaded in both sessions. However, if a download is interrupted and you restart it using modified application settings (such as changed product/languages you wanted to download) the utility will still assume that the cached incomplete downloads from the preceding interrupted session are part of the current session, even though you restarted using new application settings. To prevent this, either restart using the same application settings or remove the cached incomplete downloads from your [LiveUpdate Admin]/TEMP folder. ********************************************************************** AUTOMATIC/SILENT PACKAGE RETRIEVAL ********************************************************************** A feature called Silent LiveUpdate Administrator allows scheduled LiveUpdates to retrieve all the packages you need. If you run the Silntlua.exe program (normally installed in \Program Files\ LiveUpdate Administrator\) or you run LUADMIN.EXE -SILENT from the command prompt, then packages will be retrieved with no user intervention required. The only indication that this program is running is the task bar icon (labeled "Silent LU Admin") that remains until the program exits. Please note that you first need to run LiveUpdate Administrator to select the products to support, the language, and the download location. Once LiveUpdate Administrator exits, the settings are saved and Silent LiveUpdate Administrator will use them every time it runs. ********************************************************************** UPDATING THE LIVEUPDATE ADMINISTRATION UTILITY ********************************************************************** The LiveUpdate Administration Utility can update itself. When the LiveUpdate Administration Utility has finished downloading packages, it will automatically check for new LiveUpdate Administration Utility updates. To manually check for LiveUpdate Administration Utility updates, click the Tools menu and click "Update LiveUpdate Administration Utility." If an update is available, it will appear in the Select Updates panel. Check the package, and it will be installed automatically. Note that the LiveUpdate Administration Utility will temporarily shut down while retrieving and installing updates to itself. ********************************************************************** ROLLING OUT AN UPDATED VERSION OF THE LIVEUPDATE CLIENT ********************************************************************** You can either manually download the latest LiveUpdate setup file from the Symantec Internet site at ftp://ftp/public/english_us_canada/liveupdate/updates/lusetup.exe or http://www.symantec.com/techsupp/files/lu/lu.html or you can download the client using the LiveUpdate Administration Utility. The latter method allows your LiveUpdate clients to directly update their workstations from your internal server. When run manually, the installer can be run silently. Use the /s /a /q command line switches to use this functionality. NOTE: If you have a custom host file (Liveupdt.hst) on your client machines, you MUST modify the Name field (as displayed in the Description area of the Host File Editor) of the first or second entry to prevent the LiveUpdate installer (Lusetup.exe) from overwriting your custom host file during an update. The LiveUpdate installer is used to install or patch LiveUpdate. The client installer will NOT overwrite the existing Liveupdt.hst file if the Name field (in the Description area of the Host File Editor) in either the first or second entries of the customized Liveupdt.hst host file has been modified. ********************************************************************** USING CUSTOM UPDATES IN THE LIVEUPDATE ADMINISTRATION UTILITY ********************************************************************** The Custom Updates functionality in LiveUpdate Administration Utility versions 1.4, 1.5, and later are for use by customers who receive packages directly from Symantec. These packages have not yet been released on the LiveUpdate production servers. These packages can be used to address unique situations, such as virus definitions that detect and remove a new virus or other specific customer needs. These packages can be rolled out to client systems along with any production packages that are available from Symantec. "Custom update location" specifies where the packages you received from Symantec are located on your system. You can use the browse button to locate the files. The "Active custom updates" box lists any current custom updates that are being applied by the LiveUpdate Administration Utility. The custom updates can be deleted manually using the Delete button, or if the "Automatically delete obsolete custom updates" box is checked, the packages will be deleted once all the date information in the packages indicates they are older than the production LiveUpdate packages. You will be informed by SARC (Symantec AntiVirus Research Center) or Symantec Platinum Support whether you should use this option and how to proceed further. ********************************************************************** LOGGING ********************************************************************** With the release of LiveUpdate Administration Utility 1.5, we have added a user interface for logging events, such as: * The retrieval process (including silent and background) * Custom update merging * Others, such as host file encryption/decryption All events may be filtered by either type or status. We also allow you to remove all events from the log file, individually select the event, or filter the event by type or status and then remove it. ********************************************************************** KNOWN ISSUES ********************************************************************** In order for this version of the LiveUpdate Administration Utility to load you must have Comctl32.dll version 4.72x or later installed. For your convenience we are distributing the IE 4.01 common control (Comctl32.dll) update with this version of the LiveUpdate Administration Utility. Luau.exe will not install this DLL; you may, however, install this separately as required. Note that this common control update does not work under Windows NT 3.5x, and the LiveUpdate Administration Utility does not currently support Windows NT 3.5x. Do NOT install this common control update on computers running Windows NT 3.5x. Double-click the 401comupd.exe executable in the LiveUpdate Administration Utility directory, which is normally installed to C:\Program Files\LiveUpdate Administration. The LiveUpdate host file does not support double-byte characters. ********************************************************************** RECENT FIXES ********************************************************************** * Fixed an incompatibility between LUAdmin and LiveUpdate 1.6x. The option to "retrieve new and previously downloaded updates" now works correctly in LiveUpdate 1.6x. Build 18. * Added support for future versions of LiveUpdate, which will require that all Symantec content updates be electronically signed. Build 18. * Fixed a product defect where LUAdmin was not correctly merging new TRX files into the TRI file. Build 19. * Added support for electronically signed custom updates. LiveUpdate client version 1.7x or higher now requires at least build 21 of this version of the Administration utility (>= 1.5.3.21). ********************************************************************** END OF FILE **********************************************************************