NickTT Tracker

Teams Mobile Calls to Teams Desktop App Drop

NickTT — Thu, 16 Nov 2023 19:30:24 GMT

We noticed a strange issue. If someone calls a user in Teams.. from the Mobile App and click answer... the call will drop immediately. However, if Teams is running on a non VDI machine, it works fine. Doesn't matter if the caller is external or internal to the company.

We are running Horizon 2306.

My Teams VDI version is 1.6.00.29964. Though we are seeing this same situation with other versions of Teams.

Looking at the Teams call logs I am getting "Response code: 410"

Teams Phone → Mobile App = Works

Mobile App → Teams Phone = Works

Mobile App → Mobile App = Works

Mobile App → Physical Desktop App = Works

Physical Desktop App → Mobile App = Works

Mobile App → VDI Desktop App = Drops

VDI Desktop App → Mobile App = Drops

Teams Mobile Calls to Teams Desktop App Drop

NickTT — Thu, 16 Nov 2023 18:20:18 GMT

We are running Horizon 2306.

My Teams VDI version is 1.6.00.29964. Though we are seeing this same situation with other versions of Teams.

Looking at the Teams call logs I am getting "Response code: 410"

Re: Ver 2209/2206/2203 not connecting. App self terminates. Only v2111.1 works.

NickTT — Fri, 13 Oct 2023 04:27:04 GMT

Same here... have had a case open for months. I have even tried updating the UAG, Connection Servers and Agents to the latest and greatest. No luck. Run the older client and it works fine.

Re: Horizon UAG wont connect to desktop on first try.

NickTT — Thu, 21 Sep 2023 12:16:47 GMT

No LB but we use a Public DNS traffic steering policy to flip DNS record if our primary GW is down to redirect traffic over our backup ISP.

We have a total of 2 GW and 2 Connect servers. However they are paired as a 1 to 1 match. IE GW01 is paired to CS01. We understand that users will have to reconnect remotely, as we only about 50 at any given time, if there is some sort of connectivity issue with the primary Gateway. I actually worked with VMware support on this setup and got their blessing. So the GW have no HA configurations on them.

The system had been working fantastic for years till we upgraded to 2212. We had the clients and agents running 8.5 or under for some time while the servers were running 2212. We finally upgraded to 8.8 and started having issues with the remote access. We pushed out 8.8 for the improve MS Teams Support.

The strange part is that it only fails on the first try.... after that... no issues. Almost like DNS is failing to resolve or something.

Horizon UAG wont connect to desktop on first try.

NickTT — Mon, 18 Sep 2023 17:07:14 GMT

Recently we started running into issues of our remote workers having to connect twice to their VM when remote going through a gateway. User will get a gateway error message but then when they try a second time it connects.

Horizon Client Returns:
vdpconnect_gateway_error: the connection to the remote computer encountered a gateway error.

Horizon 2212 (8.8.0 build - 21073894)

Unified Access Gateway Appliance v22.12

Agents 8.8.0-21067308

I have had a ticket open for some time.. anyone else see this?

Re: Horizon, Teams and Yealink MP50

NickTT — Fri, 15 Sep 2023 13:25:19 GMT

We returned them... Yealink buttons don't work correctly in VDI. Wouldn't dial numbers correctly.

Teams Phone - "Connect a Device"

NickTT — Fri, 15 Sep 2023 13:16:05 GMT

When Teams runs locally on a laptop and you have a desk phone like the Poly CCX505 or CCX600, you can "Pair" the device to Teams so you when you make calls in Teams it actually remotely controls the phone and send connects the call that way. It gives users a nicer experience in the long run because they don't have to guess what device to use, be it PC audio or the Phone. Is something like that possible with Teams in Horizon?

Re: Horizon, Teams and Yealink MP50

NickTT — Tue, 15 Aug 2023 17:12:31 GMT

We got a few to test them out. Will let you know in a few weeks.

Re: Agent Upgrade Not Available

NickTT — Tue, 15 Aug 2023 14:20:13 GMT

We upgraded to the the PLUS license and have the required license... however it still shows it needs to be enabled but doesn't say how or where. We only use Manual Desktop Pools. Any info on how to enable this?

Re: Teams Human Interface Devices

NickTT — Mon, 05 Jun 2023 17:05:48 GMT

Started working through the gateways too for me so we are in good shape.

Static DNS Removed after Reboot.

NickTT — Mon, 05 Jun 2023 12:40:22 GMT

We are seeing this issue randomly. About 1 machine a day. We use Cisco's Umbrella Client for secure DNS. So all VMs have their DNS set to local host IP, 127.0.0.1. Starting earlier this year we have seen machines boot up after a restart with no DNS entry at all. Just empty. To resolved the issue we manually set DNS back to our local Domain controller's IP and it will start resolving again. The Umbrella client will then check in and reset DNS back to 127.0.0.1. This is only happening to Virtual machines. Doesn't matter if it's a server or workstation. I suspect it's something going on with VMware tools. I will see an application event log event from VMUpgradeHelper right before I see events where the domain or other systems are not reachable.

