Forum Discussion
Remote assistance with Quick Assist is changing
Nathan_Pfeifer this is another enormous fail for Microsoft. The Experiences + Devices team needs to learn how the customers are using the tools before they make changes that remove all the benefits.
Our enterprise adopted Quick Assist as our remove support tool, completely replacing a third party product because:
1) It was native to Windows 10, and subsequently Windows 11.
2) NO ADDITIONAL COST or LICENSING required
3) No deployment tools required. Just point the end user to the search bar, type "quick assist" and click on the icon. As simple as falling off a log.
Russell Mosier and Bianca Taylor, from the Experiences + Devices team should not be excited. They should be ashamed that their company ignored the end user experience, in favor of software development ease.
There may be a compromise, but right now you are losing customers for that app. The Enterprise is still your bread and butter Microsoft, if you are going to empower the end user, you have to do so within the enterprise operational security models.
In our eyes, learn from your mistake and put it back into the OS, natively, where it belongs
Just the addition of adding alphanumeric to the code equation makes what was once a ridiculously simple way to connect that much more of a pain. "A as in apple S as in Sam, did you say F? NO S!, P as in Paul, did you say T? OMFG as in ... well never mind...
I didn't even have to tell them to type Quick Assist in the search box, it was TWO KEYTAPS, tap Windows and type the letter Q, in a sea of consumer fails, this was something Microsoft got right, big time. I too who only support regular consumers, was saving a TON OF $$ by not having to subscribe to overpriced remote control solutions.
I have so far not done the update, as I am waiting waiting, to make sure my end users who can barely use a mouse let alone deal with the Store can deal with the change, I may be over reacting but the alpha numeric is already a PIA.