Microsoft Technology Licensing, LLC

Niraj Agarwala

Ido Miles Ben-Shachar

Ersev Samim Erdogan

Sriram Sampath

Tristan William Scott

Nelly L Porter

Ashwin Palekar

Meher P Malakapalli

Kevin Scott London

Artem Belkine

Raymond Matthew Reskusich

Alberto Henriquez

Mahadev K Alladi

Subhashini Raghunathan

Ayesha M Mascarenhas

Naga Vankata Rajagopal Ramadugu

Ramasamy Pullappan

An endpoint broker to provide application launch endpoints from multiple data centers having different tenancy sets. Upon accessing a request for an application launch endpoint connection for a user, the broker selects a data center, from amongst multiple data centers that have different tenancy sets, that is to provide an endpoint in satisfaction of the request. The endpoint broker identifies an endpoint from the selected data center, and then associates the identified endpoint with the user. The user is then provided access to the identified endpoint using the association. Thus, a user is not restricted to having an endpoint from a single data center. If there are concerns with providing an endpoint from one data center, an endpoint may be provided from another data center in a manner that is transparent to the user.

Endpoint data centers of different tenancy sets

Disclosed are techniques for providing a platform and application program interface (API) that leverages a terminal services session broker infrastructure to support third party plug-in applications. In a typical scenario, when a user requests for a connection to access third party plug-in applications, the application program interface may interact with the session broker process to identify sessions or suitable servers to which the user can be connected. The user may access the third party plug-in applications through the identified sessions or suitable servers.

Platform for enabling terminal services virtualization

Techniques for discovering, connecting to, disconnecting from, reconnecting to, updating, and removing workspaces are described. In one embodiment, a list of discovered workspaces is maintained on a user device. Shortcuts for resources corresponding to each respective one of the discovered workspaces are integrated into a user interface of the user device. A request to access one of the resources contained in one of the discovered workspaces is received. Responsive to receiving the request, a connection from the user device to one or more resource hosts containing the resources corresponding to the indicated one of the discovered workspaces is opened. Access from the user device to the resources stored on the resource host(s) corresponding to the indicated one of the discovered workspaces is enabled by presenting shortcuts for resources corresponding to the discovered workspaces as though they were local resources.

Integrated client for access to remote resources

Growing community of inventors

Bothell, WA, United States of America

Niraj Agarwala