Event:  Restoring network configuration. 
Source: VMUpgradeHelper
EventID: 258

AND

Event: Restored network configuration.
Source: VMUpgradeHelper
EventID: 271

Re: Teams Human Interface Devices

NickTT — Wed, 03 May 2023 16:58:11 GMT

Yep, noticed it started working while in the office. However, I also noticed when working remotely going through the gateway the buttons do not work. Anyone else seeing this issue?

Re: Teams Human Interface Devices

NickTT — Tue, 07 Mar 2023 17:41:10 GMT

Any update or comment to my question @sprabhu11 ?

Re: Teams Human Interface Devices

NickTT — Thu, 16 Feb 2023 16:51:40 GMT

@sprabhu11

Are there any special configurations we should stage ahead of time? For instance... I have "Allow Auto Device Splitting" enabled and set to Allow in Group Policy.

Re: Teams Human Interface Devices

NickTT — Thu, 16 Feb 2023 16:46:27 GMT

Wonder if this is related....

TM510646: February 15, 2023 2:44 PM

Title: Teams users with Human Interface Devices (HID) may experience persisting dial tones or other degraded functionality User impact: Users with HIDs attached when disconnecting from a Teams meeting may subsequently experience degraded functionality. More info: This issue only affects the Teams desktop client and Windows Microsoft Teams Room (MTR) devices, and only when those devices had an HID connected during a recently terminated meeting. Users may experience the following impact scenarios: - Device peripheral call indicators, such as an LED display, may not turn off as expected when a Teams meeting ends. - For users utilizing on-premises Skype for Business with Microsoft Teams in coexistence mode, a persistent dial-tone during Microsoft Teams calls may be experienced. - If users were muted during a meeting, users may experience being unable to unmute during subsequent meetings. Users may restart their Microsoft Teams client to mitigate this impact. This commonly affects users with a HID such as an audio headset. More information regarding HIDs can be found here: https://learn.microsoft.com/en-us/windows-hardware/drivers/hid/ While the fix is being deployed, we can disable the HID feature for your organization to temporarily mitigate this issue if requested. However, users won't be able to use Mute/Unmute or Hook/OffHook controls from their headset devices until the full fix is available. Current status: The fix initiated its deployment as expected on Tuesday, February 14, 2023, and we've confirmed that it has been deployed to 50 percent of the affected environment. Based on current progress, we now expect that the deployment will complete and the issue will be resolved by tomorrow, Thursday, February 16, 2023. Users may begin to experience relief from impact as they receive the fix, and we'll continue to monitor its progress until the deployment has completed in full. Scope of impact: This issue only affects Microsoft Teams users with a HID connected, and only impacts the Microsoft Teams desktop client and Windows MTR devices. Start time: Tuesday, December 6, 2022, 8:34 PM (12/7/2022, 1:34 AM UTC) Estimated Time to Resolve: Based on current progress, we expect this issue to be resolved by Thursday, February 16, 2023. Preliminary root cause: Changes to improve the HID feature for Microsoft Teams users introduced a code issue, causing degraded functionality to some users with these device types attached to their Teams client. Next update by: Thursday, February 16, 2023, 6:00 PM (11:00 PM UTC)

Host Profile Equivalent for CoreDump Settings

NickTT — Wed, 01 Feb 2023 13:36:23 GMT

Is it possible to set this in a host profile?

esxcli system coredump file set --smart --enable true

Re: Teams Human Interface Devices

NickTT — Wed, 25 Jan 2023 16:40:01 GMT

OK.... I am not crazy!! I saw the same thing. It then broke again but I thought it had something to do with the new laptop I got or a GPO change. I haven't been able to get it working again.

Currently on:

You have Microsoft Teams Version 1.5.00.21463 (64-bit). VMware Media Optimized.

Re: MS Teams New Meeting experience on Horizon - rolling out now (but doesn't work?)

NickTT — Thu, 29 Sep 2022 12:04:36 GMT

We had a few users that clicking the "Restart Teams" didn't do anything. We resolved the issue by deploying a job that completely uninstalls Teams, deletes any folders left behind and then re-installs the latest version of Teams with the -ALLUSER -ALLUSERS switches. Since then, we have been fine.

Re: Enable software acoustic echo cancellation for Media Optimization for Microsoft Teams

NickTT — Wed, 28 Sep 2022 16:50:35 GMT

Native Teams on the laptop works fine.

Re: Jabra Heads and other USB Audio Devices in Horizon Best Practice

NickTT — Tue, 27 Sep 2022 18:56:47 GMT

Anything new here on HID controls? I was checking out Composite USB Devices splitting policies to see if I could git HID controls to work with Horizon, Teams and Jabra.

Configuring Device Splitting Policy Settings for Composite USB Devices (vmware.com)