In our case, the end-points only have a single QHD monitor attached. I am hoping this will get escalated and I am contacted to work on the issue. We're using Horizon instant clones for VM deployment and App Volumes to deploy the flight sim applications to users. I would be more than happy to work with a Network Engineer to resolve this issue. This affects many people at work as well as vendors who use AT&T hotspots to connect to our resources. Funny how VMware and AT&T Business are supposed to be helping customers and businesses work, and then this happens. Either by a direct firewall deny policy or by not allowing the needed services/ports/applications in the firewalls that Horizon View requires. I just wondered if we could get any word from VMware when theyre going to release a client with native Apple.
#Vmware horizon client m1 code
This is AT&T blocking the VM workstation/service tunnel/proxy/port(s). so as I sit here on my M1 based MacBook Pro, every other business application Im using supports Apple Silicon and the only process I see on Activity Monitor which is still running emulated Intel code is the VMware Horizon client. This is also stated in the release notes of the current version. But I have no doubt this will be changed in the (near) future. Currently, it's running as an 'Intel' application, which means it uses Rosetta2. It works great, and I haven't noticed any (performance) issues. If I am using a Frontier DSL connection, I have no issues. I've been using my M1 powered MBP with the Horizon Client for some time now. If I use a Verizon hotspot or my work phone on Verizon (Android Client for Horizon), I have no issues. I have tried with both VMBlast and PCoIP protocols, and the same issue occurs if I try to use a web browser and the html5 option. This IS AT&T blocking the tunnel/proxy/port(s). I can connect to the Horizon View server, but as soon as I try to connect to a service or a VM desktop it always fails. My employer uses VMware Horizon View for remote access to VM workstations and services. It would be good to know if this is a regional firewall issue or a national one. This is affecting me, in the greater Seattle area. This is STILL an ongoing issue with AT&T wireless and connecting to VMware Horizon View services (NOT the initial connection to the server). I saw a few specific posts (regarding a certain model of hotspot), and posted in that thread, but then thought this should be a new topic not tied to a specific hotspot.