Jump to content

Upgrade on-prem Access (Cluster)


Recommended Posts

Hello

We run Access on-premise in a cluster of 3 nodes, version 23.09. We now want to upgrade it to 24.07, when looking at the upgrade documentation it says to remove all nodes except one, and now upgrade the node that still is connected to the loadbalancer.
Upgrade a Workspace ONE Access Cluster (omnissa.com)

This sounds kinda odd to me, is there really no way to upgrade with 0 downtime for the end user?

We have a completly HA Horizon environment with all components loadbalanced, two pods, multiple UAGs, AppVolume Managers, Connectionservers etc.

The part that currently makes the environment not 100% serviceable without any disruption is Access, which is being more and more important in our environment

Link to comment
Share on other sites

  • Replies 4
  • Created
  • Last Reply

Top Posters In This Topic

Popular Days

Top Posters In This Topic

  • Employee

To ensure a smooth upgrade and a stable service startup, downtime is necessary when upgrading Workspace ONE Access (On-Premises). It is recommended to schedule the upgrade during periods of low user activity. If you have a disaster recovery site, you may consider utilizing it as part of your upgrade strategy. Please note that users connected to Horizon will not be disconnected until they choose to log out of their sessions.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...