“Logon As Current User” and the “AD domain list” options default disabled after a VMware Horizon upgrade

When upgrading a VMware Horizon Connection server to version 7.8 or higher the following message appears during the upgrade.

This means the following settings are disabled after the upgrade:

  • Login As Current User will no longer work when selecting the “Log in as current user” in the Horizon Client
  • List of user domains will be withheld from Horizon clients

With this option, the Active Directory domain name is not visible and replace *DefaultDomain*

These settings are disabled to improve security but sometimes after a Horizon environment upgrade one or more settings needs re-enabled again. Here are the steps to enable these settings:

Enabling Login As Current User

Allow the Connection Server to accept logon as current user authentication

  1. Open: https://fqdn/admin
  2. Enter the user name and password
  3. Click on “View Configuration” and select Servers
  4. Select the Connection Servers tab
  5. Select the Connection Server and click on Edit
  6. Select the Authentication tab
  7. Scroll down the bottom and select “Accept logon as current user”
  8. Click on OK

Repeat steps 5-8 for each VMware Horizon Connection Server.

Enabling the domain list in the Horizon Client

  1. Open: https://fqdn/admin
  2. Enter the user name and password
  3. Click on “View Configuration” and  Edit the “Global Settings”
  4. Scroll down and select “Send domain list”
  5. Click on OK

After enabling this global setting the Active Directory domain is visible again and it is possible to select another AD domain.

Quick tip: Determine the VMware Horizon Agent options for a silent/unattended installation

When performing a silent/unattended installation of the Horizon Agent client you must specify MSI properties and Horizon Agent options to define the configuration of the agent. When a new version of the Horizon Agent comes available the documentation is not always available yet or up to date. When using a silent install of the VMware Horizon Agent with wrong options can result in a setup failed 1603 error.

A quick way to determine what options are available for the Horizon Agent that can be used is to install the Horizon Agent and manually select/deselect the options. After the installation and reboot open Regedit an browse to the following location:

HKEY_LOCAL_MACHINE\Software\VMware, Inc.\Installer\Features_HorizonAgent

Al the options/features are listed and have a value of:

  • Local = Installed/enabled
  • Absent = Not Installed/disabled

These options can be used for silent installing the VMware Horizon Agent. Here is an example that install the Horizon Agent:

VMware-Horizon-Agent-x86_64-7.10.0-14590940.exe  /s /v"/qn VDM_VC_MANAGED_AGENT=1 VDM_FLASH_URL_REDIRECTION=1 RDP_CHOICE=1 INSTALL_VDISPLAY_DRIVER=1 ADDLOCAL=BlastUDP,Core,HelpDesk,NGVC,PerfTracker,ClientDriveRedirection,RTAV,RDP,ThinPrint,TSMMR,USB,V4V,VMWMediaProviderProxy,VmwVaudio,VmwVdisplay,VmwVidd REBOOT=Reallysuppress"

In this example the following MSI properties are installed:

  • RDP is enabled
  • The agent is installed is a vCenter Managed desktop
  • Flash URL redirection is enabled
  • Installs the WDDM display driver

For the VMware Horizon Agent options refer to the following link.

 

Boot error: Shutting down firmware services… error after upgrading to VMware ESXi 6.7 Update 3

After upgrading one of my home lab servers to VMware ESXi 6.7 Update 3, I’ve got the following error when trying to boot:

Shutting down firmware services…

Page allocation error: Out of resources

Failed to shutdown the boot services.

Unrecoverable error

After changing the boot mode from UEFI to “legacy only” in the BIOS, the ESXi host booted without the error.

VMware has confirmed that this is a bug. There is VMware community thread (link) about this bug and two other workarounds. When there will be a permanent fix available is unclear at the moment.