Abstract: In some remote application execution environments, a client device (e.g., to which application output is sent and where user interaction is performed) may include native control elements for touch input such as virtual keyboards, virtual pickers and the like. When the server device detects an editable/control field of a remoted application receiving focus, the server may instruct the client to activate a native control element for user interaction. The client may determine the manner in which to modify an application display to resolve potential display conflicts. For example, a native control element may obscure or hide portions of the remoted application on the client display. Modifying the application display may include panning the display, zooming into or out of portions of the display, adapting the display for scrolling, and the like. The remote computing device may also transmit values for populating a native control element.

Abstract: In some remote application execution environments, a client device (e.g., to which application output is sent and where user interaction is performed) may include native control elements for touch input such as virtual keyboards, virtual pickers and the like. When the server device detects an editable/control field of a remoted application receiving focus, the server may instruct the client to activate a native control element for user interaction. The client may determine the manner in which to modify an application display to resolve potential display conflicts. For example, a native control element may obscure or hide portions of the remoted application on the client display. Modifying the application display may include panning the display, zooming into or out of portions of the display, adapting the display for scrolling, and the like. The remote computing device may also transmit values for populating a native control element.

Abstract: In some remote application execution environments, a client device (e.g., to which application output is sent and where user interaction is performed) may include native control elements for touch input such as virtual keyboards, virtual pickers and the like. When the server device detects an editable/control field of a remoted application receiving focus, the server may instruct the client to activate a native control element for user interaction. The client may determine the manner in which to modify an application display to resolve potential display conflicts. For example, a native control element may obscure or hide portions of the remoted application on the client display. Modifying the application display may include panning the display, zooming into or out of portions of the display, adapting the display for scrolling, and the like. The remote computing device may also transmit values for populating a native control element.

Abstract: In some remote application execution environments, a client device (e.g., to which application output is sent and where user interaction is performed) may include native control elements for touch input such as virtual keyboards, virtual pickers and the like. When the server device detects an editable/control field of a remoted application receiving focus, the server may instruct the client to activate a native control element for user interaction. The client may determine the manner in which to modify an application display to resolve potential display conflicts. For example, a native control element may obscure or hide portions of the remoted application on the client display. Modifying the application display may include panning the display, zooming into or out of portions of the display, adapting the display for scrolling, and the like. The remote computing device may also transmit values for populating a native control element.

Abstract: Methods and systems for enabling multiple mobile devices to access an access gateway when at least one of the multiple mobile devices is unable to establish a virtual private network connection with the access gateway are described herein. For example, in some embodiments, a mobile device may configure itself as a member of a mesh network. A virtual private network connection may be established between the mobile device and the access gateway. The mesh network may include one or more other member devices that are unable to establish a virtual private network with the access gateway. After completing its configuration, the mobile device may receive, over a peer-to-peer connection of the mesh network, data that is intended for the access gateway and that is from one of the other member devices. The mobile device may transmit the data to the access gateway via the virtual private network connection.

Abstract: Methods and systems for enabling multiple mobile devices to access an access gateway when at least one of the multiple mobile devices is unable to establish a virtual private network connection with the access gateway are described herein. For example, in some embodiments, a mobile device may configure itself as a member of a mesh network. A virtual private network connection may be established between the mobile device and the access gateway. The mesh network may include one or more other member devices that are unable to establish a virtual private network with the access gateway. After completing its configuration, the mobile device may receive, over a peer-to-peer connection of the mesh network, data that is intended for the access gateway and that is from one of the other member devices. The mobile device may transmit the data to the access gateway via the virtual private network connection.

Abstract: Methods and systems for enabling multiple mobile devices to access an access gateway when at least one of the multiple mobile devices is unable to establish a virtual private network connection with the access gateway are described herein. For example, in some embodiments, a mobile device may configure itself as a member of a mesh network. A virtual private network connection may be established between the mobile device and the access gateway. The mesh network may include one or more other member devices that are unable to establish a virtual private network with the access gateway. After completing its configuration, the mobile device may receive, over a peer-to-peer connection of the mesh network, data that is intended for the access gateway and that is from one of the other member devices. The mobile device may transmit the data to the access gateway via the virtual private network connection.

Abstract: Methods, systems, computer-readable media, and apparatuses for providing a native desktop using cloud-synchronized data are presented. In some embodiments, a desktop management service provided by at least one computing device may selectively store data from a remote desktop. Subsequently, the desktop management service may synchronize the stored data with a cloud-based data storage platform. Thereafter, the desktop management service may cause a native desktop to be presented on a client device using the synchronized data. In some arrangements, the extracted, analyzed, and/or selectively stored data may include one or more application shortcuts, one or more documents, one or more registry keys, one or more personalization settings, or one or more layout settings. Additionally or alternatively, the remote desktop may be associated with a first operating system, and the native desktop may be associated with a second operating system different from the first operating system.

Abstract: Methods and systems are disclosed for transmitting data from a host computing device to a client computing device. This data may include graphical data, which may require additional processing by a renderer, such as a graphical processing unit (GPU), prior to being transmitted. Upon being forwarded to a specialized hardware component that, for example, may combine a GPU with a controller and one or more network interfaces, the graphical data may be rendered, packetized and transmitted without being provided to a system memory of the host computing device or otherwise involving the host computing device. Data packets including rendered graphical data may be generated by a second processor, different from the host processor of the host computing device.

