How To: Extend the TS Session Broker to Support VDI (Part 1)

a-foton » How To: Extend the TS Session Broker to Support VDI (Part 1)

a-foton » How To: Extend the TS Session Broker to Support VDI (Part 1) — Wed, 13 Aug 2008 07:13:56 GMT

PingBack from http://blog.a-foton.ru/2008/08/how-to-extend-the-ts-session-broker-to-support-vdi-part-1/

re: How To: Extend the TS Session Broker to Support VDI (Part 1)

stryqx — Wed, 13 Aug 2008 09:19:44 GMT

A smarter method of detecting bandwidth and latency and optimising display experience accordingly. Some way of feeding this back up to the application layer would be good.

Case in point: nothing worse than opening up IE in a session across a slow link only to find that the home page is set to a Flash-enabled site. Aargh!

re: How To: Extend the TS Session Broker to Support VDI (Part 1)

JamesNT — Thu, 14 Aug 2008 05:36:59 GMT

The ability to access the Terminal Services API with Visual Basic .Net 2008 without having to wrap a bunch of C classes. If the ability to do this exists, please let me know.

For example, I'd like to write a program that will loop through all connections and log off anyone that is not an Administrator - and block anyone from logging on that is not an Administrator. That way I can upgrade our app that we host via TS without some clueless user logging on and ruining the upgrade.

JamesNT

Interesting Links – 8/14/2008

Matt Johnson's Technical Adventures — Thu, 14 Aug 2008 20:05:52 GMT

Ask the Directory Services Team : MCS Talks Infrastructure Architecture joeware - never stop exploring…

re: How To: Extend the TS Session Broker to Support VDI (Part 1)

MikeH — Sat, 16 Aug 2008 13:40:56 GMT

Sorry for posting off topic!

But I have a real problem with RDP 6.1 on Windows Vista. I somehow screwed up my RDP-Sound which worked for a long time. Maybe you can explain the archtitecture and files and registry keys which are involved in playing RDP Sound on the server to the client.

When I play the sound on the console everything is fine, when I play the sound via RDP on another Vista machine I can't here any sound. I use the option to play the sound on the remote machine. There is no mute active. But there is also no visual indicator for playing sound. How to debug this case? Somehow I think it's muted but just doesn't show.

Maybe you can help. Thanks.

How to loop through all connections and log off anyone that is not an Administrator

Christa [MSFT] — Tue, 19 Aug 2008 00:29:47 GMT

Hi, James,

One option for the scenario you describe is to use the logoff command to log off all connections on the terminal server, then use change logon /drain to put the terminal server into drain mode. When a TS is in drain mode, users can only reconnect to disconnected sessions (which you already logged off), but you can still connect using a /admin connection.

Hope this helps,

Christa

re: How To: Extend the TS Session Broker to Support VDI (Part 1)

Shuba [MSFT] — Tue, 19 Aug 2008 02:03:23 GMT

MikeH,

What is the OS version of the machine you are conencting to? Also is this machine running server OS or Client OS? That makes a difference when you choose the option "Leave at remote computer" in your RDP client.

Thanks.

Shuba

re: Problem playing remote sound on RDP Client

MikeH — Sun, 24 Aug 2008 21:13:05 GMT

Hi Shuba,

thanks for replying.

The OS version of the machine I connect to is Vista SP1 Business. The Client OS is also Vista SP1 Ultimate, so both of them should speak the same language (protocol) RDP 6.1.

If you could provide technical details of registry keys and drivers in use for playing sound over RDP protocol would be great.

As stated before it has worked at the beginning but somehow something has happend.

Is there a way to remove the rdp audio drivers and let the system automatically reinstall the needed drivers? Maybe this way it is possible the get the right settings again.

I think my problem has something to do with the audio redirection as described by larry osterman:

Adding the concept of an audio endpoint also makes some scenarios like the RDP scenario I mentioned above orders of magnitude simpler. Before Vista, remote desktop audio was implemented with a DLL that effectively replaced winmm on the RDP server and redirected audio to the RDP client. With this architecture, it would have been extremely difficult to implement features like per-application volume and other DSP related scenarios for remote clients. For Vista, remote desktop audio was implemented as an audio endpoint. As such, applications running on a remote desktop server function just like they would on the local machine - instead of bypassing the audio engine in the client application, remote desktop audio runs through the audio engine just like local audio does, it gets redirected at the back end of the engine - instead of playing out the local audio adapter, the audio is redirected over the RDP channel.

source: http://blogs.msdn.com/larryosterman/archive/2005/09/21/472480.aspx

Thanks for your help.

Mike

Extending the free Session Broker that's built-in to Windows Server 2008

Brian Madden — Tue, 30 Sep 2008 21:33:22 GMT

Like many features of Windows Server, the TS Session Broker is a "platform" feature that provides basic functionality, but Microsoft wrote it in such a way that it's highly extensible. To that end, the Microsoft Terminal Server team has

re: How To: Extend the TS Session Broker to Support VDI (Part 1)

Geoff — Mon, 17 Nov 2008 09:48:54 GMT

Can you please provide the ability to have many people connect to the same RDP session for viewing. This could be used in a training scenario.

Extending the free Session Broker that's built-in to Windows Server 2008

Brian Madden — Fri, 13 Mar 2009 08:43:08 GMT