VMware Horizon 8: Infrastructure Troubleshooting Quiz Questions and Answers
Answer :
Check the latest entries in the Blast-Worker-SessionId[#].log file on the desktop
Explanation :
Verifying the current codec and transport protocol used by a Blast session involves checking entries in the Blast-Worker-SessionId[#].log file on the virtual or physical desktop or RDSH server. The log file contains entries that indicate which codec (such as H.264, Blast Codec, Adaptive, etc.) and transport protocol (UDP/TCP) is being used. The Horizon Performance Tracker (Option A) can also be used for protocol/codec verification, but the question asks for log verification as described in module content. Option C (Event Viewer on admin workstation) and Option D (vdmadmin.exe) are not used for this type of protocol and codec verification.
The 'VMware Horizon Connection Server' service must always be running, as it provides essential services for the Horizon platform. While the Script Host is disabled by default and only required for certain operations, the Message Bus and Web Component should also generally be running, but the main always-required core service is the 'VMware Horizon Connection Server'.
Check if the user is able to log in, select a Horizon resource, and launch it.
Explanation :
The first step is to determine whether the problem occurs during the authentication or protocol phase. By checking if the user can log in, select a Horizon resource, and launch it, you can narrow down where the issue occurs. Port tests, service restarts, or deep packet analysis are useful only after this determination.
Security warning displayed when running the script downloaded from the internet.
Explanation :
A security warning when running scripts downloaded from the internet is a common deployment error when using PowerShell scripts to deploy UAG. This error can be resolved by running 'unblock-file' on the script. The other options are unrelated to the typical UAG deployment errors highlighted in the module.
TokenGroups attribute read permissions are insufficient in Active Directory.
Explanation :
If desktop launch fails on a remote pod for users assigned by group, it is likely because the Connection Server machine account lacks sufficient permission to read the tokenGroups attribute in AD. Granting access by adding the Connection Server to the Windows Authorization Access group is the resolution.
Time between UAG and AD server is not synchronized; reset AD server time to match UAG.
Explanation :
The 'Clock skew too great' error in authbroker.log occurs when the UAG time and Active Directory server time are not synchronized. The recommended action is to reset the AD server's time to match the UAG's UTC time. The other options do not address the authentication context clock synchronization.
Verify that values are set in the INI file for each network interface.
Explanation :
The error 'Invalid network in property netmask1' (which could mention netmask0, netmask1, or netmask2) indicates a missing value for a network interface in the INI configuration file. The proper action is to verify that a value is set in the INI file for each of the required networks.
Verify LDAP and CPA-specific attributes and attempt to recover using dsmgmt and ADSI Edit utilities
Explanation :
The administrator should first attempt to inspect and repair LDAP and CPA-linked attributes using dsmgmt and ADSI Edit, which are the main tools for direct LDAP and CPA troubleshooting as shown in the module; rebuilding AD is only a last resort.
To increase display protocol quality for high-resolution still images and graphics-intensive applications
Explanation :
Raising 'MaxBandwidthKbpsPerMegaPixelSlope' above the default 6200 allows higher bandwidth use per megapixel, improving quality for high-resolution and graphics-intensive applications (like medical imaging, 3D design), but uses more resources.
Verify the full certificate chain and client trust store
Explanation :
Browsers strictly validate the full certificate chain. A missing intermediate or root certificate in the client trust store can result in browser SSL errors, even if native clients function. Verify the chain and the client/browser trust root.
