Mouse of presenter slow/unusable/flickering when sharing screen in Microsoft Teams. Unusable when giving control. Via Remote desktop

Anonymous
2020-03-26T15:19:57+00:00

Hi,

We experience the following:

  1. Person "Alice" starts a Teams-Screensharing with "Bob" via the Chat->Screensharing
  2. The mouse of "Alice" is now reacting slow and less usable. It is shaking / flickering. When Alice moves the mouse, the cursor lags behind or shakes.
  3. When "Alice" gives "Bob" control, Alice cannot move her own Mouse-pointer anymore. Bob, who has control, can move the mouse and work on Alice' desktop. Alice cannot move her mouse, so she can't revoke screensharing and also not take away control from Bob. Only if Bob gives up control, Alice can use her desktop again.

When the presenter tries to move her mouse pointer, it is shaking, flickering, slow, dragging. When in addition "giving control" to someone, the mouse is unusable and the remote controller has all control, whereas the presenter loses all mouse control.

(adding synonyms here for people who also search for this problem)

Circumstances under which this happens:

  • Microsoft Teams runs on two PCs "PC-A" and "PC-B" in the same local company network. The PCs are close to each other, no network latency. PC-A (Alice) shares the desktop with PC-B (Bob).
  • Alice sits physically in front of an Acer Laptop and uses VPN, a home internet connection, and Microsoft Remote-Desktop (mstsc.exe) to connect to her "PC-A", which is at the company. Between the Acer Laptop and PC-A there is network latency and limited bandwith as her internet at home is consumer-grade.
  • Bob sits physically in front of his "PC-B".
  • Bob could also be logged in via VPN&remote-desktop like Alice if he works from home-office. The problem is the same.
  • All are Windows 10 with recent patch-level.
  • The two screens of her Laptop and PC-A have different resolutions.
  • Teams is a fresh install a week ago.

If Alice and Bob sit physically in front of PC-A and PC-B, the problem does not occur. Then, there are mutliple mouse-pointers shown and screen sharing with Microsoft Teams works fine.

I suspect it is related to remote desktop (mstsc.exe) and the way that the mouse is moved when being remotely connected. Screen resolutions differ, too.

Did anybody experience this, too?

Any idea how to resolve it?

We could start Teams on the Acer Laptop, but that would open other problems.

kind regards

Leo

Microsoft Teams | Microsoft Teams for business | Other

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

50 answers

Sort by: Newest
Most helpful Newest Oldest
  1. Anonymous
    2020-04-01T14:15:40+00:00

    We have the exact same problem - poor mouse reaction, rubberbanding as soon as the screen is shared.  Disabling the firewall did not help.

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments
  2. Anonymous
    2020-03-31T18:13:09+00:00

    We're having the same issue. One user reports that the problem cam soon after an MS update on 03/20/2019 we're looking into downgrading to see if this resolves the issue.

    We also have FW disabled by default so this did not solve or help for us.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  3. Anonymous
    2020-03-31T16:22:59+00:00

    Update:

    It is also happening with users that have the Firewall unlocked.

    kind regards

    Leo

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  4. Anonymous
    2020-03-27T16:51:33+00:00

    Hi @Marvin,

    Thanks for the clarification. As both Remote Desktop and Teams are from Microsoft, maybe testing Teams when logged in via Remote Desktop is something you could do.

    Update from today with another piece of information that may help:

    1. The bad mouse-flicker still happened today between Alice and Bob as described above.
    2. We noticed that "Alice" had on her computer not authorized Windows Defender Firewall yet to allow connections outgoing from "Teams.exe". This can happen because the Defender Firewall only asks once, when first sharing a screen, if Teams should be allowed to do outgoing connections. When the user clicks "cancel" on the Firewall dialog, it never pops up again - but screensharing and audio connections still work, but more badly.
    3. After logging in as Admin on Alice' computer and configuring Windows Defender Firewall to allow teams.exe, her experience improved a lot.

    So the cause may be related to how Teams and Firewall do work together.

    I will track this further and keep adding information if I get them for any other person out there experiencing this issue.

    best

    Leo

    Was this answer helpful?

    0 comments
  5. Anonymous
    2020-03-27T12:12:20+00:00

    Hi Leo,

    Based on your description, this issue doesn't occur when user doesn't use remote desktop connection. In this scenario, the issue should be related with remote desktop function instead of Teams request control function. Regarding the remote desktop feature, it's out of our knowledge base and support boundary since we focus on Teams services and issues. I'll try to consult our related team to check if they have any experience. But still, for users, it's suggested to control their own PCs to share the screen with each other.

    Regards,

    Marvin

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments