SurajRoy's Posts

Having 2 Connection servers eliminate single point of failure. In case if there is an issue with single Connection server and if you do not have a secondary Connection server, it would be a down situation.

This seems to be issue with RTAV not able to keep the keep alive message running. I would recommend opening ticket with VMware View support team to check if there are any HotPatch available or if taken care in future release.

Can you confirm if it is Instant Clone with persistent disk or Linked clone with Persistent disk. Here we are using persistent disk to save users profile. What if we rename the profile and then login to the same agent machine. Does it exhibit the same behavior? 

NOTE: Horizon view 7.12 is end of support. Make sure Connection server and View agents are running same version. You can test with View agent 7.13.1. In case if there is already an existing agent installed, uninstall the existing old agent > reboot the PC > reinstall the agent > reboot the PC. Agent unreachable can happen due to network issue or due to key pairing issue between CS and agent.  You can also go to cert store of the physical agent machine and uninstall horizon cert prior reinstalling the agent.

What type of agent machines are these: Linked Clone / Instant Clone Floating or persistent Are you using any kind of profile management like UEM / Persona or Persistent disk Did you optimized the Master image? Are you able to reproduce the issue if you login directly to agent machine via vCenter console using Domain User account or Local admin account?  

Client preference file is the best way to share to end user and replace it with their existing one. However, it is difficult to make the changes on multiple end users client machine.   You can consider the below setup. CS1: CS1.xyz.com ( internal FQDN) CS2: CS2.xyz.com ( Internal FQDN) Deploy 2 UAGs with HA enabled. UAG1 point to > CS1.xyz.com UAG2 point to > CS2.xyz.com UAG HA VIP URL : "vdi.mspartners.com". Hence, the above setup will avoid single point for failure at both UAG and Connection server level and at the same time, end users need not have to add any secondary URL as the URL still remain the same. If you want to know or have resource as how to configure or best way to configure UAG HA let me know.

There are couple of options Create separate pools for ThinClient where default protocol set to PCOIP. Use Horizon Smart Policies. Refer to https://docs.vmware.com/en/VMware-Horizon-7/7.13/horizon-remote-desktop-features/GUID-9B169CD0-3BEB-40E4-87D9-A5458BAF0BCA.html#:~:text=Horizon%20Smart%20Policies%20for%20user,can%20configure%20a%20triggered%20task. 

As per the release notes of Horizon 8.2:   The forwarding rules for HTTP requests received by Connection Server instances have changed at this release. If you have defined custom frontMapping entries in locked.properties, you should remove them before upgrading. If you wish to disallow administrator connections to certain Connection Server instances, then instead of defining custom frontMapping entries, add this entry to locked.properties: frontServiceWhitelist = tunnel|ajp:broker|ajp:portal|ajp:misc|moved:*|file:docroot   Also you can use the KB: https://kb.vmware.com/s/article/2088354       

As per the https://www.vmware.com/resources/compatibility/pdf/vi_view_guide.pdf Dell Wyse 3020 max support View 7.13. If the user is able to connect to his VDI desktop using Laptop or Desktop PC as client machine then it may be related to ThinClient only.

Well this issue can happen due to several reason.  Check if the view agent and VMware Tools installation order are correct. Make sure the power policy set on the Master image / Agent VM should be set to High Performance and display should be set to never sleep. Also check if the userint string value is correct. Refer to https://kb.vmware.com/s/article/1028975 

You can follow the below step to isolate the issue. Login to Agent VM via vCenter console as local admin. Go to device manager Uninstall the graphic driver And then connect to VDI desktop using View display protocol. If it work, it is related to graphic driver install with the agent. You can upgrade the agent to 7.13.1 and test if the issue still persist. Also note the display resolution set at the pool should be higher than the resolution set on the display monitors.

Curl command is the correct test done to check the cause of failure. You need to make sure the Destination Connection server under Edge setting Green. In case if it is not, it could be due to UAG unable to reach the Connection server via FQDN or IP or the SSL thumbprint may be incorrect. Sometime there is a space in front of the thumbprint which case copied while copying the thumbprint and it is hidden. Use the Delete/Space key to delete any hidden character infront of the thumbprint.