Okay, I chanced getting locked out of this computer in question, and I tested these new permissions by checking/unchecking them for my own user account.
If I uncheck the "Keystrokes" permission, I am no longer able to type through LMI. (Although I can still access the on-screen keyboard.) Once I re-check the permission, I can type again.
If I uncheck the "Ctrl-Alt-Del" permission, the ctrl-alt-del button no longer functions. Once I re-check the permission, it works again.
I actually didn't bother testing the "blank screen" permission, because it seems straightforward.
I have not yet been able to ask my originally affected user to try again, so I can't be 100% certain that this was the cause of their issue, but it seems like it probably is.
So...yeah. Unless my experience is somehow unique, you probably won't want 15512 until maybe these new permissions can default to being enabled for users who already have remote control permissions.
Sorry for the uninvited "at", but since this seems kind of urgent...KateG ?
Hi etb, I apologize for the frustration. We have paused the deployment of 15512 earlier today due to this issue.
Good to know that the rollout has been paused! This new option is easily overlooked and also caused me a bit of frustration today until I'd noticed the version difference. If I've already granted a user remote desktop access, maybe the default keystroke option should be enabled in this instance?
