Maintenance on a server in the pool

We recommend you to first create a destination pool for maintenance purposes:

Create a destination pool in which you include all your existing servers. You do not need load balancing here. Optionally, set default credentials.
Create an app configuration. Here you can enable the option to start the server as an admin session and for the system to allow keeping the login data when changing the destination in an app instance. This is useful if you haven‘t set default credentials even if you should use the same credentials for the servers.
Create an app instance for your user and select the destination that is to be maintained.

To remove a server from the live pool for maintenance, you should either disconnect all users from that server or shut down the server itself. Shutting down the server usually disconnects all users. If you are using roaming user profiles, they will be restored.
When shutting down the server, the Windows Exporter can no longer reach the server to display the metrics. Therefore, a Box icon appears next to the server.
Did you set the reuse of existing user sessions (sticky sessions) with at least 1 minute? Make sure all users are disconnected or the server is shut down, then click the Bracket icon. By doing this, you will delete the sticky user sessions in oneclick™ ahead of time.
Click the Pencil icon, deselect your server, and save your selection.
If the server is offline, an error message appears because oneclick™ ties to uninstall the load balancing service when it is removed from the pool. Since the server is offline, oneclick™ cannot do this. Ignore the message if you want to put the server back into the pool after maintenance. Your users will be distributed to the other servers when logging in again.

Connect to your server and perform the maintenance.
After completing the maintenance, open the live operation pool again and click on the Pencil icon.
Select your server and click Save. Your server is now available again and users can connect.