VMware Horizon Community
jrr001
Enthusiast
Enthusiast
Jump to solution

How do I prevent this?

I most large scale setups you will have 2 or more connection brokers (one being a replica) frontended by a load balancing solution.

What is the best way to prevent kill all the connections to desktops when you need to reboot say for patch tuesday one of the connection brokers?

Is there a setting in View manager so I can still use PCoIP and prevent breaking connection during broker maintenance?

Thanks...points awarded!

Reply
0 Kudos
1 Solution

Accepted Solutions
npeter
Expert
Expert
Jump to solution

This may be of helpful.. But you need find a way to tell load balancer to ignore this machine for further connections.

Disable or Enable View Connection Server (View4.6 ADmin Guide page 21)


You can disable a View Connection Server instance to prevent users from logging in to their View desktops.
After you disable an instance, you can enable it again.
When you disable a View Connection Server instance, users who are currently logged in to View desktops are
not affected.


Your View Manager deployment determines how users are affected by disabling an instance.
n If this is a single, standalone View Connection Server instance, users cannot log in to their desktops. They
cannot connect to View Connection Server.
n If this is a replicated View Connection Server instance, your network topology determines whether users
can be routed to another replicated instance. If users can access another instance, they can log in to their
desktops.
Procedure
1 In View Administrator, click View Configuration > Servers.
2 In the View Connection Servers panel, select the View Connection Server instance.
3 Click Disable.
You can enable the instance again by clicking Enable.

-noble

-nObLe

View solution in original post

Reply
0 Kudos
4 Replies
idle-jam
Immortal
Immortal
Jump to solution

there is a function where you could force log off or disconnect user from the view admin portal. as far as i know user will be disconnected when you do a reboot. perhaps you can do a reboot during the off peak period.

Reply
0 Kudos
mittim12
Immortal
Immortal
Jump to solution

It seems that when a session is authenticated against a broker it is tied to that broker.   When you reboot the broker it invalidates the session and does a disconnect.  This seems to only take place when you do a clean shutdown or reboot of the broker and is not applicable in the event of a hardware failure.    According to this thread, http://communities.vmware.com/message/1710503, there is a feature request to change that behavior. 

Reply
0 Kudos
Camek
Enthusiast
Enthusiast
Jump to solution

If you are using a hardware balancer, like BIG-IP, you can take one of the backend nodes off line in the balancer. When all the sessions have terminated on that node you can then do you need to with the off line node.

npeter
Expert
Expert
Jump to solution

This may be of helpful.. But you need find a way to tell load balancer to ignore this machine for further connections.

Disable or Enable View Connection Server (View4.6 ADmin Guide page 21)


You can disable a View Connection Server instance to prevent users from logging in to their View desktops.
After you disable an instance, you can enable it again.
When you disable a View Connection Server instance, users who are currently logged in to View desktops are
not affected.


Your View Manager deployment determines how users are affected by disabling an instance.
n If this is a single, standalone View Connection Server instance, users cannot log in to their desktops. They
cannot connect to View Connection Server.
n If this is a replicated View Connection Server instance, your network topology determines whether users
can be routed to another replicated instance. If users can access another instance, they can log in to their
desktops.
Procedure
1 In View Administrator, click View Configuration > Servers.
2 In the View Connection Servers panel, select the View Connection Server instance.
3 Click Disable.
You can enable the instance again by clicking Enable.

-noble

-nObLe
Reply
0 Kudos