Upgrade Firmware in WatchGuard Cloud
Applies To: , ,
Some of the features described in this topic are only available to participants in the WatchGuard Cloud Beta program. If a feature described in this topic is not available in your version of WatchGuard Cloud, it is a beta-only feature.
You can upgrade firmware for a device in WatchGuard Cloud. Service Providers can upgrade the firmware for any account they manage. You can upgrade the firmware immediately or schedule the upgrade for a future time.
If an auto-backup is not available or appropriate, you can also manually Downgrade Firmware on a Cloud-Managed Device.
Upgrade Device Firmware in WatchGuard Cloud
For locally-managed Fireboxes only, the Firebox automatically creates a backup when firmware is upgraded from WatchGuard Cloud. For information on how to create a backup image manually, see Manage Firebox Backup Images in WatchGuard Cloud.
An individual Firebox must run Fireware v12.5.2 or higher to be able to update the firmware from WatchGuard Cloud. To upgrade a FireCluster in WatchGuard Cloud, cluster members must run Fireware v12.7.1 or higher (or v12.5.8 or higher for T10, T15, T30, T35, T50, M200, and M300 Fireboxes).
To see and manage firmware upgrades:
Sign in to your WatchGuard Cloud account.
For Service Provider operators, select Overview or a child Service Provider account. Select Configure > Devices.
Select Firmware Upgrades.
Firmware Upgrades page for Subscriber account
Firmware Upgrades page for Service Provider account
The Firmware Upgrades Overview section shows the total number of devices with each of these upgrade statuses:
Devices ready to upgrade now — Devices that are online, with an upgrade available
— Devices that are online, with an upgrade available Devices scheduled to upgrade — Devices that have an upgrade scheduled
— Devices that have an upgrade scheduled Devices pending upgrade — Devices that have an upgrade in progress
— Devices that have an upgrade in progress Devices failed to upgrade — Devices that failed to upgrade
The number of devices available for upgrade also shows on the Monitor > Devices > Device Summary page when you select the top-level folder.
To filter the device list on this page, click a tile, select the type of device, or select the view filter from the drop-down list above the device list.
To upgrade firmware for one or more devices:
In the Firmware Upgrades window, click Upgrade Firmware.
The Upgrade Firmware wizard opens. You can also click the Upgrade icon in the Firmware Version column to open the wizard. If available, select the device type, such as Firebox or Access Point. Click Next. From the Firmware Version drop-down list, select the firmware version to upgrade to. The three most recently released versions of firmware appear in the list. This list can include beta releases. For information on how to enable beta releases, see Enable Beta Features and Applications.
Click Next.
The Select Devices page opens .
From the list of devices, select the devices to upgrade. Click Next.
The Schedule Upgrade page opens.
Select when to upgrade the firmware: To upgrade selected devices now, select Upgrade now . This option is available only if all selected devices are connected to WatchGuard Cloud.
. This option is available only if all selected devices are connected to WatchGuard Cloud. To schedule the upgrade for a later time, select Schedule upgrade . Specify the Start Date , Start Time , and Time Zone when the upgrade will occur.
. Specify the , , and when the upgrade will occur. Select the Adjust for daylight saving time check box to automatically adjust the time during daylight savings. The default time zone for a scheduled upgrade is based on the time zone of the web browser. Make sure that the selected upgrade time and time zone correspond to the local time you want to upgrade each selected device. Click Next. Confirm the upgrade details. Click Update.
To cancel a scheduled upgrade:
Sign in to your WatchGuard Cloud account.
For Service Provider operators, select Overview or a child Service Provider account. Select Configure > Firmware Upgrades. In the table, click in the row for the device upgrade you want to cancel.
Select Delete Scheduled Upgrade. Click Delete.
Downgrade Firmware on a Cloud-Managed Device
If necessary, you can downgrade the firmware on your cloud-managed device to an older version.
Downgrade Access Points
For access points, you can select an available lower version of the current firmware to which to downgrade during the firmware update process.
Downgrade a Firebox
We recommend that for a Firebox you restore an auto-backup. For more information, see Manage Firebox Backup Images in WatchGuard Cloud.
If an auto-backup is not available or appropriate, you can manually downgrade your cloud-managed device. To do this, you first remove the device from WatchGuard Cloud and then add it back. This ensures that when the device reboots, if it has DHCP, it automatically connects to WatchGuard Cloud as a cloud-managed device.
You must also have access to the sysa-dl file for the Fireware version you want to downgrade to. For more information, see Download an Upgrade File.
When you downgrade the firmware, the device defaults. The Firebox automatically downloads a default configuration file. You can then restore a specific, previously deployed configuration in WatchGuard Cloud. For more information, see Manage Firebox Backup Images in WatchGuard Cloud.
If you downgrade to a Fireware version from v12.5.3 to v12.5.6 or from v12.6.1 to v12.6.3, WatchGuard Cloud automatically upgrades the firmware to the latest general (non-Beta) release for cloud management.
You cannot downgrade a Firebox to a version of Fireware lower than Fireware v12.1.3 Update 8, v12.5.9 Update 2, or v12.7.2 Update 2, based on your device model.
To downgrade firmware on a cloud-managed Firebox:
In WatchGuard Cloud, select Configure > Devices. Select the cloud-managed device you want to downgrade. On the Device Settings page, click Remove Device.
In the Remove Device dialog box, click Remove.
When you remove a device, it maintains the WatchGuard Cloud passwords, but is no longer cloud-managed. At the bottom of Account Manager, click Add Device and add the Firebox back to WatchGuard Cloud as a cloud-managed device.
For more information, see Add a Cloud-Managed Firebox to WatchGuard Cloud.
Connect to the device. From a computer on a network connected to the cloud-managed Firebox, open a web browser. In the web browser, go to https://
The Fireware Web UI login page opens. Log in with the user name admin and the passphrase you previously set for this device in WatchGuard Cloud. From the left pane, select System > Upgrade OS.
Select I have an upgrade file and then select the sysa-dl file you want to downgrade to. Click Upgrade. When no backup image is available or appropriate, click No. Click Yes to complete the downgrade and restart the device automatically.
The Firebox completes the downgrade and restarts. This can take 5 to 10 minutes to complete.
After the downgrade, the network and security settings are reset to factory default settings, but the admin and status passphrases are not reset. To manage the device, you must connect to it on Eth1, with the default IP address 10.0.1.1. For more information about the factory default settings, see About Factory-Default Settings.
If the Firebox (with TPM chip) uses DHCP and receives an IP address, it connects automatically to WatchGuard Cloud as a cloud-managed device. If the Firebox uses a Static IP address or PPPoE external connection, there must be someone onsite to run the Web Setup Wizard or to use a USB drive to gain Internet access to connect to WatchGuard Cloud. For more information, see Connect the Firebox.
See Also
Upgrade a FireCluster in WatchGuard Cloud
Downgrade Fireware OS
About WatchGuard Cloud Account Manager (Service Providers)
About WatchGuard Cloud Device Manager (Subscribers)
Reboot a Firebox
Manage Firebox Backup Images in WatchGuard Cloud
Recommended steps to prepare for the update of FlexiCapture Cloud SaaS
Please follow the steps below:
Validation of your projects and applications in a preproduction environment with the new version FlexiCapture prior to the update is recommended. To request a preproduction tenant please contact your account manager. To ensure a quick update of your project, please remove unused document definitions via Project Setup Station. consider compacting your project to remove unused versions of document definitions. As usual, it is the best practice to validate all changes using a dev/test environment before making the changes to your production project. set the retention period for processed batches to a lower value (under 5..7 days). In case a Document Definition in your production project is locked for editing, all your local changes will be discarded and the document definition will be upgraded automatically. Please check and unlock all document definitions using Project Setup Station (a part of Developer Package) before the upgrade. If you use local stations, download the installation images before the actual update. Processing of tasks submitted through FlexiCapture Cloud REST API will be suspended for the duration of maintenance window. The client using the API should be prepared to retry processing of any failed tasks submitted during the maintenance window or the tasks that didn’t complete processing before the maintenance window. If you use FlexiCapture Cloud in several regions, please ensure you have checked the schedule for the maintenance window for each specific region.
What you should know about FlexiCapture Cloud SaaS update procedure
The FlexiCapture Cloud update is performed during a scheduled maintenance window. To avoid any problems we recommend that you don’t use the system during the maintenance window. The FlexiCapture Cloud Operations team will update all components and services of FlexiCapture Cloud, validate the functionality of the environment and automatically update all projects to allow processing with the latest version of FlexiCapture. All tenants in FlexiCapture Cloud will be updated together during the maintenance period. Users may be unable to log in to the service for a short period of time. Users who are already logged in and are working on the verification tasks will experience errors. Therefore, we recommend that you avoid using the service during the maintenance window. The service may fail to accept tasks for processing. Processing of tasks submitted through FlexiCapture Cloud REST API will be delayed for the duration of the maintenance window. The client applications using FlexiCapture Cloud REST API must be prepared to retry processing of any failed tasks submitted during the maintenance window. Batches that are pending processing or submitted for processing during the maintenance period will go to Exceptions until the corresponding projects are updated. Users may restart processing of the batches that went to Exceptions manually, or submit the batches for processing again. The update of all projects for all current customers in the environment will be completed within the maintenance window. To continue using local stations (Verification Station, Project Setup Station and others), you must install the new version after the Cloud has been updated. Installation images are available for download at
Highlights of ICaaS applications update
(Undefined variable: K2Variables.CloudProductName)
All bug fixes in K2 Cloud Update 16 Fix Packs 1-16.
When you have an anonymous form with a Calendar control and you try to type a date, a "the date is invalid or in an incorrect format" error occurred.
Performance enhancement for forms using multiple SmartObject methods returning large amounts of data.
When using the "apply the changes made to the row on the editable list view" rule action on a form, and the refresh button to save values, it did not behave as expected.
When using the Export to Excel control on an Editable list view and the data contains a special character such as “&”, the special character did not export correctly to Excel.
When editing a workflow and configuring an Email reminder on a workflow task step, a “Cannot convert value ‘’ to Int32.” error occurred when starting an instance of the workflow.
Each release includes all bug fixes from preceding releases; see the release notes for previous releases for more details on bug fixes in previous versions.includes the following additional bug fixes:
Leave a Comment