Abstract: Systems and methods for unlocking a device remotely from a server, where the device is connected locally to a client, and the server is remote to the client and the device, are provided in accordance with various aspects of the subject technology. In one aspect, a system includes a remote unlocking module configured to monitor, at the server, traffic between a secure application and a virtual bus driver for at least one string descriptor request associated with switching an interface of the device from a first interface type to a second interface type, and to intercept the at least one string descriptor request. The system further includes an agent configured to receive the intercepted at least one string descriptor request, and to send the intercepted at least one string descriptor request from the server to the client over a network.

Abstract: The deployment of a driver or an application on a client device having a write-filter is described. A deployment configuration file is obtained, wherein the deployment configuration file includes a plurality of deployment entries each having information for deployment of one of a driver and an application. A first deployment entry is retrieved from the deployment configuration file, and the deployment configuration file is modified to remove the first deployment entry from the deployment configuration file. The modified deployment configuration file is stored in a location of a memory of the client device that is exempt from a write-filter restriction, wherein the write-filter restriction prohibits a file stored on the client device with the write-filter enabled from persisting across a reboot of the client device. The one of the driver and the application of the first deployment entry is then deployed on the client device while the write-filter is disabled.

Abstract: The deployment and updating of applications and drivers on a client device having a write-filter is described. A first deployment extensible markup language (XML) configuration file is obtained for deploying a first application or driver at the client device. A first application or driver is deployed on the client device based on the first deployment XML configuration file, while the write-filter of the client device is disabled. The write-filter is enablable to prohibit a file stored on the client device with the write-filter enabled from persisting across a reboot of the device. Following the deployment, automatic updating is performed by determining whether an autoupdate is available, obtaining a second deployment XML configuration file for updating the first application or driver, and updating the first application or driver based on the second deployment XML configuration file, while the write-filter is disabled. The automatic updating may be repeated.

Abstract: Examples of methods, systems, apparatus, and machine-readable storage media are provided to facilitate access and control of a remote desktop of a remote machine by a web browser at a client device through a transcoding server without installing proprietary plug-ins or protocols on the client device. A transcoding server may translate user input requests from a web browser into input calls compatible with a remote desktop display protocol. The transcoding server may receive remote desktop drawing commands from the remote machine and translate the remote desktop drawing commands into web browser drawing updates compatible with the web browser. A transcoding server may communicate with a web browser via HTTP and communicate with a remote machine via a remote desktop display protocol. A web browser may be an HTML5 browser. A transcoding server may send drawing coordinates to the web browser via an HTTP header and may use long polling.

Abstract: Managing access restriction to a device is provided. The operations may include determining that a device stack corresponds to a device that is remote to the server and is connected locally to a client that is remote to the server; attaching a device access restriction object on top of the device stack; receiving, at the device access restriction object, an access request to the device; and determining, at the device access restriction object, whether the access request is allowed access to the device.

Abstract: Managing access requests to a device is provided. The operations may include determining that a device stack corresponds to the device that is remote to the server and is connected locally to a client that is remote to the server, the device stack comprising one or more device objects; attaching a device access restriction object on top of the device stack; facilitating restriction of access to the one or more device objects from sessions different from a session associated with the device; receiving, at the device access restriction object, an access request to the device; and determining, at the device access restriction object, whether the access request is allowed access to the device. The access request may be allowed if a session from which the access request is received is a predetermined session.

Abstract: Systems and methods for facilitating unlocking a device connected locally to a client, utilizing a server located remotely from the client and the device, are provided in accordance with various aspects of the subject technology. In one aspect, a system includes a proxy configured to receive, at the client, at least one string descriptor request from the server over a network, where the at least one string descriptor request is associated with switching an interface of the device from a first interface type to a second interface type. The system further includes a stub driver configured to receive the at least one string descriptor request from the proxy, and to direct the at least one string descriptor request to the device.

Abstract: Source data stored on a source device may be shared with one or more devices. Sharing the source data may include facilitating receiving, at a first device, a first token associated with the source data, from a second device, using a near proximity communication (NPC) protocol. The NPC protocol may support generation of the first token based on detection of presence of the first device within five feet of the second device. The first token may be encoded for NPC communication and may be non-public. The first token may be based on the source data and the receipt of the first token may be based on the detection. The first token may be decoded and communicated, based on a first communication protocol, to a third device to download the source data using the decoded first token. The second device may be an NPC-enabled device.

Abstract: Source data stored on a source device may be shared with one or more devices. Sharing the source data may include facilitating obtaining an image of a visual tag from another device. A visual tag may be obtained via a communication method or optically captured via an optical device. The visual tag may comprise a visually encoded first token associated with the source data. The first token may be a non-public token based on the source data. The visual tag may be decoded to retrieve the first token. The device with the retrieved first token may provide for communication based on a communication protocol to a second device to download the source data using the retrieved first token. A device may be adapted to provide display of the visual tag or communicate or receive the visual tag.

Abstract: Source data stored on a source device may be shared with other devices. Sharing the source data may include facilitating communication associated with the source data, based on a communication protocol, between a first device and another device. Receiving a first token associated with the source data may be facilitated. The first token may be encoded to generate a visual tag. An image of the visual tag may be provided to enable a second device to capture the image, retrieve the first token after decoding the visual tag, and use the first token to access the source data utilizing a communication protocol.

Abstract: Source data stored on a source device may be shared with other devices. Sharing the source data may include facilitating communication associated with the source data, based on a first communication protocol, between a first device and another device. Receiving a first token associated with the source data may be facilitated. The first token may be encoded to enable communication using a near proximity communication (NPC) protocol. Communication of the first token may be provided to a second device, located within five feet of the first device, using the NPC protocol, to enable the second device to access the source data utilizing a second communication protocol. The NPC protocol is a wireless communication protocol, and supports automatic connection between at least two devices located within five feet. The first and second devices are NPC-enabled devices.

