Abstract: Access to peripherals can be managed in a containerized environment. A management service can be employed on a computing device to detect when a container is created. When a container is created or a peripheral is connected, the management service can determine that an application running within the container should be allowed to access a peripheral. The management service can then interface with a peripheral mapper running within the container to enable the application to access the peripheral. A peripheral access manager can also be employed to isolate the peripheral to the container.

Abstract: Services can be managed across containers. A management service can obtain or compile configuration information for containerized applications and containerized services that are hosted on a computing device. The configuration information can define how a containerized application is dependent on a containerized service. Using the configuration information, the management service can establish data paths between containers to enable container services running in the containers to perform cross-container communications by which a containerized application in one container can access a containerized service in another container. The management service may also enable a container service to perform communications by which a containerized application can access services provided by the host operating system.

Abstract: Systems and methods for deploying software updates in heterogeneous workspace environments are described. The system for managing workspaces includes computer-executable instructions for obtaining multiple inventories corresponding to multiple workspaces of an IHS, wherein the inventories each include information associated with the applications deployed in its respective workspace. The instructions are further executed to, for each inventory, identify the workspace associated with the inventory, determine which of the applications are to be updated with new software, and deploy the determined new software to the identified workspace.

Abstract: Device group configurations can be managed across workspaces based on context. A service can be employed on each client computing device that a user may use in his or her workspaces. The service can be configured to determine when a profile applies to a workspace and can automatically apply a device group configuration to the workspace. The service can also monitor for context changes while a device group configuration is applied and can adjust the device group configuration based on the context changes.

Abstract: Dependent containers can be managed based on context. When an application is deployed in a container and relies on a service or other resource external to the container, context about the container, the application and any data paths the container may require can be monitored and used to calculate a container instance weight, an application weight and a data path weight. Such weights can then be used to calculate a per container weight which in turn can be used to determine if any changes in container type or location may be more optimal for an application. Such weights can also be used to calculate a per solution weight which in turn can be used to determine if any changes in container type or location may be more optimal for a solution.

Abstract: Systems and methods for deploying software updates in hybrid workspace environments are described. In some embodiments, an Information Handling System (IHS) may include a processor and a memory coupled to the processor, the memory having program instructions stored thereon that, upon execution, cause the IHS to: consolidate an Operating System (OS) and Basic Input/Output System (BIOS) inventory with a plurality of workspace inventories; resolve dependencies among a plurality of updates based upon the consolidated inventories to identify an order of deployment; and deploy the plurality of updates in the order of deployment.

Abstract: Audio visual privacy controls can be provided. A privacy service can be configured to interface with multiple filter drivers that are loaded above components of an AV platform to enable the privacy service to selectively block a particular AV app's access to an AV device based on context. A privacy service may leverage a first filter driver to identify an AV app and may leverage a second filter driver to block the AV app's access. The privacy service may consider different types and combinations of context to determine when access to an AV device's stream should be blocked.

Abstract: Resource sharing can be enabled in a multi-client scenario. A service can be employed on client computing devices to detect when the client computing devices are connected to a display. The service can communicate with a management server to report when the client computing device is connected to a display. The management server can maintain information about the displays to which the client computing devices are connected. When the management server determines that a multi-client scenario exists, such as when multiple client computing devices are connected to the same display, the management server can provide information to the services on the client computing devices to enable the services to configure the client computing devices to share resources. When the management server determines that the multi-client scenario no longer exists, it can interface with the services to cause them to prevent further sharing of resources.

Abstract: Audio visual privacy controls can be provided. A privacy service can be configured to interface with multiple filter drivers that are loaded above components of an AV platform to enable the privacy service to selectively block a particular AV app's access to an AV device based on context. A privacy service may leverage a first filter driver to identify an AV app and may leverage a second filter driver to block the AV app's access. The privacy service may consider different types and combinations of context to determine when access to an AV device's stream should be blocked.

Abstract: Priority reversing data traffic for latency sensitive peripherals, including receiving a connection notification and parameters of a peripheral; identifying, from the parameters, that an interface type associated with the peripheral is a bulk interface, the bulk interface associated with a first communication channel between the IHS and the peripheral and having a first latency; determining, based on the bulk interface type and a data traffic priority associated with the peripheral, that the data traffic associated with the peripheral is priority-inversed; in response to a communication request by an application executing on the IHS for communication with the peripheral, determining that the data traffic associated with the peripheral is priority-inversed, and in response, placing the data traffic in a queue associated with a second communication channel defined between the IHS and the peripheral, the second communication channel having a second latency, wherein the first latency is greater than the second la

