As per the release notes of latest View Client 2106 it support Windows 10 version 21H1 SAC support and earlier. https://docs.vmware.com/en/VMware-Horizon-Client-for-Windows/2106/rn/horizon-client-wi...
See more...
As per the release notes of latest View Client 2106 it support Windows 10 version 21H1 SAC support and earlier. https://docs.vmware.com/en/VMware-Horizon-Client-for-Windows/2106/rn/horizon-client-windows-2106-release-notes.html#keyfeatures Not sure if the client has been tested against Windows 11
When you say end users using Spectrum having issue. What is the issue? Does session disconnect during session? OR End users are not able to connect to VDI using Blast?
It is the latest photonOS behavior. if the connection server FQDN is .local we have 2 options. Use IP address of Connection server instead of FQDN OR use FQDN and add details under Host Entry und...
See more...
It is the latest photonOS behavior. if the connection server FQDN is .local we have 2 options. Use IP address of Connection server instead of FQDN OR use FQDN and add details under Host Entry under Edge settings > More info
If the user is entitled for more than 1 pool, disconnect will not exit the view client. If only 1 pool is entitle and still after disconnect the client is open we have 2 options. - At pool let set ...
See more...
If the user is entitled for more than 1 pool, disconnect will not exit the view client. If only 1 pool is entitle and still after disconnect the client is open we have 2 options. - At pool let set logoff after disconnect immediately - Ask the user to close the view client after disconnect from session.
Make sure you are using View agent 7.10 or higher and latest view client. Also test this on any Windows Client machine HKEY_LOCAL_MACHINE\Software\Policies\VMware, Inc.\VMware VDM\Client AllowD...
See more...
Make sure you are using View agent 7.10 or higher and latest view client. Also test this on any Windows Client machine HKEY_LOCAL_MACHINE\Software\Policies\VMware, Inc.\VMware VDM\Client AllowDisplayScaling (REG_SZ) Value: true
Option 1: Have individual View Pod for individual customer. This is applicable if you have separate vCenter for each customer. However, in your case it seems there is only 1 vCenter. You can cr...
See more...
Option 1: Have individual View Pod for individual customer. This is applicable if you have separate vCenter for each customer. However, in your case it seems there is only 1 vCenter. You can create separate pool for separate customer and select Hide Domain from the Global settings to make sure during login the domain is not listed so that end users get confused which domain to select. However, I am not sure if this would be supported by VMware, but can be tested.
what is the agent OS version ( Windows) and agent version? NOTE: There is an issue with WDDM driver that comes with VMware Tools 11.0.0 - 11.2.5 and Windows 10 20H2. Test with latest VMware Tools...
See more...
what is the agent OS version ( Windows) and agent version? NOTE: There is an issue with WDDM driver that comes with VMware Tools 11.0.0 - 11.2.5 and Windows 10 20H2. Test with latest VMware Tools as it will have latest SVGA driver.
Are you able to connect to Adam database Refer to https://kb.vmware.com/s/article/2012377 Check if you are able to connect using the view admin account or not or it error out. Also check if there...
See more...
Are you able to connect to Adam database Refer to https://kb.vmware.com/s/article/2012377 Check if you are able to connect using the view admin account or not or it error out. Also check if there is any LDAP collision. Refer to https://docs.vmware.com/en/VMware-Horizon/2006/horizon-console-administration/GUID-BA4C28C2-B897-470C-A703-A3C187DC12A8.html NOTE: Take back of the adam OR snapshot of the connection server prior any troubleshooting.
Try the below step in test pool or test machine: 1) Uninstall the Horizon agent 2) Reboot and make the below registry change [HKLM\SOFTWARE\VMware, Inc.\VMware VDM\Agent\Configuration]Invalidate...
See more...
Try the below step in test pool or test machine: 1) Uninstall the Horizon agent 2) Reboot and make the below registry change [HKLM\SOFTWARE\VMware, Inc.\VMware VDM\Agent\Configuration]InvalidateMachineIdentity:REG_SZ=”false” 3) Install the agent back and validate the status
I hope you have gone through the below KBs: Changing IP: https://kb.vmware.com/s/article/2051923 Changing Name: https://kb.vmware.com/s/article/2000357
For UAG HA to work you need 3 Public IP ( Which you have) and 3 Public DNS resolving to those 3 Public IP. Example: UAG 1: Public IP: 171.10.10.1 Public DNS resolving to above IP: UAG1.xyz.co...
See more...
For UAG HA to work you need 3 Public IP ( Which you have) and 3 Public DNS resolving to those 3 Public IP. Example: UAG 1: Public IP: 171.10.10.1 Public DNS resolving to above IP: UAG1.xyz.com UAG 2: Public IP: 171.10.10.2 Public DNS resolving to above IP: UAG2.xyz.com VIP: Public IP: 171.10.10.100 Public DNS resolving to above IP: myvdi.xyz.com On each UAG point the tunnel URL and IP to their own public IP and public DNS. So under UAG1 the PCoIP External URL: 71.10.10.1 and for UAG2 the PCoIP External URL should be 71.10.10.2 The end users only need to remember " myvdi.xyz.com" and when they click on the desktop to launch the launch, the client will talk to specific UAG and need have to go through VIP. NOTE: UAG HA VIP cannot handle UDP traffic 4172
I come across this issue and below are my findings. Refer to KB: https://kb.vmware.com/s/article/82276 It is caused by windows 10 compatibility issue with WDDM driver provided by VMware tools 11.2...
See more...
I come across this issue and below are my findings. Refer to KB: https://kb.vmware.com/s/article/82276 It is caused by windows 10 compatibility issue with WDDM driver provided by VMware tools 11.2.5 Resolution: Upgrade VMware tools to 11.2.6 or higher OR Run Optional update as per KB and make sure the SVGA driver is 8.17.2.13 or higher
Connection server load balance the session using some load balancing mechanism. To check you can disable all RDSH host on the Farm EXCEPT 1 and then check. This will make sure no load balancing take...
See more...
Connection server load balance the session using some load balancing mechanism. To check you can disable all RDSH host on the Farm EXCEPT 1 and then check. This will make sure no load balancing take place and hence will force the session with that 1 available RDS host. If the issue do not occur, then yes, it is related to load balancing. Also you can enable 1 RDS host at a time and check which one is causing issue. For more info please refer to https://docs.vmware.com/en/VMware-Horizon-7/7.13/horizon-published-desktops-applications/GUID-6EDE18E6-9603-4585-9CFC-5544DBA09198.html
