MicrosoftAs far as I understand the response not every bit of WAC is really a task of the WAC Team but unfortunately has internal dependencies to other PGs. See RDP issue.
As a user it's not comprehensible, because at the end of the day the experience and expectation is that this tool should ease the workflow.
I am quite successful in teaching WAC and promoting it. Basically, in an ideal world we should disable RDP altogether for security reasons. But we aren't there yet. Few critical things still need RDP 😞
Sconfig for example and other commands that are interactive and don't run remotely but only in local PS or cmd.
Agree on all your statements and thanks for the feedback about it.
As said previously the communication about this project and product should get more open. Currently it's in a "free gift mode", you never knew what you get after 6 months of waiting.
I hope this could change.
The idea about open source sounds good, but if the statements of the involved other PGs are true in core features and extensions believe it's complicated to moderate the code. We have great other examples on github from Microsoft though.
The difference it's only one specific product.
Like Exchange CSS, PowerToys, PowerShell, winget etc.
Maybe it's a good idea to have a survey why people still need to bother with RDP and this Bug in WAC and next to fixing it, eliminate reasons to use RDP.
