To successfully distribute a Windows LiveUpdate configuration, you must have specified the target computers and organizational units when you created or modified the Windows LiveUpdate configuration.
When you distribute a configuration, a message is sent to the computers that are associated with the Windows LiveUpdate configuration, which instructs them to contact the SESA Manager for a new configuration.
To distribute a Windows LiveUpdate configuration
1
In the Symantec management console, on the Configurations view tab, in the left pane, expand the top-level SESA domain, and then expand LiveUpdate1.0 > Windows LiveUpdate.
2
Under Windows LiveUpdate, right-click a configuration, and then clickDistribute.
3
When you are prompted to distribute the configuration, click Yes.About Java LiveUpdate client configurations
In SESA, Java LiveUpdate client configurations are divided into the following groups of settings:
■ General ■ Java LiveUpdate ■ Hosts
■ Java LiveUpdate 3.0 Settings ■ Custom Content
Java LiveUpdate installs with a default configuration, as specified in the LiveUpdate.conf configuration file. However, you may want to modify a configuration or distribute additional configurations to Java LiveUpdate client computers.
You can use the Symantec management console to create and distribute additional LiveUpdate configurations to one or more computers on which Java LiveUpdate is installed. In addition, SESA provides a Default Java LiveUpdate configuration, which you can also configure for distribution to Java LiveUpdate computers. When you create or modify a Java LiveUpdate configuration, you must specify the Java LiveUpdate computers to associate with the configuration. You must also specify the SESA organizational unit to which the computer or computers belong. Managing LiveUpdate clients with SESA
About Java LiveUpdate client configurations
As an option, you can specify any configuration groups to which the computer or computers belong.
Java LiveUpdate configurations let you specify network proxy server settings that may be required for Java LiveUpdate sessions in your network environment. You can also specify additional LiveUpdate HTTP or FTP servers to use for downloading product updates. In addition, you can create a LiveUpdate configuration to specify that certain LiveUpdate computers use a LiveUpdate configuration file other than the default one. Similarly, you can specify that certain LiveUpdate computers use an internal LiveUpdate Administration host server. Java LiveUpdate configurations also let you specify the maximum size of LiveUpdate log files.
To create a new Java LiveUpdate configuration, you use the Create a new Configuration wizard. After the configuration is created, you can make additional changes by selecting Properties. You can also configure the Default Java
LiveUpdate configuration.
See“Working with Java LiveUpdate configurations”on page 84. See“Distributing a Java LiveUpdate configuration”on page 88.
General settings
The General tab displays the name and description of the selected Java LiveUpdate configuration. A Java LiveUpdate configuration is a collection of settings that you can apply to products on computers directly, or by setting up configuration groups or organizational units.
By default, SESA uses the Default Java LiveUpdate configuration. The General tab contains the following options:
The name of the configuration. You cannot modify this name after you create it.
Configuration name
The configuration description. You cannot change the description of the Default configuration.
Description
The date that is set automatically when you change a configuration. You cannot change the date manually. Last modified on
Java LiveUpdate settings
Only one set of the Java LiveUpdate settings may be included in a single LiveUpdate configuration.
79 Managing LiveUpdate clients with SESA
Note:Java LiveUpdate does not accept user names and passwords for any protocol other than FTP.
You can define the Java LiveUpdate settings that are listed in Table 5-4. Table 5-4 Java LiveUpdate settings
Description LiveUpdate setting
SESA property name
Specifies a proxy server address. The address must be the TCP/IP address of the server. This setting is not supported for FTP.
proxy ProxyServer
Specifies the port on which the proxy server is listening (optional). If a port number is not specified, it defaults to 80. The address must be either the TCP/IP address or the FQDN (fully qualified domain name) of the proxy server, and the port must be the TCP/IP port that the proxy server is listening on. This setting is not supported for FTP. proxy
ProxyServerPort
Specifies a user name to use when logging on to the specified proxy server. This setting is required only if the proxy server requires a logon user name. This setting is not supported for FTP.
proxyusername ProxyUsername
Specifies the password that is associated with the specified proxyusername account. This setting is required only if your proxy server requires a logon password. This setting is not supported for FTP.
proxypassword ProxyPassword
Specifies whether overrides are allowed. Value is either True or False. The default is False. If set to anything other than True, JavaLiveUpdate ignores the -c command-line switch and host file setting. If the setting is not present or set to True, Java LiveUpdate honors the -c command-line switch and host file setting.
AllowConfiguration Override
AllowConfigSwapping
Specifies the maximum allowed log file size in kilobytes (KB). Java LiveUpdate discards older log entries once the log file exceeds the specified maximum size. The minimum allowable log file size is 512 KB. The default log file size is 1024 KB.
MaximumLogFileSize MaxLogFileSize