Abstract: Providing access control to distributed resources, including storing, at a computing dock coupled to an information handling system, a local access database indicating verified credentials of one or more users; receiving, at the computing dock, a request for access to a resource coupled to the computing dock; providing, in response to the request for access, an authentication request to an authentication system; in response to the authentication request, providing, by the computing dock, an authentication challenge to the information handling system; receiving, at the computing dock and in response to the authentication challenge, user credentials at the authentication system; verifying, at the authentication system, the user credentials against the local access database; providing, based on the verified user credentials, an authorization token to the first device; and allocating, based on the authorization token, access to the resource to the information handling system.

Abstract: Managing privacy controls in an information handling system to allow Information Technology Decision Makers (ITDMs) to prevent unwanted disclosure of information while allowing users to work together. A first privacy policy is asserted to protect information. When a user device requests an override to access an I/O device, embodiments analyze device parameters and application parameters to determine whether to authorize the use of the I/O device. If the override request is authorized, the user is able to access the I/O device and a new privacy policy is asserted. If a device parameter changes, embodiments may assess whether the change could result in unwanted disclosure of information and dynamically change the privacy policy to prevent the disclosure.

Abstract: Embodiments of systems and methods for platform framework policy management are described. A platform framework may receive, from an application of an IHS (Information Handling System), a registration as a user of a platform policy that is used to operate one or more of the hardware devices of the IHS. A platform framework of the IHS provides the application with a reference to the platform policy. In response to notifications of updates to the platform policy, the platform framework identifies the application as a registered user of the platform policy and provides the application with a reference to the updated platform policy. The platform policy may include a communication handle by which the policy is retrieved, where the handle may include a token that validates the authenticity of the platform policy.

Abstract: In one or more embodiments, one or more systems, one or more methods, and/or one or more processes may: execute a first application within a first operating system (OS) virtualization on a first information handling system (IHS); suspend the first application at a point of execution; determine one or more statuses associated with the first application, in which the one or more statuses includes the point of execution where the first application was suspended; provide the one or more statuses to a second IHS; configure a second application and a second OS virtualization with the one or more statuses associated with the first application within the first OS virtualization; establish input/output associated with the second application with one or more components of the first IHS via the network; and execute the second application within the second OS virtualization on the second IHS at the point of execution.

Abstract: Systems and methods for managing hardware privacy configuration in modern workspaces are described. In an embodiment, 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: receive, at a workspace privacy agent, a first hardware privacy request from a first application executed within a first workspace instantiated by a local management agent; and execute the first hardware privacy request.

Abstract: Systems and methods provide isolated workspaces operating on an IHS (Information Handling System) with use of pre-boot resources of the IHS that are not directly accessible by the workspaces. Upon notification of a workspace initialization, a segregated variable space, such as a segregated memory utilized by a UEFI (Unified Extensible Firmware Interface) of the IHS, is specified for use by the workspace. The segregated variable space is initialized and populated with pre-boot variables, such as UEFI variables, that are allowed for configuration by the workspace. Upon a workspace issuing a request to configure a pre-boot variable, the segregated variable space is identified that was mapped for use by the workspace. The requested pre-boot variable configuration is allowed based on whether the pre-boot variable is populated in the segregated variable space. When the requested pre-boot variable configuration is allowed, the pre-boot variable is configured on behalf of the workspace.

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: Modern Standby is enabled for unsupported applications. An enabler driver can be included on a system that supports Modern Standby and can be configured to detect when applications are loaded on the system. When an unsupported application is loaded, the enabler driver can interface with an enabler service to determine whether the unsupported application is Modern Standby capable. If so, the enabler driver can add the unsupported application to a throttle job object that the operating system uses to determine which applications should remain active during Modern Standby. In instances where an application is deployed in a container, an enabler container service can be leveraged to determine whether the containerized application is Modern Standby capable. If so, the enabler driver can add the container to the throttle job object.

Abstract: In one aspect, a disclosed method includes learning one or more chip agnostic parameters across a plurality of best known configuration (BKC) firmware versions, performing BKC attributes tuning based on said learning, implementing platform specific BKC table offsets and a handoff block to pass the table offsets to update routines by creating a trusted session for platform firmware table updates, and dynamically publishing changes in BKC policy. A BKC firmware serialization protocol may be implemented to ensure gaps in firmware versions at an end user platform are resolved by synchronizing each BKC version attribute. The serialization protocol may employ node-based cloud ecosystem learning. The method may further include reloading memory map parameters for uninterrupted services. The uninterrupted services may include, as examples, user presence detection after power resume and central processing unit (CPU) power cap functions.