Abstract: Systems and methods are provided for management of processor thread used in support of workspaces operating on an IHS (Information Handling System), where the workspaces operate in isolation from the operating system of the IHS. A remote workspace orchestration service manages deployment of workspaces on the IHS. The workspaces are instantiated and operate according to a workspace definition provided by the workspace orchestration service. A remote access controller of the IHS determine one or more processor threads of the IHS used in support of the workspaces. The remote access controller monitors memory utilization by the processor threads used in support of the workspaces in order to detect memory thrashing resulting from the operation of a particular workspace. Based on the monitored memory utilization, the processor threads used in support of the workspaces are modified in order to reduce memory thrashing during the operation of the workspaces.

Abstract: Systems and methods are provided for consolidation of IHS (Information Handling System) authentication resources utilized by workspaces operating on the IHS, where the workspaces operate in isolation from the operating system of the IHS. A remote workspace orchestration service manages deployment of workspaces on the IHS. The workspaces are instantiated and operate according to a workspace definition provided by the workspace orchestration service. An embedded controller of the IHS registers authentication functions of the IHS with the workspace orchestration service, which notifies the workspaces of the consolidated authentication functions. An authentication agent is instantiated that supports operating system authentications for applications operating within the workspaces. The respective workspace definitions of the workspaces are updated to route credential requests to the authentication agent.

Abstract: A session can be predicted and created on a user's computing device to thereby allow the user to immediately resume productivity upon logging in. When a user accesses a set of applications from multiple computing devices and/or at different times or locations, telemetry information can be captured and processed to generate session predictions for the user. The session predictions can then be employed to automatically create sessions on the user's computing devices based on the user's location and the time of day.

Abstract: Services can be managed across containers. A management service can obtain or compile configuration information for containerized applications and containerized services that are hosted on a computing device. The configuration information can define how a containerized application is dependent on a containerized service. Using the configuration information, the management service can establish data paths between containers to enable container services running in the containers to perform cross-container communications by which a containerized application in one container can access a containerized service in another container. The management service may also enable a container service to perform communications by which a containerized application can access services provided by the host operating system.

Abstract: Peripherals can be managed in a containerized environment. A peripheral can be virtualized in multiple containers to allow applications hosted in the containers to access the peripheral. Local applications may also be allowed to access the peripheral. Such access may be enabled by virtualizing handles to the peripheral. The applications' access to the peripheral may be managed in accordance with policy to thereby ensure that one application's access does not negatively impact another application's access.

Abstract: Modern Standby configurations can be applied on a per-application basis. When a system is transitioning into Modern Standby, a host service can select a Modern Standby configuration to be applied to each Modern Standby capable application. The host service can then create job objects, or other suitable structures or functionality, to cause the selected Modern Standby configurations to be applied to the Modern Standby capable applications while the system is in Modern Standby. In this way, even though the operating system may implement Modern Connected Standby for all Modern Standby capable applications, dynamically selected Modern Standby configurations can be applied to mimic Modern Disconnected Standby or suspension for at least some of the Modern Standby capable applications.

Abstract: Applications can be migrated between containers during Modern Standby on a computing device. This migration may be performed to prolong the battery life of the computing device or to otherwise enhance performance. When a change in sensor state information is detected, a migration policy can be applied to application information to generate migration instructions. The migration instructions can then be used to migrate applications between containers.

Abstract: A computing device's performance can be dynamically tuned for a containerized application. A dynamic tuning solution can be configured to identify target applications that are running in workspaces implemented using containers, including when a target application is moved between workspaces and when a workspace's context is changed. The dynamic tuning solution can create mappings between identifiers of the container and a performance level associated with the target applications. A driver can then use these mappings to ensure that the computing device is dynamically tuned to the performance level associated with the target application when the container hosting the target application is active. The dynamic tuning solution can also reconcile discrepancies between a performance level associated with a target application and a performance level associated with a workspace in which the target application is containerized.

Abstract: When a transport is added, degraded, upgraded or lost between a computing device and a dock, peripherals can be moved or have their configurations modified to thereby seamlessly handoff and efficiently share the peripherals' traffic between the available transport(s). A service can be employed on the computing device to determine when a transport is added, degraded, updated or lost and to identify and implement one or more applicable rules to accomplish the handoff and sharing of the peripherals' traffic.

Abstract: Memory usage can be optimized during an imaging process to enable larger-sized deployments and client servicing. A variety of components can be employed on a computing device to present a hybrid virtual volume to the operating system during an imaging process. The hybrid virtual volume will appear to the operating system as having a large size while consuming minimal amounts of memory and disk. As a result, the risk of the imaging process failing for lack of resources will be minimized even when the image is large.