How is VWS effected by a vCenter reboot?

Jump to solution

So we have an issue where we need to bounce vCenter.

Question 1. will my connected users be dropped?

Question 2.  I assume I can't import, clone, reconfigure ...what other functionality do i lose?

Question 3.  Once vCenter is back what do I need to do?

0 Kudos
1 Solution

Accepted Solutions
Highlighted
yorker1
1 Copper

RE: How is VWS effected by a vCenter reboot?

Jump to solution

1. No users will be dropped unless you are rebooting your ESX servers.  

2. Since the service is unavailable, you will not be able to do any type of Management nor Cloning of new Templates.  the Broker will continue to get Heartbeats from the VDI machines as long as the Data Collector Service is still up and running on the VDI Machines.

3. The connection should be self healing but you may require a restart of your 'Quest Connection Broker Service(s)' on each Connection Broker in your Farm if you see errors or issue occuring.

1 Reply
Highlighted
yorker1
1 Copper

RE: How is VWS effected by a vCenter reboot?

Jump to solution

1. No users will be dropped unless you are rebooting your ESX servers.  

2. Since the service is unavailable, you will not be able to do any type of Management nor Cloning of new Templates.  the Broker will continue to get Heartbeats from the VDI machines as long as the Data Collector Service is still up and running on the VDI Machines.

3. The connection should be self healing but you may require a restart of your 'Quest Connection Broker Service(s)' on each Connection Broker in your Farm if you see errors or issue occuring.