Today was our second and final day at IGEL DISRUPT. Today was focusing all around the industry, what challenges people are facing, what technology they are seeing enter the market and ultimately what technology they think will be leading and interesting in 2019.Read More
Unified Access Gateway (formally Access Point) is used to secure external access for a Horizon View. There are numerous advantages over using Security Servers, which are still supported, noticeably the lower resources required to run and the removal of the necessity to pair with a dedicated security server. Not to mention the lack of Windows! In a multi-site environment with redundancy that is a significant reduction in deployed resource.Read More
We talk to Jason Southern and Luke Wignall of NVIDIA at VMworld 2017 in Barcelona. They discuss the latest updates to the NVIDIA GRID product range including the new P40 card that uses the latest pascal chipset. NVIDIA also demonstrate the technology in action including a preview of vMotion for vGPU based workloads.Read More
The guys at IGEL were nice enough to send me an IGEL UD Pocket recently for me to evaluate, the UD pocket is a bootable USB thin client that can be used to turn any X86 hardware into a thin client. I have been using the UD Pocket for the last month and have recorded a video with my thoughts and experiences of the device.Read More
In order to achieve a successful VDI deployment, there are numerous factors to take into consideration, I have picked a few below around some of the technical aspects that are important to get right.Read More
Traditionally you might map user network drives via a logon script or maybe a group policy preference. VMware’s User Environment Manager (UEM) gives you some other nice options in the fun filled world of drive mappings!
We can take a conventional approach by mapping a drive for all users or targeting by an AD object such as group or OU. OK, so far so group policy preferences!
Why don’t we map a drive on a per application basis? Using UEM we can associate the mapped drive with an app and set it to apply ‘on demand’ when said application is launched. This avoids the need for the drive mapping to happen at user logon but it is available when required.
But what about my power users that want to be able to manually map drives (and persist them across devices)? UEM does not capture these manually mapped drives by default but we can add the below registry location so this information is stored and reproduced in a different session
I’ve used network drives as an example here but by moving application settings into UEM we can optimise the logon process, provide a consistent user experience and control all relevant app settings in one place. Very Nice!
ESXi 6.0 Update 1 Breaks Horizon View prior to 6.2
Whilst out on a customer site, I had an unusual error in Horizon View 6.11. One of the pools just had “ViewCompsoer Fault:” and failed all compose jobs. Looking at the VMs in the Admin console, they all showed up as Deleting (Missing). The VMs in the vCenter didn’t exist so I had to manually delete them from the Adam Database using the VMware KBs
After trawling through the SQL Composer database to remove the Composer database entries I started to look at the error logs for View Composer. In Composer the logs had errors relating to failing to initialize the disks as it couldn’t find the path of the cloned disk. After checking the UFA logs in the View Composer log bundle, I came across an error “sslv3 Handshake Alert Error”. After a bit of digging I came across this article from VMware.
So it appears ESXi 6.0 Update 1 disables SSLv3 which is how the View Composer connects to the hosts in all versions of Horizon View prior to 6.2. Installing this update will cause the View Composer to fail on recompose tasks. This was disabled due to a vulnerability but you can re enable this as a workaround, you only need to re-enable port 902 as I have described below. .http://kb.vmware.com/selfservice/search.do?cmd=displayKC&docType=kc&docTypeID=DT_KB_1_1&externalId=2121021 )
Note: to edit a file in ESXI you can use the command VI in front of the file name, to insert text once in the editor, press the insert ley on the keyboard, once finished editing press escape to exit from insert mode, then type :wqto save and exit, to save without exiting instead use :q!
- Create a backup copy of the /etc/vmware/config file
- Edit the /etc/vmware/config file to append the following line at the end of the file:
vmauthd.ssl.noSSLv3 = false
Note: If you have the line vmauthd.ssl.noSSLv3 = true in the file, change it to vmauthd.ssl.noSSLv3 = false
[root@w1-fiqabj-003:~] cat /etc/vmware/config
libdir = "/usr/lib/VMware"
authd.proxy.nfc = "vmware-hostd:ha-nfc"
authd.proxy.nfcssl = "vmware-hostd:ha-nfcssl"
authd.proxy.vpxa-nfcssl = "vmware-vpxa:vpxa-nfcssl"
authd.proxy.vpxa-nfc = "vmware-vpxa:vpxa-nfc"
authd.fullpath = "/sbin/authd"
vmauthd.ssl.noSSLv3 = false
- Restart the rhttpproxy service with the command:
Taken from VMware article here - http://kb.vmware.com/selfservice/search.do?cmd=displayKC&docType=kc&docTypeID=DT_KB_1_1&externalId=2121021 )
The fix from VMware is to upgrade to Horizon View 6.2 which no longer uses SSLv3