Abstract: Examples of methods, systems, apparatus, and machine-readable storage media are provided to facilitate access and control of a remote desktop of a remote machine by a web browser at a client device through a transcoding server without installing proprietary plug-ins or protocols on the client device. A transcoding server may translate user input requests from a web browser into input calls compatible with a remote desktop display protocol. The transcoding server may receive remote desktop drawing commands from the remote machine and translate the remote desktop drawing commands into web browser drawing updates compatible with the web browser. A transcoding server may communicate with a web browser via HTTP and communicate with a remote machine via a remote desktop display protocol. A web browser may be an HTML5 browser. A transcoding server may send drawing coordinates to the web browser via an HTTP header and may use long polling.

Abstract: Examples of methods and apparatus are provided for state-based provisioning of a local client having a windows-based embedded image. The apparatus may include a retrieval module of the local client that facilitates locating a remote repository server containing a configuration file and that facilitates obtaining the configuration file from the remote repository server. The apparatus may include a reset check module of the local client that determines whether to reset a previous state of the image based on the configuration file. The apparatus may include an apply settings module of the local client that applies, to the image, one of a first configuration change and a second configuration change based on the determination. The first configuration change may include a configuration update to the previous state of the image. The second configuration change may include a change to the image independent of the previous state of the image.

Abstract: The deployment of a driver or an application on a client device having a write-filter is described. A deployment configuration file is obtained, wherein the deployment configuration file includes a plurality of deployment entries each having information for deployment of one of a driver and an application. A first deployment entry is retrieved from the deployment configuration file, and the deployment configuration file is modified to remove the first deployment entry from the deployment configuration file. The modified deployment configuration file is stored in a location of a memory of the client device that is exempt from a write-filter restriction, wherein the write-filter restriction prohibits a file stored on the client device with the write-filter enabled from persisting across a reboot of the client device. The one of the driver and the application of the first deployment entry is then deployed on the client device while the write-filter is disabled.

Abstract: The installation of a disk image onto a client device having a hardware platform of a particular class is described, where the disk image includes a driver-store having a plurality of drivers for a plurality of hardware platforms. The disk image is stored on the client device, and at least one driver from the driver-store is installed on the client device based on the hardware platform of the client device. A device driver configuration file is retrieved, wherein the device driver configuration file identifies one or more drivers associated with a class of hardware platforms, and identifies one or more common drivers shared by two or more of the plurality of hardware platforms. Drivers identified in the device driver configuration file and that are neither associated with the class of the client device, nor associated with the platform of the client device, are removed from the driver-store.

Abstract: The automatic updating of an application or a driver on a client device is described. At least one deployment configuration file, including a deployment entry corresponding to a package for updating an application or a driver, is obtained at the client device. The deployment configuration file is stored on the client device in a memory location that is exempt from a write-filter restriction, wherein the write-filter restriction prohibits a file stored with the write-filter enabled from persisting across a reboot of the device. A check is performed to determine whether the deployment entry identifies an application or driver that is installed on the client device, and identifies a version of the application or driver that is higher than a version installed on the client device. The application or driver corresponding to the deployment entry is then updated on the client device using the package, while the write-filter is disabled.

Abstract: The processing of a first data stream to generate a second stream conforming to a remote desktop protocol (RDP) is described. Operations may include facilitating storage of first data from the first stream at a first index indicated in the first stream, facilitating retrieval of second data from a second index included in the first stream, and facilitating generation of the second stream conforming to the RDP and including the first and second data. Additionally, the processing of a third data stream conforming to the RDP to stream a fourth stream is described. Operations include facilitating processing of the third stream to identify a package data unit (PDU), facilitating storing of a hash value corresponding to the PDU, and facilitating generating an altered PDU for inclusion in the fourth stream and including an index identifying a location in memory storing the hash value.

Abstract: The deployment and updating of applications and drivers on a client device having a write-filter is described. A first deployment extensible markup language (XML) configuration file is obtained for deploying a first application or driver at the client device. A first application or driver is deployed on the client device based on the first deployment XML configuration file, while the write-filter of the client device is disabled. The write-filter is enablable to prohibit a file stored on the client device with the write-filter enabled from persisting across a reboot of the device. Following the deployment, automatic updating is performed by determining whether an autoupdate is available, obtaining a second deployment XML configuration file for updating the first application or driver, and updating the first application or driver based on the second deployment XML configuration file, while the write-filter is disabled. The automatic updating may be repeated.

Abstract: Computing device deployment and configuration using a mass storage device is provided. A generic computing device is provided to a customer or end user. A mass storage device is used to distribute configuration information to the generic computing device. The configuration information includes customer-specified or ordered software applications or other features. The configuration information can also include updates to the computing device system software. The customer or end user couples the mass storage device to the generic computing device in order to load the configuration information into the computing device. After the configuration information is loaded, the computing device is configured for the customer's use. Further features, such as creating customized images, are also provided.

Abstract: An example of a method for facilitating split booting includes executing a base system image file of a system, initializing components of the first computing device, loading the extended system image file, and executing the extended system image file from the first computing device without booting the first computing device. The base system image file and an extended system image file of the system are built from a single executable system image file of the system. An example of a method for building system images includes building, as a single executable file, a system image file of a system and dividing the system image file into a base system image file and an extended system image file. An example of a machine-readable storage medium having code for carrying out the method, an apparatus having the machine-readable storage medium, and an apparatus having means for carrying out the method is disclosed.