What? You've never heard of the VMware OS optimization tool? Hah! Neither had I until recently; so when I found this nugget, I had to write about it. 

The vOOT—is that a name?—is the VMware OS Optimization Tool, and it is a free download for end-users, typically running VDI, to turn off unneeded services, registry keys, and other functions: does your virtual desktop really need the Wireless WAN Autoconfig service running? Likely not! It comes with two parts:

• OS Optimization Tool (check and optimize)
• Remote OS Analysis Tool (check only)

Typically you will start by running the Remote OS Analysis Tool and checking your virtual desktops; or you might just check a VDI template or seven. 

This will generate a report for each virtual desktop; and it can be view dynamically, as a graphical report, or exported as a CSV. You will have to do a little work to get the individual CSV files aggregated if that's desire.

And, the templates against which you check your VDs can be customized for further optimizations, or if you happen to need WWAN services on your desktops, for example :).

Before you run vOOT for the first time, you will need to have run View PowerCLI (different from the vSphere PowerCLI; installed locally on the View Connection Broker server), otherwise you will get a PowerCLI error.

Make sure you follow the steps to setup WinRM as outlined in the Remote Analysis Tool User Guide. 

The VMware OS Optimization Tool is a VMWare Labs, called Flings, tool, developed by loyal VMware community members with/without help from VMware :). 

☑︎ Awesome
☑︎ Useful
☐ Easy to Use
☒ Supported

Can't wait to get it? Download vOOT.

Here's an example from a recent troubleshooting session. A user could login, but did not have any inventory available in the web client. Huh?

Why would this happen? First, it is not because you forgot to add the user to the SSO RBAC list. If you had, they wouldn't even be able to login. No, you did that correctly. 

It was probably because, as in this case, you added the user to a group in SSO that was not configured for actual inventory permissions. All you need to do is add that group in with the appropriate RBAC roles to the appropriate inventory-level object.