Launching soon: The world's first vendor agnostic bug scrubLearn more & join waitlist
OPERATIONAL DEFECT DATABASE
...
...
Microsoft Teams optimization for Horizon does not enableA "VMware Media Not Connected” error message is displayed within Teams. In Teams logs, we see entries similar to the below: 2023-03-09T22:00:21.558Z Err connectToHorizon(): Port is not valid 2023-03-09T22:00:16.561Z Err connectToHorizon(): Port is not valid 2023-03-09T22:00:16.560Z Inf intervalMs 5000 timeout undefined 2023-03-09T22:00:16.557Z Inf onVMEvent(): Fire event = {"event":"vdiClientDisconnected","reason":"endpointUnsupported"} 2023-03-09T22:00:16.556Z Inf enumerateDevicesShim(): Use fallback mode. 2023-03-09T02:58:36.097Z Inf connectToHorizon(): port is 0 2023-03-09T02:58:31.095Z Inf onWebSocketClose(): Websocket closed 2023-03-09T02:58:31.095Z Inf intervalMs 5000 timeout undefined 2023-03-09TT02:58:31.091Z Inf onVMEvent(): Fire event = {"event":"vdiClientDisconnected","reason":"endpointUnsupported"} 2023-03-09T02:58:31.086Z Inf enumerateDevicesShim(): Use fallback mode. Similar entries to the below are seen in the vmware-html5Server-extra-*-*.log file: This file is located in the following directory: C:\Windows\TEMP\vmware-SYSTEM 2023-03-05T15:53:19.426-08:00| html5mmrServer| I125: [0x000016AC][MainServerChannel::Stop] this = 0x2748AEDFE90 Stopped the server 2023-03-05T16:55:53.265-08:00| html5mmrServer| I125: [0x000016AC][MainServerChannel::OnChannelStateChanged] this = 0x2748AEDFE90 Channel state = 0. 2023-03-05T16:55:53.265-08:00| html5mmrServer| I125: [0x000016AC][MainServerChannel::Stop] this = 0x2748AEDFE90 Stopped the server 2023-03-05T16:55:53.265-08:00| html5mmrServer| I125: [0x000016AC][HTML5MMRObj::~HTML5MMRObj] this = 0x27488FC6ED0 2023-03-05T16:55:53.265-08:00| html5mmrServer| I125: [0x000016AC][HTML5MMRObj::~HTML5MMRObj] this = 0x27488FC6FA0 21-03-30T11:15:20.386-06:00| html5mmrServer| I125: SOCKET getaddrinfo failed for host view-localhost: No such host is known. 2023-03-30T11:15:20.386-06:00| html5mmrServer| I125: SOCKET Could not resolve listener socket address. 2023-03-30T11:15:20.386-06:00| html5mmrServer| I125: [0x00002E10][WebSocketServerImpl::StartServer] this = 0x1E1AFD07300 Failed to listen to the socket. 2023-03-30T11:15:20.386-06:00| html5mmrServer| I125: [0x00002E10] = Failed to start server. 2023-03-30T11:15:20.386-06:00| html5mmrServer| I125: [0x00002E10][HTML5Server::StartServer] this = 0x1E1AFD07020 Websocket port number is 0 Enabling Teams Logging:Settings > General, and select "Enable logging for meeting diagnostics (requires restarting Teams)"Note: MS Teams diagnostic logs can be obtained via Crtl + Alt + Shift + 1 on the MS Teams window. The files will be created in the Download folder.
This issue occurs due to various reasons. These include, but are not limited to: TCP port 9427 is blocked between Agent & UAG/Security Server.The Agent machine contains an invalid or no entry in the hosts file.
Open port 9427 for MMR between the appropriate endpoints, see VMware Horizon ports and network connectivity requirements (1027217).Make sure the local hosts file on your agent machine contains ‘view-localhosts’ as the entry by default, if not, change it to 127.0.0.1 view-localhost - This is required for MMR functionality. File Location: C:\Windows\System32\drivers\etc\hosts
For more detailed information on MS Teams optimization setup, visit the below link:Microsoft Teams Optimization with VMware HorizonThis is a child article of Known Issues with Horizon View and Microsoft Teams (90693)