1. Bug Reports
  2. Bugs
+1
Waiting for information

Block Gues Input not blocking

MJ Does IT 2 years ago • updated by Rishikesh Gajul (Product Manager) 7 months ago • 5

I just started a remote session with a remote client. While logging in I realized his keyboard is stuck, somebody must have left something on keyboard. Easy peasy, I blocked Guest Input and got around that. But then while actually trying to work I noticed the remote keyboard is active again, even though I blocked it, and it was still blocked.

ConnectWise Control Version:
Server Affected:
Host Client Affected:
Guest Client Affected:

Answer

Answer
Rishikesh Gajul (Product Manager) 7 months ago

Hi Jason,

Thank you for raising this issue with us. We have tested this on our side and could not reproduce it . I will strongly suggest you to contact our Support team for further assistance.

MJ Does IT 2 years ago

Update: so I got around that by un-blocking guest input and then blocking it again. It seems whatever blocking option is selected before log-in stops working after log-in, and has to be re-enabled again. I've seen the same thing happen with screen block, if I set it before log in, it doesn't stick. Is shows as being enabled but it isn't.

+1
Under review
Scott Linak 2 years ago
Jason Callahan 7 months ago

We're on 20.10.957.7556 and this is still broken. Blocking guest input doesn't do anything.

Answer
Rishikesh Gajul (Product Manager) 7 months ago

Hi Jason,

Thank you for raising this issue with us. We have tested this on our side and could not reproduce it . I will strongly suggest you to contact our Support team for further assistance.

Waiting for information
Rishikesh Gajul (Product Manager) 7 months ago

Customer support service by UserEcho