Cisco FirePOWER ASA 5500 series Configuration Manual page 546

Using Client Update to Ensure Acceptable Client Revision Levels
To perform client update, enter the client-update command in either general configuration mode or
tunnel-group ipsec-attributes configuration mode. If the client is already running a software version on
the list of revision numbers, it does not need to update its software. If the client is not running a software
version on the list, it should update. The following procedure tells how to perform a client-update:
In global configuration mode, enable client update by entering the command:
Step 1
hostname(config)# client-update enable
hostname(config)#
In global configuration mode, specify the parameters for the client update that you want to apply to all
Step 2
clients of a particular type. That is, specify the type of client, the URL or IP address from which to get
the updated image, and the acceptable revision number or numbers for that client. You can specify up to
four revision numbers, separated by commas.
If the user's client revision number matches one of the specified revision numbers, there is no need to
update the client. This command specifies the client-update values for all clients of the specified type
across the entire security appliance
The syntax of the command to do this is:
hostname(config)# client-update type type url url-string rev-nums rev-numbers
hostname(config)#
The available client types are win9X (includes Windows 95, Windows 98 and Windows ME platforms),
winnt (includes Windows NT 4.0, Windows 2000 and Windows XP platforms), windows (Includes all
Windows based platforms), and vpn3002 (VPN 3002 hardware client).
If the client is already running a software version on the list of revision numbers, it does not need to
update its software. If the client is not running a software version on the list, it should update. You can
specify up to three of these client update entries. The keyword windows covers all of the allowable
Windows platforms. If you specify windows, do not specify the individual Windows client types.
For all Windows clients, you must use the protocol http:// or https:// as the prefix for the URL. For the
Note
VPN 3002 hardware client, you must specify protocol tftp:// instead.
The following example configures client update parameters for the remote-access tunnel-group. It
designates the revision number, 4.6.1 and the URL for retrieving the update, which is
https://support/updates:
hostname(config)# client-update type windows url https://support/updates/ rev-nums 4.6.1
hostname(config)#
Alternatively, you can configure client update just for individual tunnel-groups, rather than for all clients
of a particular type. (See Step 3.)
VPN 3002 clients update without user intervention and users receive no notification message. The
following example applies only to VPN 3002 Hardware Clients. Entered in tunnel-group ipsec-attributes
configuration mode, it configures client update parameters for the IPSec remote-access tunnel-group
"salesgrp". It designates the revision number, 4.7 and uses the TFTP protocol for retrieving the updated
software from the site with the IP address 192.168.1.1:
hostname(config)# tunnel-group salesgrp type ipsec-ra
hostname(config)# tunnel-group salesgrp ipsec-attributes
hostname(config-tunnel-ipsec)# client-update type vpn3002 url tftp:192.168.1.1 rev-nums
4.7
hostname(config-tunnel-ipsec)#
Cisco Security Appliance Command Line Configuration Guide
29-4
Chapter 29 Setting General IPSec VPN Parameters
OL-10088-01