Windows 10 21H2 on VMware VDI Horizon 8 Version 2111 ESB with Zoom

The latest release Zoom which is required to deploy due to a CVE-2022-22782 and CVE-2022-22786 vulnerability:

 

Zoom for VDI 5.10.2

Zoom plugin for Hozion 5.10.2

 

Windows 10 21H2 on VMware VDI Horizon 8 Version 2111 ESB with Zoom

Windows 10 21H2 on VMware VDI Horizon 8 Version 2111 ESB with Cisco Jabber

The following combination will be consider more stable and hit less bugs so far:

 

VMware Agent – 8.4.0-18964730

VMware Horizon Client - 8.4.1-19480429

 

Cisco Jabber 14.1.1 (14.1.1.56904 Build 306904)

Cisco Jabber JVDI agent 14.1.1

Cisco Jabber JVDI Client 14.1.1

 

 

Windows 10 21H2 on VMware VDI Horizon 8 Version 2111 ESB with Cisco Jabber

VMware horizon client upgrade and reinstall handling when you using Cisco JVDI client

1. If you upgrade Horizon client from 5.x to 8.x, no action is required on Cisco JVDI client
2. If you uninstall/reinstall Horizon client, you need to reinstall Cisco JVDI client after the Horizon client being uninstall / reinstall.

 

VMware horizon client upgrade and reinstall handling when you using Cisco JVDI client

After upgrade to VMware 8 (2111)- Zoom on VDI - need to upgrade zoom VMware media plugin on the physical machine

VMware Horizon 8 2111 is an Extended Service Branch (ESB), after you upgrade the infra, if you upgrade your horizon client from 5.x (Horizon 7), to 8.x (e.g. 8.41 (2111)) or 8.5 (2203)). You need to also upgrade your Zoom Plug-in on client for VMware Horizon. Otherwise, your Zoom running on your VDI have many malfunctioning.

 

Zoom Plug-in on client for VMware Horizon

https://zoom.us/download/vdi/5.10.2/ZoomVmwareMediaPlugin.msi

 

After upgrade to VMware 8 (2111)- Zoom on VDI - need to upgrade zoom VMware media plugin on the physical machine

How to setup VMware Security Server to support login outside firewall and within DMZ at the same time?

Possible Solution: Using DNS name with different IP address resolve from external and internal

e.g. vdi001.abc.com

It will resolve from Internet / external network a IP address A (e.g. 203.x.x.x – You Public or external IP address on firewall which is use for NAT mapping)

Then, it resolves IP address B (e.g. 192.168.x.x – Your VMware Security IP address (DMZ))

But, it only work for using RDP and Blast protocol.

Remark:

1. RDP and Blast support using DNS name

2. PCoIP did not support DNS name (It must be IP address)

How to setup VMware Security Server to support login outside firewall and within DMZ at the same time?

VMware VDI issue - slow and force logoff

There are many reason will cause VDI slow and force logoff, one of the reason is out of memory (high memory usage) on ESXi host

If your host using over 90% physical memory and also have Memory (Balloon). That mean you out of memory on that ESXi host.

 

There are several possible solutions:

1. Reduce no. of VDI

2. Reduce the RAM allocation on each VDI

3. Add additional physical memory to ESXi host

VMware VDI issue - slow and force logoff

How to disable VMware View pool start up automatically

1. Power off the vCenter (Make sure you able to connect the ESXi host via vSphere and/or SSH before power off vCenter) (Make sure your ESXi host didn't under lockdown mode)
2. Power on the VMware connection server
3. Change the local ADAM value

a. Go to Run and enter “adsiedit.msc”

b. Select the OU “Server Groups” and select the CN="VDI pool name"

C. Change the value “pae-Disabled” – “1”

d. Reboot the VMware Connection Server

 

Reference:

http://blog.clearpathsg.com/blog/bid/155706/Disable-VMware-View-Pool-using-Powershell-PowerCLI

How to disable VMware View pool start up automatically

VMware View Don’t

Don't do item on VMware View:

1. Rename DataCenter name on vCenter - it will cause the view administrator malfunctions
2. Rename VM - since the VMware view administrator will not recongize this renamed VM
3. Rename folder contain VM which is created by vmware view administrator when create VDI pool, if the folder being rename, the view administrator will not able to manage this VDI pool.
4. VMware View - protocl error - login the VM via vSphere or RDP and reboot it. (don't use VMware Tools to restart the guest OS)

VMware View is very depend on vCenter, if vCenter manufuntion, many administration tasks cannot perform on VMware view administrator.

VMware View Don’t

VMware Horizon (VMware View) Misc Technotes

1. Link clone is require View composer

2. There are two type VDI VM – Full virtual machine (full clone) and link clone

3. VMware View require vCenter

4. View connection server – receive client connection and also management server for view

5. View security server – like a proxy (gateway) to allow client connect instead of connect the connection server directly. All client connection will be redirect from security server to connection server and then able to use VDI. The security server is no management role.

6. View storage accelerator -> reduce boot storm issue by using ESXi host cache.

7. Domain account on VMware View is used for join domain of VM child.

8. Transfer Servers -> for VMware view offline/local mode (e.g. laptop user need to use view offline)

9. The Transfer server for those local mode user to download (click-out) and upload (click-in)

10. Link clone by reference the persistent disk

11. View connection server

Blast Secure Gateway -> for using html5 to connect those VDI instead of using PCoIP

Disadv: The performance of the view will be decrease.

12. Guest System – prerequisites: Network needs DHCP

13. Link clone will be use the snapshot for link clone machine, it will not affect by parent disk change

14. Full clone (Full Virtual Machine) from VM template.

15. Desktop Delivery Model -> Manual Pool, Automated Pool and Terminal Service Pool

The Link clone is used for automated pool only

16. User assignment -> dedicate and floating

17. Recompose is I/O demanding

18. Link clone VM create from replica, the replica is full clone from parent image’s snapshot

19. Provisioning settings change need to Recompose

20. Recompose is required when parent VM update, otherwise those linked clone VM did not update

21. Recompose will recreate new replicate and delete the current replicate.

22. Refresh will not create new replicate

23. Rebalance will help to reassign the VM on different ESXi host and datastore via vMotion and DRS

24. If DRS disable, rebalance still work.

25. All Recompose, refresh and rebalance need down time. ALL VM will be poweroff.

26. Naming setting need to handle carefully, otherwise provisioning fail, then need to re-components.

27. Full clone must use sysprep

28. Persistent disk for redirect Windows user profile (Only available for dedicate VM – user assignment) Floating user assignment need to use windows folder redirection or roaming profile. VM also provide View Persona Management like roaming profile. The disposable disk for Windows temp file

29. Local session via vSphere client to connect VM, remote session via VMware View

30. ThinApps need to locate on file server, VM need to able to access this file server.

VMware Horizon (VMware View) Misc Technotes