PENDING Anyone having remote mouse issues

[rtruss]

Is anyone having techs report mouse issues using remote control post 2111 update? It appears to happen mostly with users who have 2 (might be 3) or more monitors.

 

[GSTERLING]

Yes this has been happening to us. The mouse pointer does not match up to where you click.

 

[Tradewell]

Is anyone having techs report mouse issues using remote control post 2111 update? It appears to happen mostly with users who have 2 (might be 3) or more monitors.

We are seeing the same thing. KB12959506 has been applied and current client version is 5.00.9068.1012.

 

[Tradewell]

OK I have a support call opened with Microsoft. They claim the Hot Fix for MECM 2111 "KB12959506" with the client update to 5.00.9068.1012 fixes the issue, not. I found another article from yesterday and it works. So long as the system you remote into has scaling set to 100% on all of it's monitors it works. If just one of the monitors is set to a different scaling percentage the mouse is off. I have sent this information to MS and I'm waiting on their reply.

 

[ConfigMgr Dude]

We opened a Microsoft support case, even if we are running 2111 + latest fix, the problem persists. The temporary workaround for this was to use an older version of CmRcViewer.exe and DLLS but this didn't work fine on all computers. They said that Microsoft will fix this in 2203 and a hotfix update for 2111

 

[Prajwal Desai]

We opened a Microsoft support case, even if we are running 2111 + latest fix, the problem persists. The temporary workaround for this was to use an older version of CmRcViewer.exe and DLLS but this didn't work fine on all computers. They said that Microsoft will fix this in 2203 and a hotfix update for 2111

Thanks for the update. Wasn't aware of this.

 

[Tradewell]

What I got back from support.

Thanks Paul for your patience.

I was able to repro this issue in my lab and opened a Bug for product group. It is build related issue or regression bug.

Product group has fixed the issue and will be released in next hotfix. Since it is build issue so we cannot provide workaround for it.

Since this issue was related to known code defect, the case will be closed as "non-decrement", and you will not be charged for the support incident.

Please let me know if you have any other question.

Thanks, Microsoft Tech

 

[GSTERLING]

Thanks!