After nearly a month of back and forth with Parallels support, the following things are clear to me:
- Both Microsoft and Parallels share the blame for this issue.
- Microsoft has made changes to supposedly improve security around remote access.
- Parallels support knows that quick assist does not work reliably, but they will waste your time asking questions and making pointless workaround suggestions.
- Parallels support will not update the knowledgebase article that says to update Quick Assist versions from 2023 (
https://kb.parallels.com/en/129712) to point out that this is no longer a workable solution.
- Parallels support will not add a new knowledgebase article that describes the problem and the reasons for it.
- Parallels support is not interested in the fact that Quick Assist still works fine in VMware virtual machines.
I was sent the following link during the email exchanges with Parallels support:
https://learn.microsoft.com/en-us/a...assist-remote-session-ended-we-ended-the-conn. The most helpful answer in that post does a good job of explaining why Microsoft has made the changes that break Quick Assist and provides links to information about remote help capabilities with Microsoft Intune.
Reading those articles lead me to a description of Remote Assistance (
https://support.microsoft.com/en-us...sistance-cf384ff4-6269-d86e-bcfe-92d72ed55922). There are a number of web pages that describe how to actually use Remote Assistance. It is more difficult to use than Quick Assist, but it does work in a Parallels VM.
I am not sure the people I help with remote support sessions would be able to deal with Remote Assistance. Just entering the Quick Assist code and approving the access was often a challenge for therm.
Given the turmoil around VMware since the Broadcom acquisition, I don't think I will keep using VMware.
Looks like I get to spend a bunch of time testing out remte access alternatives.