Tag Archives: VMware Horizon View

Troubleshooting Horizon View with Log Insight

VMware vRealize Log Insight provides out of the box content pack for Horizon View. I find the content pack useful for both monitoring and troubleshooting. Naturally, there are cases where you need to build your own custom field and dashboard. In this blog, I share one such example.

The example I share is a Mass Disconnect of users. This means many users were suddenly disconnected at the same time, causing disruption at work and complain to IT.

Mass disconnect can certainly happen, and Horizon View Event Database records that. You will see the string “has disconnected from machine” in the View Event DB. Here is one such example. In this case, I’ve filtered to a particular user.


The first challenge is Horizon View Event does not distinguish between abnormal disconnect and normal disconnect. You will see many such string in the event DB. It is difficult to analyse in large environment as you cannot visualise.


Yes, see the example below.


I queried the same string. With Log Insight, I can query all the View Connection Server, not just one at a time. That’s another benefit of Log Insight.

From the above, you can see clearly that the string happens many times. I plotted for 5 days, and we can see the pattern matches the working hours. So how do we see an abnormal one since the log does not distinguish it?

The mass disconnect means it hit many users at one shot. Within 1 minute, you will see many users hit. Log Insight enables us to zoom. As you can see below, I zoomed into 5 seconds and we can see there is a mass disconnect event within that 60 seconds.


I masked out the user name. Yes, you can also show the user Microsoft AD ID in the table. I also masked the ESXi host. Yes, that means you can group the result by ESXi Host. An example of such chart is shown below. We can also show them by cluster.


We can also present the chart differently. In this chart, I group by ESXi, as I want to know quickly how many users were hit for each ESXi. From here I can tell it was quite well spread.


Once I know the users, we can create a custom group in vRealize Operations. This has to be done manually. It’s a one time effort, so it’s okay with me.

Once the custom group created, I can run analysis on it. For example, I can check if the disconnect were because of disk. As you can see below, the disk latency rose to 543 ms during the time of the disconnect. It’s a one time rise, and the time matches the mass disconnect time.


In vRealize Operations, we can zoom into the specific time. Here, it’s clear that it’s a one time spike.


Hope you find the example useful.

VMware App Volumes 2.9 Installation – Part 4

In Part 3, we completed the Agent and View Broker installation. In this part 4, we are now ready to configure AppStacks.

Go back the Windows VM where you install your App Volumes Manager. If you remember, we left at the screen in Part 2. There is no AppStack created yet. Click the Create AppStack button.


You get the following screen. To create AppStack, just need to specify the name, datastore, etc. Click the Create button.


It is not instant, and the status changes to Creating.


Wait for the above process to complete. Once completed, the status will change to Unprovisioned. Click on the Provision button. Notice it’s giving you a hint on the next step, which is Select Provisioning VM.


Remember the MS AD integration requirement? This is where it comes in handy. You need to find the computer. In my case, I just typed “volume“, clicked Search button, and it found my Provisioning VM.

I selected it, and clicked on the Provision button.


The AppStack status is now changed to Provisioning. Again, it’s giving you a hint on the next step, which is to install applications on the provisioning computer.


My plan is to create >1 AppStacks so I can evaluate cross AppStacks integration and see the experience in managing multiple AppStacks. I created these 3 AppStacks

  1. Core Apps:
    1. Basic and mandatory apps, like Java, Flash, Chrome, FF.
    2. The reason for including browsers is browsers typically needs plugins.
  2. Productivity:
    1. MS Office, Adobe Reader
  3. Admin Tools
    1. SSH, BitVise, vSphere C# Client, vSphere Web Client, etc.

This what it looks like after I created 3 AppStacks. The next step is to choose a Provisioning VM.


A Provisioning VM can be used for >1 AppStack, but not at the same time. If you do not manually unassign it, you get an error message like the following:


The next step is to install application. I will use a separate post to mark the separation, as the work is done on another place (the Provisioning VM). You can find it on Part 5.

VMware App Volumes 2.9 Installation – Part 3

In Part 2, we completed the Volumes Manager installation. In this part 3, we are now ready to install the Agent and Horizon View Broker. You can do them in any order.

Agent Installation

The step is simpler than the Volumes Manager installation. You start with the same ISO image and setup.exe.

Go to the Provisioning VM, and mount the ISO file. Once done, click on the setup.exe.


The same wizard screen appears.


This time, leave the choice as Agent.


The only thing you need to specify is the App Volumes Manager address. I use FQDN as I prefer to avoid hard coding IP address.


And within a few minutes, it’s done. You get the screenshot like this to confirm it’s done.


Once that’s done, it will prompt you to reboot. After that, power it off so you can take a snapshot. This preserves any changes.


You now have a master image, ready as your provisioning machine. Keep this machine clean.

You specified the App Volumes Manager address during the setup. Verify it’s registered with the Volumes Manager. You should see your newly registered VM in the Infrastructure tab, Machines subtab.


Now that’s done, let’s move to the Horizon View Broker Service.

App Volumes View Broker Service Installation

The step to install the broker is similar to the agent. In fact, the process was faster than the Agent installation.

Mount the App Volume installer on your View Connection Server.


It only ask for your App Volume Manager.


Yes, that’s it. Pretty simple to install the Agent and the View Broker. With that, we are ready to configure AppStack. I cover that in Part 4.