What’s In The Studio – Pivoting Community Involvement to Video January 14, 2021. This feature require a command-line switch to enable in the Horizon Client installer. 
Unlike the Agent install key, it uses a binary value to denote if a feature is installed instead of “local” or “absent.” The Horizon Client has fewer installable options compared to the agent, and the only optional item that does not appear in this key, at least in a default installation, is URL Content Redirection. The contents of this field contain the list of features that are installed in the Windows Horizon Client. Inside this registry key, there will be a key named with a GUID. The path for this registry key on a 64-bit machine is HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\VMware, Inc.\VMware VDM\Client\Installer\. Horizon has a single installer that is used for both 32-bit and 64-bit Windows, so the location of this key will depend on what version of Windows you have installed. There is also a registry key that shows installed features for the Horizon Client on Windows. This registry key is located at HKEY_LOCAL_MACHINE\Software\VMware, Inc.\Installer\Features_HorizonAgentĪs you can see in the attached screenshot, features that are available have a value of “Local.” Features that aren’t available, ie those that were not installed, as listed as being “Absent.”
Inside your virtual desktops and RDSH servers, there is a registry key that shows all of the features available in the Horizon agent and whether they are available locally. Thanks to a tip from a couple of my colleagues, including William Uhlig and Dan Berkowitz, there is an easier way to see what was installed with the Horizon Agent. You could reinstall the agent or client to make sure the component you need is there. You want to try out something in Horizon that requires a change to the Agent or Client, but you can’t remember if it’s been installed.
From the command line, navigate to the C:\Program Files (x86)\VMware\VMware Horizon View Client\DCT directory and enter the following command: ’s say you have a desktop pool or RDSH Farm. In the Horizon Client window, from the Options menu, select Support Information, and in the dialog box that appears, click Collect Support Data. zip file that you can send to VMware Technical Support. You can use either the client UI or a command-line command to collect logs into a. Navigate to the C:\Program Files (x86)\VMware\VMware Horizon View Client\DCT directory and enter the following command: support.bat loglevelsĪ new command prompt window appears, and you are prompted to select a verbosity level. You can also use a command-line command to set a verbosity level. Use the View Common Configuration ADMX template file vdm_common.admx. For WSNM service logs, configure the log location, verbosity, and retention policy. For USB redirection logs, configure the log location, verbosity, and retention policy. For client UI logs, configure the log location, verbosity, and retention policy. The setting is called Configure PCoIP event log verbosity. Use the View PCoIP Client Session Variables ADMX template file pcoip.admx. For PCoIP client logs, you can configure the log level, from 0 to 3 (most verbose). You can use group policy settings to make some configuration changes: ViewMP-Client- XXXXXX.log vmware-mks- XXXXXX.log Use the View Common Configuration ADMX template fileĬ:\Users\% username%\AppData\Local\Temp\vmware- username-XXXXXXĬ:\Users\% username%\AppData\Local\VMware\VDM\LogsĬ:\Users\% username%\AppData\Local\Temp\vmware- username Note: You can use a GPO to configure the log location.
0 kommentar(er)
