System Update Solution Deployment Guide Date: September 2, 2009 A ThinkVantage Technology publication
Maintenance Edition (August 2009) © Copyright Lenovo 2009. LENOVO products, data, computer software, and services have been developed exclusively at private expense and are sold to governmental entities as commercial items as defined by 48 C.F.R. 2.101 with limited and restricted rights to use, reproduction and disclosure.
Contents Preface . . . . . . . . . . . . . . . v Chapter 1. Overview . . . . . . . . . 1 System Update . . . . . Update Retriever . . . . . Managing the update process . System Update . . . . System Update and Update Non-Lenovo . . . . . . . . . . . . . . . . . . Retriever . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 1 1 2 2 4 Chapter 2. Installation . . . . . . . . . 5 Installation requirements . . . . . . . . . . 5 .Net . . . . . . . . . . . . . . . .
Search modes. . . . . . Notification parameters . . Map Drive utility . . . . Command line interface . Using the MapDrv utility . iv . . . . . . . . . . . . . . . . . . . . . . . . . System Update Solution Deployment Guide . . . . . . . . . . . . . . . 77 78 80 81 81 Appendix B. Notices . . . . . . . . . 83 Trademarks . . . . . . . . . . . . . .
Preface This deployment guide is intended for IT administrators or those who are responsible for deploying updates on computers in their organizations. The programs documented in this deployment guide are System Update, Update Retriever, and Thin Installer. System Update is a software program that you can use to help keep your system up-to-date. Update Retriever is an administrative program that you can use to customize the update process for your enterprise.
vi System Update Solution Deployment Guide
Chapter 1. Overview The programs documented in this deployment guide are System Update, Update Retriever and Thin Installer. This deployment guide explains the update process, defines each program, and how each program can be configured to fit your needs. In this deployment guide, you also will find installation procedures, application configurations, and best practices on how to use these programs in different environments.
System Update The following illustration shows the communication path of update packages from the Lenovo Help Center to a client system when using only System Update: Internet Lenovo Help Center System Update Client system Figure 1. Update process using System Update only System Update and Update Retriever For multiple systems, you can use Update Retriever on an administrative system to download packages from the Lenovo Help Center to your network.
Figure 3. Using Update Retriever on a local network For more information on configuring repository locations for package storage, see Chapter 3, “Configurations,” on page 13. Deploying updates/packages to client systems Instead of using a network share on a LAN, you can use a local system such as the administrator system for package storage. Once you have created a repository folder, you can then push the folder to client systems.
Update Retriever to edit an existing package or create a new package in the repository folder. Update Retriever uses an XML Descriptor file to define when an update package is relevant and how to install the update package. For example, you can create an XML Descriptor file that enables a specific update to be downloaded and installed on a client system depending on the version of the software already installed or existing hardware devices found on the system.
Chapter 2. Installation This chapter provides you with installation instructions for System Update and Update Retriever. This chapter will also provide you with installation requirements, components and considerations. You can download System Update and Update Retriever from the following Web site: http://www.lenovo.com/support/site.wss/document.do?lndocid=TVAN-ADMIN#tvsu For information on installing Thin Installer, go to “Downloading Thin Installer” on page 53.
v v v v v Windows Windows Windows Windows Windows Server Server Server Server Server 2008 2008 2008 2008 2008 Standard (32-bit and 64-bit) Standard without Hyper-V (32-bit and 64-bit) Enterprise (32-bit and 64-bit) Enterprise without Hyper-V (32-bit and 64-bit) DataCenter (32-bit and 64-bit) v Windows Server 2008 DataCenter without Hyper-V (32-bit and 64-bit) v Windows Web Server 2008 (32-bit and 64-bit) .Net System Update and Update Retriever require Microsoft.NET Framework 1.
HKEY_LOCAL_MACHINE\SOFTWARE\Lenovo\System Update\LanguageOverride If the LanguageOverride is empty, has an invalid value or the NLS language pack specified in the LanguageOverride field is not installed on the computer, then System Update gets the language code from the operating system regional settings. If System Update successfully loads the regional settings language, then that is the language System Update displays for the rest of the session.
When installing, a shortcut is added to the following Start menu folder for ThinkPad® systems: Start Menu\Programs\ThinkVantage For Lenovo systems, the following shortcut is added to the Start menu folder: Start Menu\Programs\Lenovo Care Preferences are stored as settings in the following Windows registry keys: v For System Update: HKLM\Software\Lenovo\System Update v For Update Retriever: HKLM\Software\Lenovo\Update Retriever The default folder where application files are installed is the following: v
Windows Vista considerations With considerations for Windows Vista, the System Update silent installation launches a User Account Control (UAC) message. You can find information on disabling and enabling the User Account Control message on the following Web site: http://technet2.microsoft.com/WindowsVista/en/library /0d75f774-8514-4c9e-ac08-4c21f5c6c2d91033.mspx?mfr=true Note: If the UAC is active, a silent uninstall will not work with Windows Vista.
Table 4. List of parameters with -a (continued) Parameter Description Example /w This parameter forces the executable defined in the installation file to execute after the extraction and to wait until the installation is complete before exiting. [System Update installation file name].
The uninstall command for System Update is: MsiExec.exe /X{8675339C-128C-44DD-83BF-0A5D6ABD8297} /qn The uninstall command for Update Retriever is: MsiExec.exe /X{F25C538D-3F57-4AF4-80DD-B1DD1558F038} /qn Silent uninstall for Windows Vista To silently uninstall System Update that has been installed on the Windows Vista operating system, complete the following steps: 1. From the desktop main menu, click Start and then navigate to the Control Panel. 2. Click User Accounts. 3.
12 System Update Solution Deployment Guide
Chapter 3. Configurations This chapter provides you with conceptual information and procedures to configure connectivity settings, repository locations and the user interface. Connection configurations System Update and Update Retriever support three types of connectivity configuration: direct connection, static proxy connection, and auto-configuration script. v Direct connection This type of configuration is used when no proxy is required to connect to the Internet.
Configuring System Update Configurations for System Update can be done through the registry, Active Directory®, or the start.reg file. If you are configuring just one system, you can use the registry to configure System Update. If you are configuring multiple systems, you can use Active Directory to configure policies for System Update. If your enterprise does not use Active Directory, Lenovo provides the start.reg file that you can configure and then deploy to multiple systems.
Table 5. Registry locations (continued) Setting Registry location DisplayLicenseNotice, see “User HKLM\SOFTWARE\Lenovo\System Settings\General configurations” on page 18. Update\Preferences\UserSettings\General DisplayLicenseNoticeSU, see “User HKLM\SOFTWARE\Lenovo\System Settings\General configurations” on page 18. Update\Preferences\UserSettings\General ExtrasTab, see “User Settings\General configurations” on page 18.
Table 6. UC Settings\General Configurable item Description Value Billboard\LiveFeed You can use this setting to disable the live feed to the System Update billboard. Default: Lenovo Live v Default - Displays Feed the live feed image on the System Update user Possible values: interface. v Default - Lenovo v Blank - Displays the Live Feed default billboard v Blank - disables image on the System this function. Update user interface. General\Disable Disables the System Update user interface.
Table 7. \UC Settings\HTTPSHelloSettings (continued) Configurable item Description Value Action ServerName This setting will disable the System Update application upgrade function (Update Thyself). The default value is pre-configured to connect to the Lenovo Help Center Web site. System Update checks the Lenovo Help Center Web site for updates for itself, even if it is connecting to a local system or network share repository. You can disable the Web upgrade for System Update by clearing this value.
Note: The RetryLimit and RetryWaitTime for the HTTPSPackageSettings are values that control the connection between System Update and the server used to search for update packages. Proxy server configurations The following table and example provides the configurable items for the proxy server connections: Table 9. User Settings\Connection Configurable item User Password Description Value Action The user name to use for the connection.
Table 10. User Settings\General Configurable item Description Value Action ContentMode Specifies which update packages System Update will search for. Default value: Active v If Active, System Update will search the Update Retriever repository for the update packages in active status. v If Test, System Update will search the Update Retriever repository for the update packages in test status. Possible values: v Active v Test Note: If there is no database.
Table 10. User Settings\General (continued) Configurable item Description Value DisplayLicenseNoticeSU Default value: YES Enables you to skip the license notice that is displayed on the Schedule Updates panel of System Update. Possible values: v YES v NO ExtrasTab Will show or hide the Extras tab on System Update.
Table 10. User Settings\General (continued) Configurable item Description Value Action IgnoreRMLicCRCSize Use this setting to enable or disable the following functions when System Update downloads packages from the Lenovo Help Center Web site: Default value: YES v Set the value to YES and System Update ignores these files and does not check for size or corruption. v v Set the value to NO and System Update checks for file size and corruption.
Table 10. User Settings\General (continued) Configurable item Description Value Action RepositoryLocation1 Use this setting to indicate the repository folder path. The key value name should be “Repository Location%N%”, where %N% is a number between (include) 1 and 20. Default value: SUPPORTCENTER System Update will search for update packages in the folder specified in this value.
Table 11. User Settings\Scheduler Configurable item Description Value Action SchedulerAbility The setting of this property value determines if the Scheduler is activated to automatically run or not. Default value: YES If YES, the Scheduler will run based on the settings. If NO, the Scheduler will not run. SchedulerLock Default value: SHOW The setting of this property determines if the Schedule Updates item is visible to you or not.
Table 11. User Settings\Scheduler (continued) Configurable item Description Value Action Note: If you use ’Recommended’ in the search mode, ’NOTIFY’ is the only option available. All other settings will stop the execution of System Update. If the setting is NOTIFY the scheduler will search for new updates and notify the end user when new updates are available for download and installation. Note: For DOWNLOADANDINSTALL, ensure no spaces separate the value.
Note: To edit registry configurations, close the System Update application. If System Update is running while changes are made in the registry, the old registry entries will be recovered. Repository configurations The default for System Update is to obtain update packages from the Lenovo Help Center Web site. You can change the setting to enable System Update to search and download update packages from a local system repository folder or a network share repository folder individually.
3. Set the access permissions of the new repository folder to read only access for end users. Administrator functions will require read and write access. 4. On client systems, navigate to the following registry entry: HKLM\SOFTWARE\Lenovo\System Update\Preferences\ UserSettings\General\RepositoryLocation1 The default for this registry entry is SUPPORTCENTER. This default setting enables System Update to search for update packages on the Lenovo Help Center Web site.
v RepositoryLocation1 - Lenovo Help Center Web site v RepositoryLocation2 - Local system v RepositoryLocation3 - Network share Creating and configuring multiple repositories with the registry: To create and configure multiple repository locations, complete the following steps: 1. Create a new folder on a local hard disk drive to be used as the repository, for example: %ANYDRV%\SystemUpdate3_x\ 2. Create a new folder on a network share to be used as the repository. 3.
If you want to control the version of System Update available to your users, you can use your network repository to store specific versions of System Update. Storing packages locally will enable the System Update application to search for upgrades within your network repository. This version control function is compatible with System Update 3.02 and future releases. To configure the registry for System Update version control, complete the following steps: 1. Download SSClientCommon.
Administrative (ADM) template files The ADM (Administrative) template file defines policy settings used by applications on the client computers. Policies are specific settings that govern the application behavior. Policy settings also define whether the end user will be allowed to set specific settings through the application. Settings defined by an administrator on the server are defined as policies. Settings defined by a end user on the client computer for an application are defined as preferences.
HKLM\Software\Lenovo\Update Retriever Group Policy settings The following tables provide policy settings for the Computer Configuration for System Update. User Settings: This table provides policies for the user settings of System Update: Table 12. Computer Configuration>Administrative Templates>ThinkVantage>System Update>User Settings Policy Setting ContentMode Active Note: If there is no database.
Table 12. Computer Configuration>Administrative Templates>ThinkVantage>System Update>User Settings (continued) Policy Setting Description General Repository Location This setting determines where update packages will be downloaded and installed from. The default setting is SUPPORTCENTER and enable System Update to download updates from the Lenovo Help Center.
Table 12. Computer Configuration>Administrative Templates>ThinkVantage>System Update>User Settings (continued) Policy Scheduler Setting Description NotifyInterval If this value is set at the default of 300 seconds, then you are prompted with a restart notification every 300 seconds when you begin to download and install a package that forces a reboot and defer the download and installation process. System Update uses the default value when invalid settings are used.
Table 12. Computer Configuration>Administrative Templates>ThinkVantage>System Update>User Settings (continued) Policy Setting Description Mapped Network Drive UNC UNC location for the mapped network drive (format \\server\share). Default: none User Use the mapdrv.exe /view command to create an encrypted value for this field. Default: none. Password Use mapdrv.exe /view command to create an encrypted value for this field.
Managing network share repositories with Active Directory® This section provides a description of the policy settings for the network share repository. Setting these policies will prompt an end user for a user name and password when the System Update end user interface is launched or when a scheduled update occurs.
Setting policies for multiple repositories: Use the following example to set the policies in Group Policy when using multiple repositories: 1. After adding the Administrative Template for System Update, navigate Group Policy Object Editor to the following location: Computer Configuration\Administrative Templates\ThinkVantage \System Update\User Settings\General\Repository Location 2. Double-click Repository Location. 3.
For organizations that do not have Active Directory, System Update can be configured through the registry using the start.reg file. Complete the following steps to change the repository locations in the registry: 1. Download the full version of System Update and the start.reg file from the following Lenovo Web site: http://www.lenovo.com/support/site.wss/document.do?lndocid=TVAN-ADMIN#tvsu 2. Update RepositoryLocation1 in the start.reg file.
Attention: The start.reg file will be deleted after the first execution of System Update. To make the start.reg settings the default settings that are restored in the event the registry settings ever get corrupted, rename the start.reg file to default.reg and save it into the following path: c:\Program Files\Lenovo\System Update\default Configuring multiple repository locations using the start.reg file The following example provides the start.
[HKEY_LOCAL_MACHINE\SOFTWARE\Lenovo\System Update \Preferences\UCSettings\HTTPSHelloSettings] "RetryLimit"="0" "RetryWaitTime"="0" "ServerName"="\\\\Server_X\\TVSU_repository\\" "BlockSize"="4096" "Domains"=hex(7):2e,00,6c,00,65,00,6e,00,6f,00,76,00,6f,00,2e,00,63,00,6f,00,\ 6d,00,00,00,2e,00,69,00,62,00,6d,00,2e,00,63,00,6f,00,6d,00,00,00,00,00 Note: To set your repository path in the registry using the start.reg file, backslash \ characters in the directory’s path should be preceded by another backslash.
Chapter 4. Working with System Update This chapter provides information on working with update packages, using the System Update program, and the Web upgrade for System Update. About System Update When you search for updates using System Update, the request goes to a repository or the Lenovo Help Center (depending on how System Update is configured). In response, System Update provides a list of new candidate updates.
Working with update packages An update package is made by bundling several files together. Updates packages consist of a self-extracting installer program, an XML Descriptor file that defines the update, and one or more NLS translated readme files. An update may also optionally include one or more NLS translated license files and one or more external detection files. Applicable update packages must match the triplet on the client system.
Note: The user name and password properties can be managed by Active Directory. Since the user name and password must be encrypted when used as an application property, an administrator can use a Lenovo supplied utility called MapDrv to generate encrypted strings for the user name and password using a software key. For additional information about the MapDrv utility, see “Map Drive utility” on page 80.
– A video driver that corrects an issue that may cause blue screen. – BIOS update that contains minor fixes that may impact a small set of customers. – A power management driver that will allow a mobile system to get the most out of its battery life. v Optional packages will improve your computing experience, but are not necessary. Examples of optional packages: – A tool that enables you to migrate files from one system to another such as ThinkVantage® Rescue and Recovery® .
v Notification: You can choose to be notified when new updates are found and have the choice to either download the update or defer the download until another time. For critical updates only, additional options are available to automatically download or download and install all new updates and get notified after downloading or installation is complete.
Table 15.
Chapter 5. Working with Update Retriever This chapter provides information about setting up, upgrading, and using Update Retriever. About Update Retriever Update Retriever enables you to download update packages from the Lenovo Help Center Web site to a network share repository folder. Your repository folder provides the storage for update packages. Once configured, System Update can search your repository for update packages. This allows greater control of the updates that are available over your network.
Attention: If you find duplicate update packages in the network share repository, these packages have different package contents. Select all packages with corresponding names for a given machine type when you are managing the contents of the network share repository. Note: If you install Update Retriever on a notebook computer running Microsoft Vista in one country and download packages when in another country, the license files with that package may not display correctly.
Table 16. The status of updates Option Possible Value Default Value Severity v Default Default v Critical v Recommended v Optional License v Default Default v Display v No display Status v Test Test v Active v Repositories You can customize the location of the repository folder. If a network share is specified (using the Universal Naming Convention), you can provide a user name and password to authenticate without requiring a prompt when making the actual connection.
Show updates in a repository You can view updates in the repository by choosing Manage repository and then selecting Update view. You can view updates in the repository by filtering by operating system, language, machine type, severity, and status. In the Update view, you can sort the list of updates by update ID, title, version, reboot type, severity, license, or status. You can select one or more packages and modify or delete them. You can also select non-Lenovo packages and modify the triplets.
10. From the Update view panel, click the drop down menu for Operating System File. 11. Change the setting to Unassigned. This gives you a list of unassigned triplets. 12. Select the check box for the update package and click Assign Systems. 13. Select the check box or for the applicable triplets or select the Select all check box. 14. Click Save. Note: Each update must be in its own sub folder. If you are importing one update, specify the folder that contains that update.
The following list provides the metadata of an update package that you can customize using Update Retriever: v Package identity – Name – Version – Vendor – Software release date – Disk space needed to install the package – Title, description, summary, and language for a package – Version detection – Target applications v Installation detection – Add remove programs – BIOS – BIOS date – CPU address width – – – – – Driver Embedded controller version External detection File date File exists – File version –
– Manual installation details – Uninstall details v Define the files that make up the update package: – Installer file – External file – Readme file – License file and other system specific files Creating an update package You can create an update package by choosing Manage repository, selecting Update view, and then clicking Create an update.
Keyboard shortcuts The following table provides the keyboard shortcuts for the main functions of Update Retriever: Table 17.
Chapter 6. Working with Thin Installer This chapter provides information about using theThin Installer program, the download instructions, and how this program can be configured to fit your needs. About Thin Installer Thin Installer is a smaller version of System Update, which is used as a standalone installation utility that runs without an installation process. Thin Installer searches for the update packages from a repository that you create.
Using Thin Installer This section provides information about using Thin Installer. There are two modes to run Thin Installer: v GUI mode – If you execute the Thininstaller.exe file directly, Thin Installer searches for the update packages from the default repository in the folder where the Thin Installer package files are unpacked. Figure 6. Default repository – If you execute the Thininstaller.
Table 18. Command line scripts (continued) Scripts Description %ANYPATH%\Thininstaller.exe /CM –search A –action INSTALL -noicon Installs all critical, recommended, and optional packages which have no reboot requirement and suppresses the balloon message after the installation has completed. %ANYPATH%\Thininstaller.
Table 18. Command line scripts (continued) Scripts Description %ANYPATH%\ThinInstaller.exe /CM –search C –action INSTALL –repository C:\MyRepository –log "C:\MyLogFolder\MyLogFile.txt" Searches a repository for critical update packages and installs those that do not contain a license agreement. You are asked to agree to a license notice before the update packages pick list is displayed if you have not set the configurable item DisplayLicenseNotice to NO.
Table 19. How to create a log file Running mode Has a writable access to current directory Description of log file GUI mode: execute ThinInstaller.exe directly. YES Log file name: Update_log_YYMMDDHHMMSS.txt Path: Current directory\logs\ GUI mode: execute ThinInstaller.exe directly. NO No log file. GUI mode: A log file is specified as one of the parameters. Example: ThinInstaller.exe /repository "c:\local" -log "c:\temp\logdir\tvsulog.txt" YES or NO Log file name: tvsulog.
Return codes Thin Installer returns codes in both the GUI and command line modes. If one of the following errors occur when using Thin Installer, Thin Installer returns code 1. Otherwise, Thin Installer returns code 0. v v v v v The XML schema validation fails for the update package. The CRC validation fails for the executable file of the update package. The update package installation fails. Thin Installer itself fails. The specified repository is not found.
The following table shows the configurable items in the XML file for Thin Installer: Table 20. Description of configurable items Configurable item Description Value Action LanguageOverride Specifies the language to be used. Default value: EN Changes the language to the Possible values: one specified. v DA v NL v EN v FI v FR v DE v IT v JP v KO v NO v PT v ES v SV v CHS v CHT BlockSize Specifies the number of Default value: bytes to be read each time 4096 data is downloaded.
Table 20. Description of configurable items (continued) Configurable item Description Value IgnoreLocalLicense Shows or hides the license Default value: dialog when Thin Installer YES is downloading and installing an update package. Possible values: v YES v NO IgnoreRMLicCRCSize Use this setting to enable or disable the following functions when Thin Installer downloads packages: v CRC - checks for the file corruption of readme and license agreements files when you download packages.
Table 20. Description of configurable items (continued) Configurable item Description Value Action ContentMode Specifies which update packages Thin Installer will search for. Default value: Active v If Active, Thin Installer will search the Update Retriever repository for the update packages in active status. Possible values: v Active v Test v If Test, Thin Installer will search the Update Retriever repository for the update packages in test status. Note: If there is no database.
62 System Update Solution Deployment Guide
Chapter 7. Best practices This chapter provides step-oriented scenarios to help you understand the update process.
Note: After you install Update Retriever, restart your system to set the Scheduler function. If you are not using the Scheduler function of Update Retriever, a restart is not needed. 6. Download System Update from the following Lenovo Web site: http://www.lenovo.com/support/site.wss/document.do?lndocid=TVAN-ADMIN#tvsu 7. Install System Update silently by entering the following command at the command prompt: setup.
Scenario 2 - Deploying specific packages For enterprises that choose to deploy specific packages to client systems, you can configure System Update, Update Retriever, and repository folders to deploy only the packages that you have selected. The following step-by-step instructions provides you with procedures to create repository folders, configure System Update and work with Update Retriever to deploy specific packages.
a. Type the applicable machine type. You can find the machine type on the bottom of a laptop or on the rear of a desktop machine. b. Select the applicable operating system from the drop down menu. c. Select the applicable language from the drop down menu. d. Click Add and then click Save. 5. On the Get New Updates panel, select the check box for the applicable machine type. To import all machine type packages, select the check box Select all. 6.
7. Create a packages for the non-Lenovo systems using Update Retriever. 8. 9. 10. 11. Note: Add the Supported Systems method in the dependencies section of the XML descriptor file to apply the updates to a particular model. Save the XML descriptor. Import the packages to the Update Retriever managed repository. Do this by specifying the path where the package are located and then click Next. Verify the packages are available for import and then click Import.
tvsu.exe /package "C:\installtxt\ installList.txt" 7. Press Enter. Scenario 6 - Deploying packages to client system repositories An alternate to using a network shared drive repository, is to deploy packages to client system repositories. Complete the following steps to deploy packages to client system repositories: Step 1 - Administrator system setup Complete the following steps to set up your administrative system: 1.
Scenario 8 - Working with Thin Installer Thin Installer always first checks for the database.xml file in the repository folder. If you have created a repository using Update Retriever, the database.xml file is created in the same folder. The Database.xml file associates each Machine Type, Operating System and Language with the Update packages. In the absence of the database.xml file in the repository, Thin Installer assumes all update packages in the repository are candidate packages.
Integrating Thin Installer with ImageUltra Builder (IUB) This is the ideal way to deploy common drivers and applications during an image rollout. The system administrator maintains one central repository and one image for different types of systems. To learn more about ImageUltra Builder, go to the following Web site: http://www.lenovo.com/support/site.wss/document.do?lndocid=MIGR-61432#image 1. Create a network shared repository and install Thin Installer.
Appendix A. Command line parameters This chapter provides information about command line parameters, search modes, notification parameters, and the Map Drive utility. Automatic search This function will perform an automatic search for new updates from a repository folder or the Lenovo Help Center. Table 21. RepositoryLocation and Command line RepositoryLocation registry entry Command line Repository searched RepositoryLocation Where %N% is a number between 1 and 20.
Table 22. Command line scripts (continued) 72 Scripts: Description: %PROGRAMFILES%\Lenovo\System Update\Tvsu.exe /CM -search C -action INSTALL Searches the repository for critical updates and installs those that do not contain a license agreement. You are asked to agree to a license notice before the download occurs if you have not previously asked for the license notice to not be shown in the future. You are notified by a system tray balloon after the updates have been installed.
Table 22. Command line scripts (continued) Scripts: Description: %PROGRAMFILES%\Lenovo\System Update\Tvsu.exe /CM -search C -action INSTALL -noicon Installs all critical packages which have no reboot requirement and suppresses the balloon message after the installation has completed. %PROGRAMFILES%\Lenovo\System Update\Tvsu.
Table 23. Command line scripts 74 Scripts: Description: %PROGRAMFILES%\Lenovo\System Update\Tvsu.exe /CM -search C -action LIST -repository C:\MyRepository Searches a repository for critical updates and notifies you with a system tray balloon prior to downloading and installing. %PROGRAMFILES%\Lenovo\System Update\Tvsu.exe /CM -search C -action DOWNLOAD -repository C:\MyRepository Searches a repository for critical updates and downloads those that do not contain a license agreement.
Table 23. Command line scripts (continued) Scripts: Description: %PROGRAMFILES%\Lenovo\System Update\Tvsu.exe /CM -search A -action INSTALL -repository C:\MyRepository Searches a repository for critical, recommended, and optional updates and installs those that do not contain a license agreement and a reboot requirement. If you have not marked the check to disable the license notice dialog box, you are prompted to agree to a license notice before the download occurs.
Table 23. Command line scripts (continued) 76 Scripts: Description: %PROGRAMFILES%\Lenovo\System Update\Tvsu.exe /CM -search R -action INSTALL -repository C:\MyRepository -noicon -includerebootpackages 1,3,4 Searches a repository for critical and recommended update packages, and then installs packages with specified reboot types that do not contain a license agreement.
When System Update is performing an automatic search through a proxy server with authentication and no user name or password have been saved, no dialogs will be displayed to the end user. An error will be logged to the System Update logging file and System Update is shutdown. If the user name and password have been saved, System Update will try to connect using the saved user name and password information.
Notification parameters The notification parameter used on the command line specifies the way System Update handles update packages and then notifies you when packages have been processed. The following table provides the parameters and descriptions for each: Table 25. Notification parameter 78 Parameter Description -action LIST Enables System Update to notify you with a system tray balloon when update packages are available on the Lenovo Help Center Web site.
Table 25. Notification parameter (continued) Parameter Description -SCHEDULER Enables System Update to run from the Scheduler function. This parameter is a registry entry that has to be updated in the registry and not on the user interface. -repository If you use a repository folder to store update packages, you must specify the folder's path. To specify the folder's path, use this parameter and System Update will search for update packages stored in the folder you specified.
The following list provides a description of the search mode and notification methods used: v -search A - enables System Update to search for critical, recommended and optional packages. v -action INSTALL - installs the packages. v -IncludeRebootPackages 1,3,4 - enables System Update to download and install packages that require a reboot. Notes: 1. If you do not include -IncludeRebootPackages 1,3,4; System Update will not detect packages that require a reboot. 2.
Table 26. The MapDrv settings and values (continued) Value Description NetPath Value output from the MapDrv utility to indicate the actual connection path (may be IP dotted format if the nameserver is not working). The actual connection path may not be the same as the stored UNC value. The MapDrv utility also enables an administrator to use the encryption engine to generate an encrypted user name and password, which can be used to pre-populate network share information on multiple systems.
app id: TVSUAPPLICATION user: temp pwd: password This command captures the encrypted user name and password to setup the repository with UNC path with authentication. Storing network share information for a TVT This function stores the network share information in the registry using the to define the subkey from the main MapDrv registry key: mapdrv /store /unc /user /pwd [/timeout ] This sets the UNC, user name and password values in the registry.
Appendix B. Notices Lenovo may not offer the products, services, or features discussed in this document in all countries. Consult your local Lenovo representative for information on the products and services currently available in your area. Any reference to an Lenovo product, program, or service is not intended to state or imply that only that Lenovo product, program, or service may be used.
Any performance data contained herein was determined in a controlled environment. Therefore, the result in other operating environments may vary significantly. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurements may have been estimated through extrapolation. Actual results may vary.
Printed in USA
