TMO for on-premise windows client.

%3CLINGO-SUB%20id%3D%22lingo-sub-1713338%22%20slang%3D%22en-US%22%3ETMO%20for%20on-premise%20windows%20client.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1713338%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Community%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EOne%20of%20the%20customer%20has%20%26nbsp%3Bquery%20that%20Microsoft%20recently%20announced%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fvirtual-desktop%2Fteams-on-wvd%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ethis%3C%2FA%3E%20solution%20(Teams%20media%20optimization)%20for%20using%20Microsoft%20Teams%20on%20Windows%20Virtual%20desktop%20(WVD).%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThis%20solution%20is%20comprised%20of%20the%20below%20installation%2Fconfiguration%20on%20the%20RD%20Session%20Host%3A%3C%2FP%3E%3CUL%3E%3CLI%3ETeams%20WebSocket%20Service%3C%2FLI%3E%3CLI%3ETeams%20version%201.3.00.21759%20or%20higher%3C%2FLI%3E%3CLI%3EThe%20%E2%80%9CIsWVDEnvironment%E2%80%9D%20registry%20key%3C%2FLI%3E%3C%2FUL%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ECustomer%20currently%20can%20validate%20if%20above%20works%2C%20by%20starting%20Teams%2C%20going%20to%20your%20icon%20-%26gt%3B%20About%20-%26gt%3B%20Version.%20It%20should%20show%20something%20like%20%E2%80%9CWVD%20Media%E2%80%A6..%20%E2%80%9D%20However%2C%20on%20the%20client-side%20the%20%E2%80%9CWindows%20Desktop%20client%E2%80%9D%20(WDC)%20is%20required.%20According%20to%20this%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fvirtual-desktop%2Fconnect-windows-7-10%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Edocumentation%2C%3C%2FA%3E%20this%20client%20is%20different%20from%20the%20Remote%20Desktop%20Connection%20client%20(mstsc).%20The%20WDC%20will%20ask%20you%20to%20connect%20to%20a%20Workspace%20URL%3B%20or%20login%2Fsubscribe%20through%20your%20e-mail%20address.%20It%20uses%20a%20URL%20like%3A%20%3CA%20href%3D%22https%3A%2F%2Fnam06.safelinks.protection.outlook.com%2F%3Furl%3Dhttps%253A%252F%252Frdweb.wvd.microsoft.com%252Fapi%252Farm%252Ffeeddiscovery%26amp%3Bdata%3D02%257C01%257Cbalgan%2540microsoft.com%257Ce2ba76f4eddd4f8c966e08d85f9fca6c%257C72f988bf86f141af91ab2d7cd011db47%257C1%257C0%257C637364487201212903%26amp%3Bsdata%3DIJ%252Bi8p7HM91KGBZ%252BeBqwYx%252FZKhkNUO%252B%252BTttNV6bDYj4%253D%26amp%3Breserved%3D0%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Frdweb.wvd.microsoft.com%2Fapi%2Farm%2Ffeeddiscovery%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSTRONG%3EPersonal%20experience%20of%20the%20customer%2F%20understanding%20on%20how%20it%20works%3A%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E%3CSTRONG%3E%26nbsp%3B%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3EWhat%20customer%20has%20noticed%20is%20that%20%E2%80%93%20since%20Windows%2010%201809%20and%20Server%202016%20%E2%80%93%20it%E2%80%99s%20possible%20to%20redirect%20the%20local%20video%20capture%20device%20to%20the%20Remote%20Desktop%20session%20(basically%20redirected%20the%20encoded%20video%20stream%20directly%20to%20the%20server%2C%20so%20it%20could%20forward%20the%20stream%20where%20needed).%20This%20solution%20%E2%80%93%20in%20contrast%20to%20the%20older%20USB%20RemoteFX%20%E2%80%93%20allows%20for%20the%20local%20video%20to%20be%20directly%20streamed%20to%20Teams%20(or%20%E2%80%9Cproxied%E2%80%9D%20through%20the%20RD%20SH)%2C%20with%20low%20latency.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EOther%20participants%20will%20see%20this%20video%20stream%20without%20latency%20on%20their%20local%20device%20(assuming%20they%20run%20Teams%20locally)%3B%20since%20the%20%E2%80%98Upstream%20Video%E2%80%99.%20The%20video%20stream%20will%20show%20up%20at%20other%20participants%20that%20also%20use%20RD%20Session%20Host%20with%20a%20delay%2C%20because%20the%20stream%20is%20basically%20displayed%20%E2%80%98at%20the%20RD%20Session%20Host%E2%80%99%20and%20then%20captured%20and%20send%20to%20the%20RD%20client%20(the%20%E2%80%98downstream%20video%E2%80%99).%20So%20it%E2%80%99s%20not%20the%20original%20stream%20that%20is%20directly%20transported%20back%20to%20the%20RD%20Client.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSTRONG%3EQuestions%3A%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EFrom%20this%20experience%2C%20customer%20has%20a%20query%20that%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3COL%3E%3CLI%3EWhat%20new%20redirect%20%E2%80%98video%20capture%20devices%E2%80%99%20feature%20in%20the%20RD%20Client%20does%20with%20the%20upstream%20video%3B%20is%20what%20the%20Teams%20Media%20Optimization%20would%20do%20with%20the%20downstream%20video%3F%20In%20their%20case%20they%20have%20a%20client%20with%20an%20On-Prem%20Remote%20Desktop%20environment%20(comprising%20of%20a%20few%20RD%20Session%20Host%2C%20an%20RD%20Broker%20Server%2C%20RD%20Web%20and%20RD%20Gateway%20server).%20All%20based%20on%20Window%20Server%202019%20(but%20they%20could%20test%20this%20on%20Server%202016%20as%20well).%20This%20is%20basically%20a%20very%20similar%20setup%20as%20the%20WVD%20solution.%3C%2FLI%3E%3CLI%3EIs%20it%20also%20possible%20to%20use%20Teams%20Media%20Optimization%20in%20an%20On-Prem%20environment%3F%20Either%20using%20the%20RDC%20in%20combination%20with%20the%20webfeed%20from%20RD%20Web%3B%20or%20future%20MSTSC%20software%3F%20Is%20it%20on%20the%20roadmap%3F%3C%2FLI%3E%3CLI%3EWill%20the%20functionally%20only%20be%20available%20for%20WVD%20(and%20never%20become%20available%20for%20on%20On-Prem%20environment)%3F%3C%2FLI%3E%3C%2FOL%3E%3CP%3EAny%20guidance%20would%20be%20of%20great%20help.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1713338%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ETMO%20for%20on-premise%20windows%20client.%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1726386%22%20slang%3D%22en-US%22%3ERe%3A%20TMO%20for%20on-premise%20windows%20client.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1726386%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F301435%22%20target%3D%22_blank%22%3E%40Newlife%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F16300%22%20target%3D%22_blank%22%3E%40Alexander%20Ivanov%3C%2FA%3E%26nbsp%3Band%20the%20team%20would%20be%20a%20good%20one%20to%20answer%20your%20question%20here.%20I%20know%20Alexander%20is%20involved%20a%20lot%20with%20Teams%20for%20WVD%20and%20may%20be%20able%20to%20pass%20you%20some%20insights%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EBest%2C%20Chris%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1744959%22%20slang%3D%22en-US%22%3ERe%3A%20TMO%20for%20on-premise%20windows%20client.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1744959%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F169605%22%20target%3D%22_blank%22%3E%40Christopher%20Hoard%3C%2FA%3E%26nbsp%3B-%20Thanks%20for%20this%2C%20I've%20sent%20a%20message%20to%20Alexander.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Frequent Contributor

