At VMUG events I actively promote the vExpert community and encourage people to apply. To me the VMUG community and the vExpert community are intrinsically linked providing a value that while often understated is massively sought within Vendor communities.

[Read more…]

When configuring Workspace / Identity Manager you can decide to tick the box “Hide Domain Drop-Down Menu”

[Read more…]

One thing that always gives me pause for thought when dealing with any of the new storage or HCI offerings is the discussion of dedupe or space savings. Some are presented as ratios while others are a percentage. I was recently telling a colleague I was getting 97% dedupe on some VDI workloads while he was getting 4:1 on another type of workload.

It took us a few minutes to get the maths right to work out the numbers so we could compare like for like, and so to that end I decided to create myself a little table to save my aging brain cells at a later date.

One thing that is not immediately apparent to most is that it is a case of diminishing returns the higher your ratio, hence why I have done more of the lower values and included some higher ones for completeness.

At some point I might do a little calculator that gives exact answers but as a rough and ready aid, it served me well.

[table id=1 /]

 

EDIT: While the table above allows you to compare apples with apples numbers wise, it is not a full list of things to consider when looking at storage savings vendor vs vendor. The comment below by Rich Fenton from Nimble Storage gives a lot more insight into the other considerations. Great points and all worth considering when storage shopping.

Enjoy!

This one was a head scratcher for a few minutes, and I admit I had a little internal panic thinking something had broken my Pod.

When accessing the admin page after putting in a load balancer, I was presented with a blue background and a blank white box. No logon options, no dashboard, no hope!

I tried all the Connection Brokers to no avail until I tried the https://localhost/admin option locally on the Connection Broker.

After a little digging it appears there is a new security option in Horizon 7 that is now enabled by default – RFC 6454 Origin Checking.

This prevents cross site forging and “rejects the request if the URL is not https://localhost/admin or https://URL_used_in_Secure_Tunnel_URL_Field/admin.”

Basically the fix options are:

• You can correct the URL in the Secure Tunnel settings and use that address from now on.
• If  you want to disable the feature and are connecting direct to connection brokers, add “checkOrigin=false” to the locked.properties file in C:\Program Files\VMware\VMware View\Server\sslgateway\conf.
  • Do not be surprised if this file is not there, you may have to create it. Make sure you use notepad or similar, Word will add unnecessary characters.
• If it’s a load balancer address you can add “balancedHost=load-balancer-name” to the locked.properties file.

This will need doing on every Connection Broker in the Pod, and the services restarting.

For completeness I have added a couple of references from VMware which cover the issue from a documentation and KB article point of view.

KB Article

Documentation

As always, check what the security and other implications are for your environment and go with the load balancer statement (if this fits) rather than disabling the feature as this feature is there to protect the environment.