Welcome to MSDN Blogs Sign in | Join | Help

Browse by Tags

All Tags » API   (RSS)

TS Session Broker Extensibility (Part 2)

In a previous blog post, Christa gave a high level explanation of the extensibility points we introduced to Session Broker (SB) in Windows Server 2008. In this post, we will dive a bit deeper to see how we can use SB Extensibility to build our own load

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

Terminal Services is both a collection of features and a platform for the TS team’s independent software vendor (ISV) partners. As a platform, we want to make sure that our components can be easily extended to support our partners’ vision

Dynamic Virtual Channels

An important goal of the Terminal Services (TS) team is to provide a product that can easily be extended by third parties to better meet their needs. While TS has always supported virtual channels, they had their limitations, including the limited number

TS-Teleport: Sample Instructions

Installation To install the sample the user needs to register both client plug-in and shell extension on the TS client and server machines respectively. NOTE: The VS support DLLs need to be copied to the same path as the sample DLLs. Please choose the

Writing a Desktop Sharing Application

Windows Desktop Sharing (WDS) API provides a rich set of API to share your complete desktop or just individual applications. Below is a step-by-step guide to write a sharing application. I have chosen C#/.Net to make things simpler and we will be using

Windows Desktop Sharing API

Windows Desktop Sharing API Basics Microsoft Terminal Services provides a public "Windows Desktop Sharing API" based on RDP to enable customers to write custom collaboration solutions in Windows Vista . These API's are available on all the SKU's starting
 
Page view tracker