BenFB's Posts

At a minimum the Horizon Agent needs to be able to communicate with the connection servers on TCP 4001/4002 (Depending on your configuration only one of these is needed). Then it depends on if you are using tunneling/security servers/UAG, the display protocol and the communication you want to allow. Can you provide us with more details of your deployment?

Horizon 6.x goes end of support in just over two weeks on 2019/06/19. I'd get an SR in with VMware now to troubleshoot your issue. In parallel you should prioritize an upgrade to 7.x. https://www.vmware.com/content/dam/digitalmarketing/vmware/en/pdf/support/product-lifecycle-matrix.pdf

We've been struggling with the same debate. However, in our case all of our virtual desktops are persistent. We are working towards non-persistent and until we get there we are holding off on instant clones. We are also waiting to see what VMware does as they announced a few years ago that they intend to deprecate linked clones eventually. You should factor in the other features that come with Enterprise to ultimately decide if it's worth it. I'd say it will always benefit you to be on Enterprise to have access to all features. You might also consider looking in to the new license model that allows for running Horizon both on and off prem.

Are you logging off or disconnecting? Linked clones or instant clones? Are these persistent or non-persistent desktops? Which version of vCenter? Which version of ESXi? Which version of Horizon View Connection Servers? Which version of VMware Tools? Which version of Horizon Agent? Are UAG or Security Servers being used?

You only need a my VMware account to create an SR which you would have needed for the trial. Either call (877) 486-9273 or submit one online and they should be able to help you out. Alternatively you can determine who your local rep is and contact them.

I'd go with 10ZIG or Dell/Wyse ThinOS devices. We've tested both and been happy with them. Depending on the model they can do both Blast/PCoIP along with Citrix and RDP which provides a lot of flexibility.

I would consider those false positives that can be ignored. For all of the communication you listed there are additional safeguard in place. Port 4172 is for PCoIP. If you must you can replace the PCoIP Secure Gateway (PSG) certificate. SSL certificate error when scanning PCoIP secure gateway port 4172 (1038762) Configure the PCoIP Secure Gateway to Use a New TLS Certificate This section of the documentation covers how Horizon performs other means of validation for the message bus traffic on ports 4001 and 4002. Certificate Thumbprint Verification and Automatic Certificate Generation Port 4101 is used for the connection server JMS traffic. Make sure you are in Enabled or Enhanced mode. Firewall Rules for Horizon Connection Server Understanding Communications Protocols Message Security Mode for Horizon 7 Components Global Security Settings for Client Sessions and Connections Change the JMS Message Security Mode to Enhanced ​ Horizon Messaging

You need to reviewed the VMware compatibility matrices to determine the order. You may have to jump through multiple upgrades of different components. Verify the order to upgrade the components. Update sequence for vSphere 6.0 and its compatible VMware products (2109760) Update sequence for vSphere 6.5 and its compatible VMware products (2147289) Update sequence for vSphere 6.7 and its compatible VMware products (53710)​ Verify the Horizon upgrade path is supported. VMware Product Interoperability Matrices Verify compatibility with vCenter, ESXi, VMware Tools and UAG if you use them. VMware Product Interoperability Matrices VMware Product Interoperability Matrices VMware Product Interoperability Matrices VMware Product Interoperability Matrices If you use Composer verify your database versions are supported. VMware Product Interoperability Matrices Verify compatibility with any endpoints/Zero/Thin Clients that you have. VMware Compatibility Guide - Horizon (Thin Clients) Search

I know there are some known issue with Global Entitlements after upgrading to 7.8.0. Are you possibly using a read-only admin account? Release Notes for VMware Horizon 7 version 7.8 Users that have the Administrators (Read Only) role cannot see View Configuration > Cloud Pod Architecture in Horizon Administrator or Settings > Cloud Pod Architecture in Horizon Console. Workaround: None. From the Horizon Console you can manage Global Entitlements. Setting Up and Managing Cloud Pod Architecture in Horizon Console You can also try using lmvutil. Administering Cloud Pod Architecture with lmvutil

I would recommend opening an SR while you still have access to support for 6.x to get their insight. What is the hold up on upgrading to 7.x? That can typically be accomplished within just a few hours.