readme by Tickingtimebomb1


									********************************************************************** LiveUpdate Client (Version 3.2) README.TXT Copyright (c) 2006 Symantec Corporation OCTOBER 2006 ********************************************************************** Copyright (C) 2006 Symantec Corporation. All rights reserved. Symantec and the Symantec Logo are trademarks or registered trademarks of Symantec Corporation or its affiliates in the U.S. and other countries. Other names may be trademarks of their respective owners. The Licensed Software and Documentation are deemed to be "commercial computer software" and "commercial computer software documentation" as defined in FAR Sections 12.212 and DFARS Section 227.7202. ********************************************************************** CONTENTS ********************************************************************** This README.TXT file describes LiveUpdate from Symantec. The following topics are discussed: * * * * * * * * LiveUpdate Privacy Proxy Server Security Consideration Installing/Uninstalling LiveUpdate LiveUpdate Configuration & Log files Using AOL (America Online) Known Issues Recent fixes Acknowledgements

********************************************************************** LiveUpdate Privacy ********************************************************************** During normal LiveUpdate operation certain data may be captured in the LiveUpdate server logs. This data is used to improve the LiveUpdate service and to create aggregate usage statistics. No personal identifying information is captured. For detailed information, please see the LiveUpdate privacy policy at the following location: ********************************************************************** PROXY SERVER SECURITY CONSIDERATION ********************************************************************** When provided with usernames and passwords, LiveUpdate will store this information in its settings file in encrypted form. However, when this information is sent to a proxy server, it is sent in an encoded, but unencrypted form. It is sometimes possible to capture data packets on the Internet, or on your LAN, and therefore it's possible that your password data may be viewed by others during transmission to the proxy server. If you have any concerns, please contact your network administrator. ********************************************************************** INSTALLING/UNINSTALLING LIVEUPDATE ********************************************************************** All Symantec products that use LiveUpdate include it as part of the product installation.

If you encounter a problem with LiveUpdate that you or Technical Support believe to be the result of an installation problem, or Corrupted files, you can reinstall LiveUpdate. To reinstall LiveUpdate 1. Locate LUSETUP.EXE or LUSETUP-LT.EXE on your computer or on the CD-ROM containing your Symantec product. You may also download the latest version from the Internet at: 2. Double-click LUSETUP.EXE You will be prompted if you wish to install LiveUpdate. 3. Click Yes. The LiveUpdate program will automatically reinstall. If you wish to uninstall LiveUpdate, note that you will no longer be able to receive updates to your Symantec products. To 1. 2. 3. uninstall LiveUpdate: Open the Control Panel. Double-click Add/Remove Programs. Select LiveUpdate from the list, and then click Add/Remove.

********************************************************************** LIVEUPDATE CONFIGURATION & LOG FILES ********************************************************************** LiveUpdate stores all of its configuration and logging information in the following files: log.liveupdate - Log file product.inventory.liveupdate - List of installed Symantec products settings.liveupdate - Configuration settings There is one additional Log File for Automatic LiveUpdate. The Log filename has the following format: <YYYY-MM-DD>_Log.ALUSchedulerSvc.LiveUpdate A new log file is created for each day and the Log filename is prefixed with a date string. If LiveUpdate cannot find its configuration files, it will recreate default versions of the files. In this event, LiveUpdate will also create a file called configuration.log.liveupdate. LiveUpdate will keep backup copies of the product and settings files by adding a number to the beginning of the filename. The higher the number, the older the file. These files are normally located in the Application Data folder on your computer. The location of this folder is Operating System dependent:

Windows Vista <System Drive>:\Program Data\Symantec\LiveUpdate Windows 2000/XP/2003 \Documents & Settings\all users\application data\Symantec\liveupdate or \Windows\profiles\all users\application data\Symantec\liveupdate Some other Windows XP systems \Documents & Settings\all\application data\Symantec\liveupdate If you cannot find this folder, search for one of the filenames noted above. Note: You should not edit any of the files noted above unless directed to do so by Symantec Technical Support. The Log file can grow in size up to a maximum size. When the Log file reaches this maximum size, it is automatically trimmed to 50% of the maximum size. ********************************************************************** USING AOL (America Online) ********************************************************************** Symantec has documentation in the Symantec online knowledgebase that can assist you in using LiveUpdate with America Online. Please go to the following URL to review this information: An important consideration in configuring LiveUpdate to work with AOL is to first make sure you are using a recent version of the AOL software. Note: Symantec is not liable for any phone charges incurred when making this dial up connection. Don't forget to close your Internet connection when you have completed your LiveUpdate session. ********************************************************************** KNOWN ISSUES ********************************************************************** 1. The Automatic LiveUpdate component may be configured to check for virus definition updates in the background. Normally, LiveUpdate will only do this when it detects an open Internet connection. However, some devices, dialup routers for example, can be configured to create an Internet connection when they detect this activity. Users should note that this could result in unexpected connection charges. In addition, automatic LiveUpdate may behave differently with different versions of the AOL connection software. We recommend that you review the "USING AOL" section above. NOTE: ISDN on-demand Internet access and Automatic LiveUpdate.