Hi Community,

 

One of the customer has  query that Microsoft recently announced this solution (Teams media optimization) for using Microsoft Teams on Windows Virtual desktop (WVD).

 

This solution is comprised of the below installation/configuration on the RD Session Host:

  • Teams WebSocket Service
  • Teams version 1.3.00.21759 or higher
  • The “IsWVDEnvironment” registry key

 

Customer currently can validate if above works, by starting Teams, going to your icon -> About -> Version. It should show something like “WVD Media….. ” However, on the client-side the “Windows Desktop client” (WDC) is required. According to this documentation, this client is different from the Remote Desktop Connection client (mstsc). The WDC will ask you to connect to a Workspace URL; or login/subscribe through your e-mail address. It uses a URL like: https://rdweb.wvd.microsoft.com/api/arm/feeddiscovery

 

Personal experience of the customer/ understanding on how it works:

 

What customer has noticed is that – since Windows 10 1809 and Server 2016 – it’s possible to redirect the local video capture device to the Remote Desktop session (basically redirected the encoded video stream directly to the server, so it could forward the stream where needed). This solution – in contrast to the older USB RemoteFX – allows for the local video to be directly streamed to Teams (or “proxied” through the RD SH), with low latency.

 

Other participants will see this video stream without latency on their local device (assuming they run Teams locally); since the ‘Upstream Video’. The video stream will show up at other participants that also use RD Session Host with a delay, because the stream is basically displayed ‘at the RD Session Host’ and then captured and send to the RD client (the ‘downstream video’). So it’s not the original stream that is directly transported back to the RD Client.

 

Questions:

 

From this experience, customer has a query that,

 

  1. What new redirect ‘video capture devices’ feature in the RD Client does with the upstream video; is what the Teams Media Optimization would do with the downstream video? In their case they have a client with an On-Prem Remote Desktop environment (comprising of a few RD Session Host, an RD Broker Server, RD Web and RD Gateway server). All based on Window Server 2019 (but they could test this on Server 2016 as well). This is basically a very similar setup as the WVD solution.
  2. Is it also possible to use Teams Media Optimization in an On-Prem environment? Either using the RDC in combination with the webfeed from RD Web; or future MSTSC software? Is it on the roadmap?
  3. Will the functionally only be available for WVD (and never become available for on On-Prem environment)?

Any guidance would be of great help.

2 Replies

@Newlife 

 

@Alexander Ivanov and the team would be a good one to answer your question here. I know Alexander is involved a lot with Teams for WVD and may be able to pass you some insights

 

Best, Chris

@Christopher Hoard - Thanks for this, I've sent a message to Alexander.