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.
UEM has pretty decent in-built logging which can and should be used to initially troubleshoot both slow logon and application launch times. As it crops up for me relatively frequently I thought I would do a video running through some of the processes I use.
Slow Logons can be a real pain. I am in the business of trying to create as fantastic a user experience as possible, so a 2 minute logon is not a good start, especially if we are talking about a non-persistent VDI environment where every logon is an initial logon!
The ability for EUC administrators to easily deploy scripts who may not have access to NETLOGON shares and group policy management can be tricky. UEM provides an environment variable created by default pointing to a script repository in the Configuration share.
I’ve had a few problems (predominantly in labs) where the NSX host preparation stage has failed. There can be a few reasons for this but I have found the most consistent way around this is to deploy the vibs manually.
I’ve blogged about this for previous versions of VMware Horizon and with version 7.6 now GA I thought I would put all of the information together and hopefully simplify the process by removing some peripheral information.