ISDN charges are generally higher than standard analog phone line charges, so users of these systems are asked to pay particular attention to this issue. 2. On some Windows 2000 systems, the LiveUpdate control panel icon may not work properly. This may be because the LiveUpdate installer was unable to upgrade the old control panel functions. To resolve this problem, try restarting your computer and deleting the file S32LUCP1.DLL from the \windows\system32 folder. Note that the operating system will lock this file if you try to open the control panel before deleting the file. Restarting the computer will unlock the file. When the S32LUCP1.DLL file is removed, the new control panel functions will be available. 3. On 64bit Itanium systems there will be no LiveUpdate Control Panel applet. To access this functionality, you may select the "Show x86 control panel" option from within the control panel on 64bit Windows systems. 4. Some of the help text within the ISP tab in the LiveUpdate control panel may be truncated due to a bug in Microsoft's HTML help. If this occurs, please try applying all the critical and recommended updates which are made available through Microsoft's Windows Update web site. 5. You cannot use the "-temphost" command-line feature to point LiveUpdate at a CD-ROM device. This is due to filename length limitations with the CDFS file system. 6. In Windows XP Professional x64 Edition, the Control Panel Icon is located under the x86 Control Panel. ********************************************************************** RECENT FIXES & UPDATES ********************************************************************** Initial release of LU 2.5 Two issues were addressed in this release. 1. Fixed an issue where we were using the wrong icon on some dialogs. 2. Fixed a problem when Windows LiveUpdate was being used with LiveUpdate Administrator (LUA). In some situations some updates were not being downloaded if the machine that LUA was running on did not meet the download criteria for the updates. LU will now no longer do this evaluation when being run from LUA. 2.6.x Initial release of LU 2.6. 2.7.x Initial release of LU

2.7.38 One Issue addressed in this release. 1. LiveUpdate server login name and password are written to a local log file in clear text. This happens when the LiveUpdate client checks for updates from the server. This is only an issue when a local LiveUpdate server is used with a login name and password. The login name and password belong to the account configured by the LiveUpdate server administrator for accessing LiveUpdate packages. Symantec strongly recommends that this user account be unique for accessing LiveUpdate packages only, and have no other system access. The system administrator account should never be used for this purpose. 3.0.x Initial release of LU 3.0.15x 1. Fixes were made to improve integration compatibility with some Symantec products. 2. Fixed a minor Localization issue in the system eventlog detail level which could be blank, and a hard coded error string. 3. Fixed an internal timing issue for patch installation 3.0.16x 1. Fixed some connectivity issues for users on dial up networking. 3.1.x Initial release of LU 3.2.x Initial release of LU 3.2.x Windows 2000, XP & Vista support only ********************************************************************** Acknowledgements ********************************************************************** LogDriver software COPYRIGHT AND PERMISSION NOTICE Copyright (c) 2002 Will Senn All rights reserved. Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, and/or sell copies of the Software, and to permit persons to

whom the Software is furnished to do so, provided that the above copyright notice(s) and this permission notice appear in all copies of the Software and that both the above copyright notice(s) and this permission notice appear in supporting documentation. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OF THIRD PARTY RIGHTS. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR HOLDERS INCLUDED IN THIS NOTICE BE LIABLE FOR ANY CLAIM, OR ANY SPECIAL INDIRECT OR CONSEQUENTIAL DAMAGES, OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. Except as contained in this notice, the name of a copyright holder shall not be used in advertising or otherwise to promote the sale, use or other dealings in this Software without prior written authorization of the copyright holder. ********************************************************************** END OF FILE **********************************************************************

To top