HOTSPOT (Drag and Drop is not supported)Refer to the exhibit.An administrator prepared a golden image based on a Windows Server Operating System. They plan to use this image to create a single-session virtual desktop pool. The installation is completed, the virtual machine is turned off, and the snapshot has been created. When the administrator creates the desktop pool, they are unable to select the created image and snapshot. They do see other previously created golden images, based on Desktop Operating Systems.The administrator has opened the Horizon Console.Mark the correct menu option where the administrator can enable Windows Server Operating Systems to be used as single-session desktops by clicking on it.
Answer(s): A
DRAG DROP (Drag and Drop is not supported)Refer to the exhibit.Drag and drop the labels on the left into their correct location in the diagram of VMware Horizon Architecture on the right.
An administrator is configuring load-balancing settings in Horizon Console for a RDSH Farm. Which two check boxes can be selected to influence the load balancing behavior? (Choose two.)
Answer(s): B,C
Load balancing is a feature that allows administrators to distribute the load of published desktop and application sessions across multiple RDS hosts in a farm. Load balancing can improve the performance and availability of the sessions and the hosts. Horizon offers two ways of configuring load balancing for RDS hosts: using load balancing settings in Horizon Console or using custom load balancing scripts.The load balancing settings in Horizon Console allow administrators to define how Horizon calculates the server load index, which indicates the load on each RDS host. The server load index can range from 0 to 100, where 0 represents no load and 100 represents full load. A server load index of -1 indicates that load balancing is disabled. Horizon uses the server load index to determine which RDS host is the best candidate for placing a new session request. The load balancing settings in Horizon Console include the following check boxes that can be selected to influence the load balancing behavior:The use custom script setting for customized RDSH load balancing: This setting allows administrators to override the default behavior of the load balancing settings and control the placement of new sessions by writing and configuring custom load balancing scripts. The custom scripts must write the server load index to a specific registry key on each RDS host. Horizon will use the value from the registry key instead of calculating it from the other settings.The Include Session Count setting to include the session count on the RDSH for load balancing: This setting allows administrators to include the number of sessions (connected, pending, and disconnected) on each RDS host as a factor in calculating the server load index. By default, Horizon uses the following formula to calculate the server load index based on the session count: (connected sessions + pending sessions + disconnected sessions)/ (maximum session count). If the maximum session count is configured as unlimited, Horizon falls back to using the absolute number of total sessions.The other options are not check boxes that can be selected in the load balancing settings in Horizon Console:The floating dynamic host profile setting, created in the vSphere profile section: This option is not related to load balancing for RDS hosts, but rather to dynamic environment manager for instant- clone desktops. A dynamic host profile is a vSphere profile that contains configuration settings for instant-clone desktops, such as network settings, domain join settings, and customization scripts. A floating dynamic host profile is a type of dynamic host profile that applies to floating desktop pools, where users are assigned a random desktop from a pool at each login. The Horizon DRS setting for fully automated vSphere load balancing: This option is not related to load balancing for RDS hosts, but rather to distributed resource scheduler (DRS) for vSphere clusters. DRS is a feature that monitors and balances the CPU and memory resources across multiple ESXi hosts in a cluster. DRS can also migrate virtual machines between hosts using vMotion to optimize resource utilization and performance. Horizon DRS is an extension of DRS that integrates with Horizon and provides additional capabilities, such as affinity rules, maintenance mode, and power management. Horizon DRS can be configured with different automation levels, such as fully automated, partially automated, or manual.
Configuring Load Balancing for RDS Hosts in Horizon Console, Load Balancing Settings, Load Balancing Scripts, [Dynamic Host Profiles], and [VMware Horizon 8.x Professional Course]
An IT support center has been tasked with helping with Horizon desktop user issues. What is the minimal level of Horizon Console access they would need to perform this action?
The minimal level of Horizon Console access that the IT support center would need to help with Horizon desktop user issues is the Help Desk Administrators role. This role allows the IT support center to view and troubleshoot user sessions, reset user passwords, send messages to users, and perform other help desk tasks. The Help Desk Administrators role can be assigned to users or groups on any access group that contains the desktop pools or farms that the IT support center needs to support.The other options are not the minimal level of Horizon Console access for this scenario:Local Administrators: This role allows full administration rights on a specific access group and its sub- access groups. This role can perform all the tasks of the Help Desk Administrators role, as well as create, edit, and delete desktop pools, farms, applications, entitlements, and other objects. This role is more than what the IT support center needs to help with user issues. Global Help Desk Administrators: This role allows full administration rights on all access groups in the Horizon environment. This role can perform all the tasks of the Local Administrators role, as well as create, edit, and delete access groups and global entitlements. This role is more than what the IT support center needs to help with user issues.Inventory Administrators: This role allows limited administration rights on a specific access group and its sub-access groups. This role can view and manage desktop pools, farms, applications, entitlements, and other objects, but cannot create or delete them. This role can also perform some help desk tasks, such as viewing user sessions and sending messages to users, but cannot reset user passwords or troubleshoot sessions. This role is not sufficient for what the IT support center needs to help with user issues.Administrators: This role allows full administration rights on all access groups in the Horizon environment, as well as global settings, licensing, roles and permissions, events configuration, and other system-wide settings. This role can perform all the tasks of the other roles, as well as configure and manage the Horizon infrastructure. This role is more than what the IT support center needs to help with user issues.
Understanding Permissions and Access Groups and [VMware Horizon 8.x Professional Course]
What is the effect of changing any VMware Blast policy that cannot be changed in real time?
Answer(s): D
VMware Blast policy settings are stored in the registry key HKLM\Software\Policies\VMware,Inc.\VMware Blast\Config on the remote desktops or RDS hosts that use the VMware Blast display protocol. These settings can be configured by using the VMware Blast ADMX template file (vdm_blast.admx) and applying it through Microsoft Group Policy Object (GPO). Some of these settings can be changed in real time, which means that they take effect immediately after the policy is applied, without requiring a reboot or a reconnection of the Horizon Client. However, some of these settings cannot be changed in real time, which means that they require a reboot or a reconnection of the Horizon Client to take effect.The effect of changing any VMware Blast policy that cannot be changed in real time is that the Microsoft GPO update rules apply and GPOs are updated manually or by restarting the Horizon Agent. This means that the new policy settings will not be applied until one of the following events occurs:The Horizon Agent service is restarted on the remote desktop or RDS host. This can be done manually by using the Services console or the command-line tool sc.exe, or automatically by using a scheduled task or a script.The remote desktop or RDS host is rebooted. This can be done manually by using the Restart option in Windows, or automatically by using a scheduled task or a script. The Group Policy refresh interval is reached. This is a configurable time interval that determines how often the system checks for and applies new or changed GPOs. By default, this interval is 90 minutes for domain members and 5 minutes for domain controllers, with a random offset of 0 to 30 minutes. This interval can be modified by using the Group Policy refresh interval for computers setting in the Computer Configuration\Administrative Templates\System\Group Policy folder of the Group Policy Management Console.Therefore, to ensure that the VMware Blast policy settings that cannot be changed in real time are applied as soon as possible, it is recommended to restart the Horizon Agent service or reboot the remote desktop or RDS host after applying the policy.
VMware Blast Policy Settings, Group Policy refresh intervals, and [VMware Horizon 8.x Professional Course]
Post your Comments and Discuss VMware 2V0-51.23 exam prep with other Community members:
Our website is free, but we have to fight against AI bots and content theft. We're sorry for the inconvenience caused by these security measures. You can access the rest of the 2V0-51.23 content, but please register or login to continue.