Abstract: Methods and systems for enabling multiple mobile devices to access an access gateway when at least one of the multiple mobile devices is unable to establish a virtual private network connection with the access gateway are described herein. For example, in some embodiments, a mobile device may configure itself as a member of a mesh network. A virtual private network connection may be established between the mobile device and the access gateway. The mesh network may include one or more other member devices that are unable to establish a virtual private network with the access gateway. After completing its configuration, the mobile device may receive, over a peer-to-peer connection of the mesh network, data that is intended for the access gateway and that is from one of the other member devices. The mobile device may transmit the data to the access gateway via the virtual private network connection.

Abstract: Methods, systems, computer-readable media, and apparatuses for providing a native desktop using cloud-synchronized data are presented. In some embodiments, a desktop management service provided by at least one computing device may selectively store data from a remote desktop. Subsequently, the desktop management service may synchronize the stored data with a cloud-based data storage platform. Thereafter, the desktop management service may cause a native desktop to be presented on a client device using the synchronized data. In some arrangements, the extracted, analyzed, and/or selectively stored data may include one or more application shortcuts, one or more documents, one or more registry keys, one or more personalization settings, or one or more layout settings. Additionally or alternatively, the remote desktop may be associated with a first operating system, and the native desktop may be associated with a second operating system different from the first operating system.

Abstract: Methods, systems, computer-readable media, and apparatuses for providing a native desktop using cloud-synchronized data are presented. In some embodiments, a desktop management service provided by at least one computing device may selectively store data from a remote desktop. Subsequently, the desktop management service may synchronize the stored data with a cloud-based data storage platform. Thereafter, the desktop management service may cause a native desktop to be presented on a client device using the synchronized data. In some arrangements, the extracted, analyzed, and/or selectively stored data may include one or more application shortcuts, one or more documents, one or more registry keys, one or more personalization settings, or one or more layout settings. Additionally or alternatively, the remote desktop may be associated with a first operating system, and the native desktop may be associated with a second operating system different from the first operating system.

Abstract: In some remote application execution environments, a client device (e.g., to which application output is sent and where user interaction is performed) may include native control elements for touch input such as virtual keyboards, virtual pickers and the like. When the server device detects an editable/control field of a remoted application receiving focus, the server may instruct the client to activate a native control element for user interaction. The client may determine the manner in which to modify an application display to resolve potential display conflicts. For example, a native control element may obscure or hide portions of the remoted application on the client display. Modifying the application display may include panning the display, zooming into or out of portions of the display, adapting the display for scrolling, and the like. The remote computing device may also transmit values for populating a native control element.

Abstract: In some remote application execution environments, a client device (e.g., to which application output is sent and where user interaction is performed) may include native control elements for touch input such as virtual keyboards, virtual pickers and the like. When the server device detects an editable/control field of a remoted application receiving focus, the server may instruct the client to activate a native control element for user interaction. The client may determine the manner in which to modify an application display to resolve potential display conflicts. For example, a native control element may obscure or hide portions of the remoted application on the client display. Modifying the application display may include panning the display, zooming into or out of portions of the display, adapting the display for scrolling and the like. The remote computing device may also transmit values for populating a native control element.

Abstract: Methods and systems are disclosed for transmitting data from a host computing device to a client computing device. This data may include graphical data, which may require additional processing by a renderer, such as a graphical processing unit (GPU), prior to being transmitted. Upon being forwarded to a specialized hardware component that, for example, may combine a GPU with a controller and one or more network interfaces, the graphical data may be rendered, packetized and transmitted without being provided to a system memory of the host computing device or otherwise involving the host computing device. Data packets including rendered graphical data may be generated by a second processor, different from the host processor of the host computing device.

Abstract: Methods, systems, computer-readable media, and apparatuses for providing a native desktop using cloud-synchronized data are presented. In some embodiments, a desktop management service provided by at least one computing device may selectively store data from a remote desktop. Subsequently, the desktop management service may synchronize the stored data with a cloud-based data storage platform. Thereafter, the desktop management service may cause a native desktop to be presented on a client device using the synchronized data. In some arrangements, the extracted, analyzed, and/or selectively stored data may include one or more application shortcuts, one or more documents, one or more registry keys, one or more personalization settings, or one or more layout settings. Additionally or alternatively, the remote desktop may be associated with a first operating system, and the native desktop may be associated with a second operating system different from the first operating system.

Abstract: In some remote application execution environments, a client device (e.g., to which application output is sent and where user interaction is performed) may include native control elements for touch input such as virtual keyboards, virtual pickers and the like. When the server device detects an editable/control field of a remoted application receiving focus, the server may instruct the client to activate a native control element for user interaction. The client may determine the manner in which to modify an application display to resolve potential display conflicts. For example, a native control element may obscure or hide potions of the remoted application on the client display. Modifying the application display may include panning the display, zooming into or out of portions of the display, adapting the display for scrolling and the like. The remote computing device may also transmit values for populating a native control element.