Most Recent VMware 2V0-51.23 Exam Dumps

Collaboration is a feature that allows users to invite other users to join an existing Windows or Linux remote desktop session with both screen sharing and audio out features enabled. A remote desktop session that is shared in this way is called a collaborative session. The user that shares a session with another user is called the session owner, and the user that joins a shared session is called a session collaborator. A Horizon administrator must enable the Session Collaboration feature for the desktop pool or farm that contains the remote desktops that support collaboration.

One of the requirements to enable Session Collaboration is to use the VMware Blast display protocol for the remote desktops. VMware Blast is a protocol that provides high-performance, high-quality graphics and multimedia delivery over LAN or WAN networks. VMware Blast supports Session Collaboration by allowing multiple users to view and interact with the same remote desktop session simultaneously. Other display protocols, such as PCoIP or RDP, do not support Session Collaboration and will not allow users to share or join collaborative sessions.

Therefore, to enable Session Collaboration in the VMware Horizon environment, the administrator needs to use the BLAST protocol as a requirement.Reference:Configuring Session Collaboration,Sharing Remote Desktop Sessions, and [VMware Horizon 8.x Professional Course]

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:

Configuring Horizon Connection Server1

Understanding VMware Horizon Services2

A golden image must have a current snapshot to be used for cloning, and having multiple active snapshots can cause confusion and issues in the provisioning process. Additionally, selecting the correct Guest OS version is crucial for compatibility and optimal performance. These factors must be correctly configured for a VM to appear in the list of available golden images for provisioning.

For instant-clone operations in Active Directory, the user account used by VMware Horizon needs specific permissions to manage computer objects effectively. These include the ability to create and delete child objects and computer objects, as well as read and write all properties of those objects. These permissions ensure that Horizon can create, modify, and clean up computer accounts associated with instant clones, facilitating seamless desktop provisioning and management.

The two options that are available for the administrator to make the shortcut available to all desktop pool users, while minimizing ongoing administrative effort, before updating the desktop pool golden image are:

Copy the shortcut to c:\users\Public\Desktop. This option will place the shortcut in the public desktop folder, which is shared by all users who log on to the same computer.The public desktop folder is normally a hidden folder, so the administrator needs to enable the option to show hidden files and folders in File Explorer1. This option does not require any additional software or configuration, but it will only work for the existing desktops in the pool. If new desktops are added or refreshed, the shortcut will not be copied automatically.

Configure a Shortcut with DEM (Dynamic Environment Manager).This option will use the DEM console to create a shortcut configuration that will apply the shortcut to the user's desktop during logon2.The administrator needs to install and configure DEM on the Horizon environment, and create a configuration share and a profile archive share for storing the DEM settings3. This option requires more initial setup, but it will work for any desktop in the pool, regardless of whether it is new or refreshed. It also allows more flexibility and control over the shortcut properties and conditions.

The other options are not valid or feasible because:

Copying the shortcut during user provisioning to a non-writeable App Volume will not work because App Volumes are used to deliver applications, not shortcuts.App Volumes are virtual disks that are attached to the virtual machines at runtime, and they contain application files, registry entries, and settings4. Copying a shortcut to an App Volume will not make it appear on the user's desktop.

Copying the shortcut to the Windows Default Domain Controller Policy will not work because this policy is used to configure settings for domain controllers, not desktops.The Default Domain Controller Policy is a Group Policy Object (GPO) that is linked to the Domain Controllers organizational unit (OU) in Active Directory, and it contains security settings that are applied to all domain controllers in the domain5. Copying a shortcut to this policy will not affect any desktops in the Horizon environment.

Configuring a Shortcut with Horizon View Client will not work because Horizon View Client is used to connect to remote desktops and applications, not to create shortcuts.Horizon View Client is a software application that runs on various devices and platforms, and it allows users to access their virtual desktops and applications through a secure connection6. Configuring a shortcut with Horizon View Client will not make it appear on the user's desktop.

How to make a desktop shortcut available for all users in Windows 101

VMware Dynamic Environment Manager (DEM) 2306 -- Carl Stalhood2

VMware Tech Zone Antivirus Considerations in a VMware Horizon Environment: exclusions for Horizon View, App Volumes, User Environment Manager, ThinApp3

App Volumes Overview

Default Domain Controller Policy5

VMware Horizon Clients Documentation6