// This is the script to give summary on the main page.
Think IPM

Monday, April 24, 2017

Cleaning up Horizon Database Errors

vSphere vCenter is great.  Horizon is great.  Composer is great.  Sometimes though, they go off script and start getting out of sync.  I’m sure everyone who has run a VMware View Horizon farm has run into issues where the view database just doesn’t reflect reality.  The VMs are long deleted but Composer and Horizon still think they are there and you get the never completing status of Deleting in the Horizon administrator console.

image

I remember the not so distant days when this would require firing up ADSI edit and doing some surgical removals of MANY entries in LDAP… 

As of Horizon 6.1, there is a MUCH easier way now.  Check out ViewDBCheck.  Most likely in
‘C:\Program Files\VMware\VMware View\Server\tools\bin’ on our connection server.

image

This handy tool will scour the Horizon DB and look for inconsistencies between the DB, the vCenter inventory and Composer DB.  If it finds any, it will give you a yes/no prompt to clean up and then do it’s thing.  Very Nice!

Although officially released for 6.1 and up, you can also use it for 5.3 by using the Fling found here.

Click Here to Continue Reading >>

Wednesday, April 19, 2017

Pushing the NVIDIA Grid VIB to vSphere using Update Manager for vGPUs.

I’ve been working with a customer getting the NVIDIA Tesla M60 cards working in their environment and compiled some great information for those of you looking into this.

So the official installation guide for the VIB is pretty much this KB article :  https://kb.vmware.com/kb/2033434

This is a pretty manual process.  I found that you can also easily and successfully use Update Manager to push the entire installation of the VIBs to your hosts.  The advantage being scale, consistency and also the ability to see the VIB installation (Baseline) in vCenter.

To start, make sure you are getting the correct enterprise versions of the VIBs and drivers.  (https://nvidia.flexnetoperations.com)

Once you have your offline bundle, you can head over to your Update Manager screen and choose the patch repository and Import Patches.

image

Once you upload the VIB Offline bundle, you should see it in the list of patches. (Note that the kepler one is the consumer version and should NOT be used) If you know how to remove it from the patch repository, drop me a note on twitter or in the comments.

From there, you can add it to a host extension baseline.

image

Now you can easily scan and remediate individual hosts or groups of hosts to install the VIB for Shared vGPUs.

To verify that the VIB was installed correctly, you can putty over to a host and run the command nvidia-smi.  If the VIB is installed correctly and you have you GPU cards in the host, you should see a similar output.

image

Once the VIB is installed, using the HTML vSphere Client, you should be able to add the shared PCI device to the Desktop VM (or image) and see the appropriate profiles.  

image

Note that shared PCI is a feature of VMware’s Enterprise Plus licensing.  Appropriate host licensing or Horizon licensing will be needed to power a machine up with a shared vGPU card.

ScreenClip

After installing the Display Drivers in the Windows VM, be sure to set the licensing to GRID Virtual Workstation.

Bonus: Once you have it all working, test it all out using the new awesome Google Earth!
(Super cool 3D modeling across many of the world’s neighborhoods)

image

Click Here to Continue Reading >>