Client upgrade screenshots

[ethutchinson]

We need to upgrade all our AnyConnect clients to 5.x through the image update in our FTDs. I have been asked to provide some screenshots for our documentation on what the client will see when they try to connect and the automatic update starts. I know this is a crazy request but does anyone have screenshots of this?

Anything at all would be appreciated.

[victoria88paul]

I understand that you're looking for screenshots to include in your documentation about the AnyConnect 5.x automatic update process. Unfortunately, I can't generate or provide specific screenshots, but I can guide you on what the experience typically looks like based on common behaviors and user flows during AnyConnect client updates via Firepower Threat Defense (FTD) devices.

Here’s a general outline of what users can expect to see when they attempt to connect, and an update is triggered:

1. Connecting to VPN

When a user tries to connect to the VPN with an older version of AnyConnect (e.g., 4.x), the following sequence usually happens if a client update is required:

Initial Connection Screen (Before Update)

• The AnyConnect client shows a standard connection window, where the user enters their username and password.

  User sees:

  • The connection window where the "Connect" button is visible.
  • A message like "Connecting..." or a progress bar.

Update Notification (Before Connection is Established)

• If the AnyConnect client is configured to check for the latest version automatically, the user might see a message informing them that a software update is required before they can proceed with the connection.

  User sees:

  • A pop-up or message saying: "A newer version of AnyConnect is required for this connection. The update will be downloaded automatically."
  • The "OK" or "Install" button to start the update.

2. Downloading the Update

Once the user acknowledges the prompt, the AnyConnect client begins downloading the new version.

Update Download Progress

• The AnyConnect client may show a progress bar or indicator that is downloading the update from the FTD device.

  User sees:

  • A progress bar or percentage indicating how much of the update has been downloaded.
  • A message like: "Downloading new version...".
  • Optionally, there might be a brief wait message while the update is prepared.

3. Install Update

After the download completes, the client will proceed with the installation of the new version.

Installation Process

• The AnyConnect client will automatically install the new version without requiring the user to manually intervene, though some versions may ask for confirmation to proceed.

  User sees:

  • A brief message such as: "Installing AnyConnect..." or "Applying the update...".
  • The installation process may take a few moments depending on the client system.

4. Reconnection Attempt with New Version

Once the update is installed, AnyConnect will restart (or just refresh), and the user will be able to proceed with the VPN connection using the latest version.

Post-Update Connection Screen

• After the update is applied, the client will show the same connection window, but the version number displayed in the application or the "About" section will reflect the new version (5.x).

  User sees:

  • A final confirmation message such as: "The update is complete. You may now reconnect to the VPN."
  • The connection process resumes as normal, with the user successfully connected after the update.

5. Potential Errors

In some cases, if the client update fails or if there is a configuration issue, the user might see error messages, such as:

• "The VPN client could not be updated."
• "Update failed. Please contact your administrator."

---

Tips for Creating Your Documentation Screenshots

1. Use a Test Environment: If possible, deploy the FTD and AnyConnect setup in a test environment. Try to simulate the update process by connecting with an older version of the client and documenting the prompts, progress bars, and installation steps.

2. Screenshots for Each Stage: You can capture screenshots of:

   • The initial connection attempt.
   • The message indicating that an update is needed.
   • The download progress.
   • The installation screen (if visible).
   • The final post-update connection screen.

3. Recheck Your Version: Different AnyConnect versions (e.g., 4.x vs 5.x) may have slightly different behaviors or UIs, so make sure the version you are testing matches your BOGO Subway Code deployment scenario.

4. Screen Recording: If you want to capture the entire update process in a more comprehensive way, consider using screen recording tools. You could then extract key frames to show in your documentation.

Resources

• Cisco AnyConnect Documentation: Cisco provides guides and release notes for AnyConnect. Check the "Upgrade and Update" sections for more details about the automatic update process. They might also provide images for reference.

[ccieexpert]

the upgrade should be similar to upgrade between 4.x version ..

this video will show a installation over 4.x using the installer, not a headend initiated ..

If this is not enough, i could try to do a quick lab setup ?

you can also download a virtual  FTDv or ASAv and then install 4.x on a test laptop/machine and then try to upgrade to 5.x - that way you can get exactly what you need...

https://www.youtube.com/watch?v=u6C5-mxPkqY

**Please rate as helpful if this was useful **