Abstract: An information handling system includes a memory device, a memory, a chipset, and a basic input/output system (BIOS). The chipset includes a main processor and a hybrid processor. During a first pre-boot phase, the BIOS memory maps the hybrid processor to a first portion of the memory device, and stores an embedded operating system in the memory. During a second pre-boot phase, the BIOS memory maps the main processor to a second portion of the memory device, stores a host operating system in the memory, and loads the embedded operating system on the hybrid processor. The second portion is a larger portion of the memory device than the first portion.

Abstract: An exception handler for dynamic remediation of fatal errors is described. In an illustrative, non-limiting embodiment, an Information Handling System (IHS) may include a Central Processing Unit (CPU) and a memory coupled to the CPU, the memory having program instructions stored thereon that, upon execution, cause the IHS to: in response to an error, call a CPU Exception Service Routine (ESR); and at least one of: re-initialize a pre-boot network stack and transmit error data to a remote service using the pre-boot network stack; or re-initialize a pre-boot storage stack and store the error data using the pre-boot storage stack.

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: Embodiments of systems and methods for managing compute resources and runtime object load status in a platform framework 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: receive, at a platform framework via an Application Programming Interface (API), an arbitration policy; notify an application, by the platform framework via the API, of a state change with respect to the arbitration policy based upon a change in context; receive, at the platform framework from the application via the API, an identification of at least one compute resource to execute a workload associated with the arbitration policy; and offload the workload to the compute resource.

Abstract: Shared hoteling workspaces and computer equipment are preconfigured based on location. A location associated with a mobile device is monitored. As the mobile device moves toward a workspace, computer equipment associated with the workspace are automatically preconfigured for use. Different configuration events and operational states may be implemented, based on a locational proximity of the mobile device to the workspace. When the mobile device arrives at the workspace, the mobile device has been automatically paired/registered with the computer equipment at the workspace. Moreover, when the location of the mobile device no longer matches the workspace, the network pairings/registrations may be automatically torn down and deleted, thus making the workspace available for a next occupant.

Abstract: A method for managing firmware of an information handling system may include receiving, by the information handling system, an update for a firmware of the information handling system. The information handling system may determine based, at least in part, on the received update, one or more firmware modules of the information handling system that are changed by the update. The information handling system may determine a location of each of the one or more firmware modules within one or more firmware volumes of the information handling system using an offset list including one or more offsets corresponding to the one or more firmware modules. The information handling system may update the one or more firmware modules based, at least in part, on the determined location of each of the one or more firmware modules within the one or more firmware volumes.

Abstract: Shared hoteling workspaces and computer equipment are preconfigured based on location. A location associated with a mobile device is monitored. As the mobile device moves toward a workspace, computer peripheral equipment assigned to the workspace are identified and a best known configuration is retrieved. As the mobile device continues moving toward the workspace, the mobile device installs the best known configuration. Location-based policies and configuration events are defined and executed to ensure the best known configuration is timely installed. When the mobile device arrives at the workspace, the mobile device has been automatically configured to the computer peripheral equipment at the workspace. The mobile device is thus preconfigured, perhaps just in time, for immediate productivity and optimum user experience. Moreover, when the location of the mobile device no longer matches the workspace, the best known configuration may be automatically deleted to conserve memory.

Abstract: Systems and methods for generating workspace distribution and/or configuration recommendations are described. In an embodiment, 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: receive data related to a plurality of workspaces; generate, based upon the data, a recommendation to modify at least one of the plurality of workspaces; and modify the at least one of the plurality of workspaces.

Abstract: Embodiments of systems and methods for intelligent orchestration of video participants in a platform framework 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: process at least a first portion of a video workload using the processor; and in response to a change in context of the IHS, process at least a second portion of the video workload using an offload core.

Abstract: Systems and methods are provided for remotely supporting managed hardware components of an IHS (Information Handling System). Prior to booting an operating system of the IHS, the managed hardware components are enumerated as supporting remote management and a network stack is created in a secured IHS memory, where the network stack is for transfer of remote device management communications directed at the managed hardware components. Still prior to booting the operating system, the IHS chipset is configured to route device management messages received from remote management tools to the network stack. After booting the operating system, a secure remote management session is established between a remote management tool and an IHS device management agent. During operation of the device management agent in the booted operating system, device management messages are retrieved from the network stack and decoded device management messages are delivered to a managed hardware component.

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.