aXsGUARD Identifier 3.0.2.0 Product Guide v1.5
Updating
7
Updating
7.1
Overview
VASCO are constantly improving their products, to solve problems or to address new needs. These improvements
are distributed to the aXsGUARD Identifier through the updating process. Updating is included in the aXsGUARD
Identifier maintenance contracts.
Updating is managed through the aXsGUARD Identifier Configuration Tool (see section
Interfaces). The updating process and supporting infrastructure are described in the following sections.
For further instructions on the updating procedure, please refer to the
aXsGUARD Identifier Installation Guide
,
delivered with the aXsGUARD Identifier and also available through the
Help
button in the Configuration Tool.
7.2
Updating Process
Updating is supported by an Update Wizard in the aXsGUARD Identifier Configuration Tool and can be:
off-line using an update file. Please visit
on-line, through a connection to the VASCO Service Center. An available update can be downloaded during the
Update Wizard.
On completion of the Update Wizard for an on- or off-line update, the aXsGUARD Identifier automatically reboots.
During reboot, services are temporarily unavailable. After reboot, the system administrator needs to log back into
the Confguration Tool. Feedback on the update is presented on the
Status
screen
A
fail-over
system reverts the aXsGUARD Identifier to the previous operational version if there is a power failure
during updating.
For instructions on how to use the Update Wizard, please refer to the
aXsGUARD Identifier Installation Guide
,
accessible through the
Help
button in the Configuration Tool.
7.3
Updating Infrastructure
The VASCO Service Center server handles registration, updating and remote support for the aXsGUARD Identifier.
On-line updating described above requires an https secure connection between the aXsGUARD Identifier and the
VASCO Service Center. Connection to the VASCO Service Center is explained in section
For off-line updating, please visit
for more information.
Note:
Updating is only possible after an aXsGUARD Identifier has been registered. This means that if an unregistered
appliance has been stored for a while and is no longer configured with the most up to date software, it must first
be registered before the software can be updated.
©
2009 VASCO Data Security
65