How do multiple Horizon Connection Server instances in a pod maintain synchronization?
Horizon Connection Server instances keep their data in an AD LDS database, which is automatically synchronized between the Connection Server. AD LDS is a Lightweight Directory Access Protocol (LDAP) directory service that provides flexible support for directory-enabled applications, without the dependencies that are required for Active Directory Domain Services (AD DS). AD LDS provides much of the same functionality as AD DS, but it does not require the deployment of domains or domain controllers. In a Horizon environment, each Connection Server instance has a copy of the AD LDS database and replicates changes to other Connection Server instances in the same pod.This ensures that the Connection Server instances have consistent and up-to-date information about the Horizon resources and user sessions12Reference:
How does an administrator enable debug logging for a single user in VMware Dynamic Environment Manager?
To enable debug logging for a single user in VMware Dynamic Environment Manager, the administrator needs to create an empty FlexDebug.txt file in the same folder as the standard log file for this user.This will trigger FlexEngine to switch to debug logging for this particular user1.Debug logging is useful for troubleshooting purposes, as it provides more detailed information about the FlexEngine operations and actions1.
The other options are not correct because:
Updating the FlexEngine registry to DEBUG will not enable debug logging for a single user, but for all users who log on to the same computer.This option can only be set through Group Policy settings and applies to all users1.Moreover, this option is not recommended, as it can cause performance issues and disk space consumption due to the large size of the log files1.
Configuring the FlexEngine GPO to DEBUG will not enable debug logging for a single user, but for all users who are affected by the GPO.This option can only be set through Group Policy settings and applies to all users1.Moreover, this option is not recommended, as it can cause performance issues and disk space consumption due to the large size of the log files1.
What is the default URL used to access the Horizon Console?
The default URL used to access the Horizon Console is https://<connection_server_FQDN>/admin, where <connection_server_FQDN> is the fully qualified domain name of the Connection Server instance. This URL allows you to log in to Horizon Console by using a secure (TLS) connection. You can also use the IP address of the Connection Server instance instead of the FQDN, but this might result in blocked access or reduced security due to certificate mismatch. You cannot use https://localhost to connect from the Connection Server host, but you can use https://127.0.0.1 instead. The other options are not valid URLs for Horizon Console.Reference:Log In to Horizon Console
An end-user is experiencing a black screen when connecting to their virtual desktop. After a few seconds, the connection closes. Which could be the cause of the issue? (Choose three.)
A black screen when connecting to a Horizon virtual desktop can be caused by various reasons, such as network issues, hardware issues, Horizon tunnel issues, or underlying guest operating system issues. Based on the options given, the following could be the cause of the issue:
A vRAM shortage on the Horizon virtual machine. This can affect the display performance and cause a black screen or a disconnect.To resolve this issue, you should configure the pool to provide enough video memory for the resolutions you plan to present to the clients1.
The incorrect video driver version installed on the Horizon virtual machine. This can cause compatibility issues and prevent the display protocol from working properly.To resolve this issue, you should verify that the View desktop is using the correct video driver and that it is compatible with the VMware Tools and Horizon Agent versions installed23.
An incorrect firewall configuration. This can block or misroute the display protocol traffic and cause a connection failure.To resolve this issue, you should verify that the required ports are open between the client, UAG/Security server/Connection server, and VDI machine4.
The other options are not likely to cause a black screen when connecting to a Horizon virtual desktop:
The client machine video memory is too high. This should not affect the display protocol performance or cause a black screen. The client machine video memory is only used to render the display on the local device, not on the remote desktop.
The Horizon virtual machine video memory is too high. This should not cause a black screen or a disconnect either. The Horizon virtual machine video memory is used to allocate resources for the display protocol on the server side, not on the client side.
[Network Ports in VMware Horizon]
Which two capabilities are supported by VMware Dynamic Environment Manager Application Profiler? (Choose two.)
VMware Dynamic Environment Manager Application Profiler is a standalone application that simplifies the creation of Flex configuration files and predefined settings for use with VMware Dynamic Environment Manager. Application Profiler analyzes where an application stores its file and registry configuration. The analysis results in an optimized Flex configuration file, which you can edit in the Application Profiler or use directly in the VMware Dynamic Environment Manager environment. With Application Profiler, you can also create application-specific predefined settings, with which you can set the initial configuration state of applications.Save the Flex configuration file with predefined settings to export the current application configuration state1.
Therefore, the two capabilities that are supported by VMware Dynamic Environment Manager Application Profiler are:
It allows creation of application-specific predefined settings. This means that you can configure the default settings for an application that will be applied when a user launches it for the first time.For example, you can set the language, theme, or preferences of an application using Application Profiler2.
It analyzes registry and file system location settings for an application. This means that it monitors the changes that an application makes to the registry and file system when it is running, and generates a Flex configuration file that captures those changes.This allows VMware Dynamic Environment Manager to manage the user personalization of those settings across different devices and sessions3.
The other options are not supported by VMware Dynamic Environment Manager Application Profiler:
It allows individual user personalization of applications. This is not a capability of Application Profiler, but rather of VMware Dynamic Environment Manager itself.Application Profiler only helps to create the Flex configuration files that enable user personalization, but it does not apply them to individual users4.
It allows third-party user personalization of applications. This is also not a capability of Application Profiler, but rather of VMware Dynamic Environment Manager itself. Application Profiler only works with applications that store their settings in the registry or file system, and does not support third-party user personalization solutions such as AppSense or RES.
It allows creation of computer templates. This is not a capability of Application Profiler at all. Computer templates are used to create virtual machines or physical computers with a predefined configuration, and are not related to application management or user personalization.
[VMware Dynamic Environment Manager FAQ]
[Create a Computer Template]