In most cases, it is best to perform a traditional update from Version 6.1 to Version 6.2.0 as described in Update Paths to Version 6.2.0.

However, the following cases require you to reimage and/or deploy your appliance:

• If you are installing the Firepower on the Firepower Management Centers MC1000, MC2500, or MC4500 you must reimage the appliances to Version 6.2.0. Because those appliances are newly supported in Version 6.2.0, you cannot perform a traditional update on those appliances.

• If you are installing Firepower Threat Defense Virtual in a Microsoft Azure Standard D3 environment, you must deploy the appliances to Version 6.2.0. Because this environment is newly supported in Version 6.2.0, you cannot perform a traditional update on those appliances.

• If you are moving from ASA with FirePOWER Services to Firepower Threat Defense, you must reimage your ASA device to deploy Firepower Threat Defense.

• If you have a Firepower Threat Defense device (physical or virtual) that was installed before version 6.1.0, and you want to switch between managing it with a Firepower Management Center and managing it with the Firepower Device Manager, you must reimage the Firepower Threat Defense.

  New installations of version 6.1.0 and later do not require a reimage.

• If you are recreating a Firepower Threat Defense Virtual device in a different environment than before, you must redeploy your virtual platform to Firepower Threat Defense. For example, if you were using VMware before and now want to deploy in AWS, you must redeploy rather than update.

• If you are unable or disinclined to follow the required update path as described in Update Paths to Version 6.2.0, you must reimage and/or deploy your appliance.