********************************************************************** LiveUpdate Administration Utility (Version 1.5) README.TXT (c) 1999 Symantec Corporation May 27th 1999 ********************************************************************** HOW TO USE THIS DOCUMENT ********************************************************************** To view README.TXT on screen in Notepad or WordPad, maximize the Notepad or WordPad window. To print README.TXT in Notepad or WordPad, choose Print from the File menu. If you use another word processor, select the entire document and format the text in 10-point Courier before printing to ensure proper spacing. To print README.TXT from the DOS prompt, type COPY README.TXT PRN: ********************************************************************** CONTENTS ********************************************************************** This README.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 LiveUpdate 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 * Use of Custom Updates in the LiveUpdate Administration Utility * Logging * Known Issues ********************************************************************** 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 definitions updates. The connection is made through either a preset telephone number or Internet site. For corporate sites, two problems have arisen: * Network traffic: Administrators want to reduce external traffic by having users download from an internal site. * Security: LiveUpdate establishes an TCP/IP connection to a Symantec server. This implementation, in some cases, requires modification to firewall software. Symantec developed the LiveUpdate Administration Utility, LUADMIN.EXE, to address these issues. 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 operations 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 machines to the internal server using the LiveUpdate Administration Utility (LUADMIN.EXE). * Distribute the host file (LIVEUPDT.HST) to all workstations that use the LiveUpdate feature. * Download update packages from Symantec to the internal server using the LiveUpdate Administration Utility (LUADMIN.EXE). ********************************************************************** 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. This can be accessed through Add/Remove Programs in the Control Panel. ********************************************************************** CONFIGURING LIVEUPDATE FOR THE LIVEUPDATE ADMINISTRATION UTILITY ********************************************************************** The LiveUpdate Administration Utility uses the normal LiveUpdate client itself 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. This can be done from the LiveUpdate 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 at "C:\Program Files\Symantec\LiveUpdate") is the host file that controls LiveUpdate operation on client workstations. You must create a new file that points to an internal server to replace the existing LIVEUPDT.HST on workstations. There are four types of hosts that may be created within a host file: FTP: If you use an internal FTP server. HTTP: If you use an internal HTTP server. LAN: If you use a UNC directory. MODEM: If you use a BBS. 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. ***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 Open... from the File menu. 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: Username for the FTP server. All users use the same name. Password: Password for the specified username. 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 Choose the 32 bit or 16 bit radio button. The 32 bit radio button is selected by default. If you are creating a host file for 16 bit LiveUpdate clients, select the 16 bit radio button. 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 From the File menu, choose Save As. 8 Save the customized file as LIVEUPDT.HST. ***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 Open... from the File menu. 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: Username for the HTTP server. All users use the same name. Password: Password for the specified username. 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 modify it if necessary. 6 From the File menu, choose Save As. 7 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 Open... from the File menu. 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 into 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 into 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 From the File menu, choose Save As. 7 Save the customized file as LIVEUPDT.HST. ***Creating a Custom Host File for Modem*** To create a custom host file entry for Modem: 1 Run LUADMIN.EXE. 2 Click Host File Editor. 3 Click Open... from the File menu. 4 Select SAMPLE.HST, located in the current directory. 5 Enter the following information: Description group box --------------------- Name: Displayed when users connect to the BBS. Country / Area: Country where your BBS is located. Login group box --------------- Name: Username for the BBS. All users use the same name. Password: Password for the specified username. Connection group box -------------------- Number: The phone number including country and area code in the following format '+country (area code) number', for example: '+1 (541) 431-1300'. Area Code: The telephone dialing code for the server's location. Country Code : The international telephone dialing code for the country where the server is located. "1" is the United States. Type: Modem 6 Choose the 32 bit or 16 bit radio button. The 32 bit radio button is selected by default. If you are creating a host file for 16 bit LiveUpdate clients, select the 16 bit radio button. 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. The other text boxes displayed in this group should be grayed out and are for information only. They are not editable. 7 From the File menu, choose Save As. 8 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 is ready for distribution, copy LIVEUPDT.HST to the "C:\Program Files\Symantec\LiveUpdate" folder on 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 Retrieve tab in the Tools:Options menu. ********************************************************************** CONFIGURING AND IMPLEMENTING LIVEUPDATE UNC SUPPORT ( LAN TRANSPORT ) ********************************************************************** Configuration: -------------- The current version of LiveUpdate supports the download of packages from an internal server via UNC support without the need for an FTP or HTTP server. The support consists of 2 components: 1 A LiveUpdate DLL which supports UNC download (S32LUHL1.DLL). 2 A customized host file created by the LiveUpdate Administration Utility which 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 FTP, HTTP or modem 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 above 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 non-zero 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 contained an entry for an internal UNC location as well as for the Symantec FTP, HTTP and modem servers. This would be an ideal setup for mobile professionals who use laptops. Note: UNC support is only available with the 32 bit version of LiveUpdate. Implementation: --------------- After the host file is created, simply copy it along with the new UNC DLL (S32LUHL1.DLL) to the LiveUpdate directory on the client machines. The default directories are: \Program Files\Symantec\LiveUpdate for Windows 95/98 and Windows NT 4.0 \Win32app\Symantec\LiveUpdate for Windows NT 3.51 Note: A special issue exists for Windows 95/98 systems connecting to a Windows NT server. 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 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 The above client workstation IP address with the above Subnet Mask applied will be 155.64.159.O. This is then matched with the Subnet of the host entry. As 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 above Subnet Mask is applied (resulting in 155.64.155.0), the Subnet and resulting masked IP address will not match and 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. It is recommended to have 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 on the 'Retrieve Updates' dialog 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 updates are retrieved or not. The following is the sequence of events that occurs when the Administrator selects the "Retrieve..." button: I Temporary download directory is created. II Any available updates for the product selection that you chose are retrieved and placed in the temporary download area. III The index files are updated and any incompatible updates are removed. IV All downloaded product updates and updated index files are moved from the temporary area to your download directory. V The product List is updated. VI Any custom updates are remerged. VII The utility checks for updates to itself. LiveUpdate packages should be placed in the root of the FTP server, HTTP server or in the UNC directory specified in the host file. In addition to the downloaded packages, LUADMIN 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 wish to individually select products from a particular Symantec product line, then select the Product Line you desire, select the Details button and from the Product Line Details dialog, check both the Language(s) and Product(s) that you wish to download. Note that with individually selecting product components to update, you run the risk of missing an available update for a component inadvertently. 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 FTP,HTTP or UNC location specified in the host file. 6 Click Retrieve to begin the administrator LiveUpdate. Follow the instructions in 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 root of your FTP server, HTTP server or to the UNC directory. The next time users click LiveUpdate from 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 recommences where it left off, then integrates all packages downloaded in both sessions. However, if a download is interrupted and you recommence it with modified application settings (such as changed product/languages you wished to download) the utility will still assume, even though you have restarted with new application settings, that the cached incomplete downloads from the preceding interrupted session are part of the current session. To avoid this, you must either restart with 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 program SilntLUA.exe (normally installed to \program files\liveupdate administrator\) or LUADMIN.EXE /SILENT then packages will be retrieved without any 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, select "Update LiveUpdate Administration Utility" from the Tools menu. 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 shutdown while retrieving and installing updates for 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, you can download the client using the LiveUpdate Administration Utility. Using 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 a command line switch /s to use this functionality. You can check the version of LiveUpdate contained in the installer by checking the properties of the installer. The installer has the same version number as the version of LiveUpdate it will install. Note: If you have created a custom host file, installing a LiveUpdate upgrade using LUSETUP.EXE should not replace the host file. However, if the name of the first host (located within the Description group box) in your custom HST file is Symantec's BBS in Eugene, then the file will be replaced and you should roll out your custom host file again. If not, the custom host file will be left on the user's system unchanged and the Symantec host file will be placed in the directory using the filename LIVEUPDT.HST.DEFAULT. ********************************************************************** USE OF CUSTOM UPDATES IN THE LIVEUPDATE ADMINISTRATION UTILITY ********************************************************************** The Custom Updates functionality in LiveUpdate Administration Utility versions 1.4, 1.5 and above 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. The "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 indicate they are older than the production LiveUpdate packages. You will be informed by the SARC or Symantec Platinum Support if you need to 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, background, retrieval process) - Custom update merging - Others, such as host file encryption/decryption All events may be filtered by either Type or Status. We also provide the ability to either remove all events from the log file or to individually select the event or to 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 above installed. For your convenience we are distributing the IE 4.01 common control (COMCTL32.DLL) update with this version of the LiveUpdate Administration Utility. The LUAU.EXE application will not install this DLL, however you may install this separately as required. Note that this common control update does not work on NT 3.5x and the LiveUpdate Administration Utility does not currently support NT 3.5x. Do NOT install this common control update on NT 3.5x systems. Double-click on 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. ********************************************************************** END OF FILE **********************************************************************