As VMware Horizon View deployments start to get much larger in numbers more and more people are starting to look at using Cloud Pod Architecture as a way to deploy their environments. Over the last few weeks this has lead to me getting a number of questions around how do Home Sites work.
The first thing you should know about Home Sites is they can not be assigned through the UI of the connection broker and currently must be done using the lmvutil command via a command prompt. For more information on assigning Home Sites you can see the commands here.
OK so what do Home Sites mean to our users. Lets first look at what happens when a user is NOT assigned a Home Site.
In the diagram below on the left the user connect from Site B so is directed to the connection server on Site B as there is capacity for the user in Site B the user is then assigned a desktop.
In the diagram on the right Site B is Off Line so the user is directed to the connection server on Site A and then assigned a desktop from the Global Pool on Site A
Now let’s look at what will happen if the user has a Home Site assigned to them.
As you can see in the diagram below on the left the user has been assigned to a Home Site on Site B. When the user connect the user is directed to the connection server on Site B and then assigned a desktop from the Global Pool on Site B.
Now in the diagram on the right the user is connecting from Site A and although they connect through the connection server on Site A they are still assigned a desktop from Site B (their Home Site)
Now let’s look at what happens when the users Home Site is down or off line.
As you can see from the diagram below if the users Home Site is down or off line the user is NOT assigned a desktop.
As you can see assigning a user a Home Site can have consequences if the Home Site goes down or off line, this is defiantly something you should keep in mind when using Cloud Pod Architecture.