Forum Discussion
Office, and potentially other apps, can launch other apps ... like a browser
Of course I know the myriad of things you've to know/do as I've been dealing with this since TS and before, and it is precisely because of that experience, that I'm looking for ways to "break things", I'm quite familiar with all those nuances.
But as this thing is in Preview, and this (the fact that the "system" ... ok the client ... by itself is uncapable of doing that level of restriction) is an old and annoyng thing, I think it's a good oportunity for the developers and program managers to deal with that at this stage.
I mean, think for a moment, the "marketing" that points to sell the promise of forgetting about all the RDS stuff (Gateway, Broker, Licensing, SQL Server, only to mention software) is certainly an attractive for us who have dealt with this over almost two decades: that definitely is a good thing.
It is also a good thing for "newbies", but arguably, a newby will feel this (what is stated in the subject) as a "lame failure" ... why in the heaven that happens? ... well, then it goes ... duh ... "it is still an RDS Session, so the user still has access to whatever is available in his session", but still the fact that the client renders the unwanted/unallowed app, "should" be something that this "as a service" solution should abstract the administrator from.
Having to continue dealing with this, with this new solution, is a miss.
And yes, there might be other thousand things to think about ... but my point is:
Newby says: Really?, you publish an RemoteApp and it is able to launch other apps that aren't published just because it invoked it?, Really?
Experienced says: Really?, still having to deal with this?
Don't get me wrong, I've learned to love RDS, it's fed me but, that doesn't prevent me from making some constructive criticism.
Abel Espino
For RDS admins WVD gives out of the box worries like Gateway management, certificates, high availability, SQL maintenance, configuration, MFA security and loads of other stuff. It is a selling point in itself already, even if locking down WVD is down to RDS admin. Many organizations will have an RDS GPO ready which can be applied to WVD with only minor tweaks, if any at all.
Since we are trying to make a voice... From my point of view, I still find it a big burden of needing to have classic AD / AD DS installed. I wish MS priorities Windows Server managed by Intune + working AAD Join to Windows Servers. Classic AD has been a good technology, it still is, but it has it's age already. There are steps in progress for that, like Windows Hello over RDP and Windows Server can already be joined to AAD in limited way, but its far from there yet to hold a serious production case 🙂