It’s finally here, the day you’ve been waiting for, how to define a Horizon FLEX entitlement!
Hello, it’s Andy again. Today’s short video once again features a shiny me, but it’s thankfully very short: just over 90 seconds after you skip all the fancy bumpers we put at the front and back of it.
To recap, in part one I showed you how to build a Horizon FLEX compatible image. In part two, I showed you how to define acceptable use policy for groups of people. In today’s lesson, we’re going to take everything we’ve learned so far, sprinkle it with AD groups and build entitlements.
Entitlements are just the fancy way of saying that the people in accounting get access to a different image than the one you give the sales people, and those differing images can operate under different acceptable use polices.
The next section on the Horizon FLEX administrator’s console shows all the VM’s that are in use, what policies are being enforced, and even gives you the ability to tweak the settings for a specific user.
Bonus point! If you’re using VMware Mirage to manage your virtual images (and you really should) that information appears in the console too. Fantastic.
Next time, I think I might show you sometime I call my Russian Doll demo. It showcases why more people use VMware hypervisors than any other. It’s truly mind blowing.