Patent application number | Description | Published |
20120084570 | Remote Resources Single Sign On - Exemplary techniques for enabling single sign-on to an operating system configured to conduct a remote presentation session are disclosed. In an exemplary embodiment, a user credential can be encrypted using an encryption key generated by a remote presentation session server and sent to a client. The client can send the encrypted user credential to the remote presentation session server. The remote presentation session server can decrypt the user credential and use it to log a user into an operating system running on the remote presentation session server. In addition to the foregoing, other techniques are described in the claims, the detailed description, and the figures. | 04-05-2012 |
20130067100 | MULTI-DESKTOP INTERACTION USING NESTED REMOTE DESKTOP SESSIONS - As described herein, a computer system receives a first indication that an interactive login session is to be established. The first indication includes user credentials for establishing the interactive login session. The computer system then establishes the interactive login session using the received user credentials. The interactive login session includes a data transfer endpoint for receiving data from other sessions. The computer system receives a second indication that a child session is to be established in parallel to the established interactive login session. The child session is configured to direct input and output data through a loopback connection to the data transfer endpoint of the interactive login session. The computer system also establishes the child session using the received user credentials. The child session then transfers at least a portion of data to the data transfer endpoint of the interactive login session using the loopback connection. | 03-14-2013 |
20130067451 | APPLICATION DEPLOYMENT AND REGISTRATION IN A MULTI-USER SYSTEM - Embodiments are directed to efficiently provisioning applications in a multi-user environment. In one scenario, an administrator computer system pre-installs at least a portion of a software application on a data image, where the software application is to be installed on a client computer system upon receiving a notification from a computer administrator. The administrator computer system receives an input from the computer administrator indicating that a specified software application pre-installed on the client computer system's data image is to be installed on the client computer system. The administrator computer system then publishes a notification to the client computer system indicating that a specified software application pre-installed on the client computer system's data image is to be installed. Upon receiving the notification, the software application is installed on the client computer system from the data image. | 03-14-2013 |
20130114624 | MINIMUM NETWORK BANDWIDTH IN MULTI-USER SYSTEM - The management of bandwidth utilization in a network system that has multiple users. The system identifies the current set of users that are accessing the network by tracking which users are newly accessing the network, which users have ceased accessing the network, and which users continue to access the network over a period of time. The system then guarantees that these identified users will have a certain minimum bandwidth over the period of time. The system then enforces the guaranteed minimum bandwidth for each of the users so that they have no less than the corresponding guaranteed minimum bandwidth. Thus, even if the network bandwidth utilization would be saturated if all requests were satisfied, the system may continue operating while provided some guaranteed level of bandwidth to each user. | 05-09-2013 |
20130117336 | DATA CHANNEL UTILIZATION MANAGEMENT IN MULTI-USER SYSTEM - The management of data storage channel utilization in a computing system that has multiple users. The system receives file-level requests from requesters and then creates a history for each requester. Upon evaluating the history of each requester, the system determines whether to delay the file-level requests from entering the file system stack based on the result of the evaluation. The system delays one or more of the file-level requests if the history of the corresponding requester meets one or more criteria. If the history of the corresponding requester does not meet the criteria, the system allows the file-level requests to be passed to the file system stack without being delayed. | 05-09-2013 |
20130152077 | PERSONAL AND POOLED VIRTUAL MACHINE UPDATE - The updating of virtual machines. A task broker schedules update tasks for multiple virtual machines on the host machine. As each update task is to be performed, if the virtual machine is not currently running, as might be the case for a personal virtual machine, the virtual machine is caused to begin running to allow the update task to be performed on the virtual machine. Also, a pooled virtual machine is updated by copying information from the old virtual hard drive to a location to allow the information to be preserved as the master image is updated. After the update is completed, the virtual machine is formed, associated with the new virtual hard drive, and copied back to the virtual machine. | 06-13-2013 |
20140289718 | PERSONAL AND POOLED VIRTUAL MACHINE UPDATE - The updating of virtual machines. A task broker schedules update tasks for multiple virtual machines on the host machine. As each update task is to be performed, if the virtual machine is not currently running, as might be the case for a personal virtual machine, the virtual machine is caused to begin running to allow the update task to be performed on the virtual machine. Also, a pooled virtual machine is updated by copying information from the old virtual hard drive to a location to allow the information to be preserved as the master image is updated. After the update is completed, the virtual machine is formed, associated with the new virtual hard drive, and copied back to the virtual machine. | 09-25-2014 |
20140373092 | PROVIDING DOMAIN-JOINED REMOTE APPLICATIONS IN A CLOUD ENVIRONMENT - Embodiments are directed to provisioning private virtual machines in a public cloud and to managing private virtual machines hosted on a public cloud. In one scenario, a computer system receives authentication information for a private domain from an entity. The entity indicates that their private virtual machines are to be provisioned on a public cloud, where the entity's private domain is accessible using the authentication information. The computer system establishes a virtual network on the public cloud which is configured to host the entity's private virtual machines, where each virtual machine hosts remote applications. The computer system establishes an authenticated connection from the virtual network to the entity's private domain using the received authentication information and provides the entity's private virtual machines on the public cloud. The remote applications provided by the private virtual machines then have access to data stored within the entity's private domain using the authenticated connection. | 12-18-2014 |
20140373126 | USER AUTHENTICATION IN A CLOUD ENVIRONMENT - Embodiments are directed to authenticating a user to a remote application provisioning service. In one scenario, a client computer system receives authentication credentials from a user at to authenticate the user to a remote application provisioning service that provides virtual machine-hosted remote applications. The client computer system sends the received authentication credentials to an authentication service, which is configured to generate an encrypted token based on the received authentication credentials. The client computer system then receives the generated encrypted token from the authentication service, stores the received encrypted token and the received authentication credentials in a data store, and sends the encrypted token to the remote application provisioning service. The encrypted token indicates to the remote application provisioning service that the user is a valid user. | 12-18-2014 |
20140379899 | AUTOMATIC ADJUSTMENT OF APPLICATION LAUNCH ENDPOINTS - The adjustment of a number of application launch endpoint servers that may be used to service incoming connection requests. Application launch endpoints are entities, such as running code, that may be used to launch other applications. Examples of endpoints include virtual machines or sessions in a session management server. The system load associated with the incoming connection rate and number of users is monitored. In response, an add threshold and a perhaps a remove threshold is calculated. If the system load rises above the add threshold, application launch endpoint server(s) are added to the set of endpoints that can handle incoming connection requests. If the system load falls below the remove threshold, application launch endpoint server(s) are removed from to the set of endpoints. The add and remove thresholds may be calculated per tenant, and adjusted based on tenant behavior. | 12-25-2014 |