This enhancement also reduces the overhead you’d normally incur when deploying Horizon on public clouds. This gives you the advantage of separating the Horizon infrastructure from your VDI workloads, and third-party entities can manage the Connection Server as a service on your behalf. You can now choose vCenter Type to support your on-premises management of Cloud Burst capacity, up to about 120ms latency between Agents and the Connection Server. The Horizon Console has its share of improvements this quarter, including improvements to Cloud Burst, the ability to run apps indefinitely, new options when creating pools, and more.Ĭhoose vCenter Type for Cloud Burst. But the benefits include unique SIDs and parity with Linked Clones.
This can result in slower provisioning since it involves more reboots. This release now supports Sysprep on Instant Clones without parents. HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Vmware, Inc.\Vmware VDM\Agent\Configuration\Screen-capture Blockingįor more information, see Configuring Remote Desktop Features in Horizon. The registry key modified on the agent machine is: To configure Screen Capture Blocking, use the Horizon Agent GPO. To block in-guest screen captures, see Microsoft’s best practices. Also, this feature blocks screen captures from the Client endpoint only.
The option is not supported on HTML, but you can deactivate HTML if you want to.
#Vmware horizon client multiple monitors windows#
Note: This option is supported on Clients and Windows Agents only. This release provides the ability to block viewers from capturing Horizon session screens, preventing or reducing intentional data theft, and mitigating malware from making periodic screen grabs. Additional REST API endpoints, including federated access group, Event DB APIs, RBAC support for existing REST APIs, and more.įor more information, see Using the VMware Horizon Server REST API and VMware Horizon Server API.
#Vmware horizon client multiple monitors update#
0 kommentar(er)
