Abstract: Client initiated cloud-delivered device management check-in allowance and arbitration may include registering an application as a cloud-based unified endpoint management and antimalware eventing-entitled application, assigning an eventing identification to the application, and deploying the application to a client Information Handling System (IHS). A cloud-delivered device management agent on the IHS is enabled to allow local eventing and a maximum number of events per time period(s) from the application are defined. The agent checks in to a cloud-delivered device management service, upon a compliance failure event, keyed by the application, and passes an alert of the compliance failure with a reason and the application's name. The agent reports excess alerting over the maximum number of events per time period as compliance failure by the client IHS, with the application's name. Also, the agent may cease passing alerts from the application in response to triggering such a report of excess alerting.

Abstract: Systems and methods support updates peripheral devices that may be coupled to an Information Handling System (IHS), such as provided at shared-use workstations. The IHS reports, to a remote orchestrator, an inventory of peripheral devices that are coupled to the IHS. In response, the remote orchestrator provides the IHS with files for updates to some or all of the coupled peripheral devices. As part of the updates, the remote orchestrator also designates a specific peripheral device as a proxy for making updates to other peripherals of the shared-use workstation. The IHS transmits the files to the proxy peripheral device, where the files are stored in a memory of the proxy peripheral device. The proxy peripheral device uses the files to update the other peripherals of the shared-use workstation, such as when the peripherals are not in use by the IHS, or after the IHS has been disconnected.

Abstract: An information handling system is configured to remotely monitor a managed resource that includes lifecycle management and/or control of basic input/output system settings and administrator password. The information handling system is also configured to provide software and/or firmware updates on the managed resource using a binary large object with an entitlement to the managed resource.

Abstract: An information handling system operating a low power communications engine comprising a wireless adapter for communicating on a low power communication technology network for receiving low power communication technology data traffic for at least one always-on remote management service for the information handling system, a controller receiving a location status of the information handling system via the low power communication technology network indicating a location or network, where the controller executes code instructions for a low power communications engine to assess a location trust level from an environment characteristics analysis engine to determine whether the location status is a trusted zone location or an untrusted zone location utilizing binary classification machine learning based on input variables including data relating to history of activity at the location or on the network learned by the environment characteristics analysis engine from reported operational or network activity, and the co

Abstract: Systems and methods for modernizing workspace and hardware lifecycle management in an enterprise productivity ecosystem are described.

Abstract: Systems and methods are provided that support configuration of settings of an Information Handling System (IHS), such as by external configuration tools that are delegated authority to configure any portion of the configurable settings of IHS. During factory provisioning of the IHS, an inventory of configurable settings of the IHS is generated and permissions are assigned for configuration of a portion of the configurable IHS settings by a configuration tool. During the factory provisioning, credentials are stored to the IHS for authenticating communications from the assigned configuration tool. Once the IHS has been delivered and deployed, configuration of the assigned portion of IHS is allowed when configuration requests from the assigned configuration tool are successfully validated against the credentials stored to the IHS during factory provisioning. The configurable settings of the IHS may include BIOS settings, operating system settings and settings supported by hardware components of the IHS.

Abstract: Systems and methods support updates to an Information Handling System (IHS). A workspace is instantiated on the IHS based upon a received workspace definition, where the workspace identifies an available update to a system operating on the IHS. A request is made for a first credential used for validation of the IHS by a first remote workspace orchestrator. The workspace provides the first credential to a second remote workspace orchestrator that controls access to updates to the system operating on the IHS. The second remote workspace orchestrator uses the first credential to validate the IHS with the first remote workspace orchestrator. The workspace performs the available update to the system operating on the IHS using a second credential provided by the second remote workspace orchestrator upon validation of the IHS by the first remote workspace orchestrator. The IHS maintains separate confidentiality with each remote orchestrator providing credentials for the update.

Abstract: Systems and methods support updates peripheral devices that may be coupled to an Information Handling System (IHS), such as provided at shared-use workstations. The IHS reports, to a remote orchestrator, an inventory of peripheral devices that are coupled to the IHS. In response, the remote orchestrator provides the IHS with files for updates to some or all of the coupled peripheral devices. As part of the updates, the remote orchestrator also designates a specific peripheral device as a proxy for making updates to other peripherals of the shared-use workstation. The IHS transmits the files to the proxy peripheral device, where the files are stored in a memory of the proxy peripheral device. The proxy peripheral device uses the files to update the other peripherals of the shared-use workstation, such as when the peripherals are not in use by the IHS, or after the IHS has been disconnected.

Abstract: Client initiated cloud-delivered device management check-in allowance and arbitration may include registering an application as a cloud-based unified endpoint management and antimalware eventing-entitled application, assigning an eventing identification to the application, and deploying the application to a client Information Handling System (IHS). A cloud-delivered device management agent on the IHS is enabled to allow local eventing and a maximum number of events per time period(s) from the application are defined. The agent checks in to a cloud-delivered device management service, upon a compliance failure event, keyed by the application, and passes an alert of the compliance failure with a reason and the application's name. The agent reports excess alerting over the maximum number of events per time period as compliance failure by the client IHS, with the application's name. Also, the agent may cease passing alerts from the application in response to triggering such a report of excess alerting.

Abstract: Systems and methods for managing communications during the orchestration of workspaces by multiple remote orchestrators are described. In an illustrative, non-limiting embodiment, a first orchestrator with respect to a workspace executed by a client 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 by the processor, cause the first orchestrator to: create a first payload with a first data portion; and receive, from a second orchestrator with respect to the workspace, a hash of at least a second data portion exclusive of the second data portion, where the second orchestrator is configured to send a second payload comprising the second data portion to the client IHS, and where the client IHS is configured to validate the second payload, at least in part, based upon the hash.

Abstract: Systems and methods for telemetry collection auto-tuning for workspaces are described. In an illustrative, non-limiting embodiment, a client 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 by the processor, cause the client IHS to: collect telemetry during execution of a workspace using a telemetry collection setting specified in a file or policy received from a workspace orchestration service, where the file or policy implements a workspace definition usable by a local management agent to instantiate the workspace; in response to a comparison between a security risk score and a threshold risk level, modify the telemetry collection setting; and collect telemetry using the modified telemetry collection setting.

Abstract: System and methods utilize Information Handling Systems (IHSs) in updating shared-use peripheral devices, such as peripherals available at a public or shared-use workstation. The coupling of a first shared-use peripheral device to the IHS is detected. The coupling of the first shared-use peripheral device is reported to a remote orchestrator that may support the operation of workspaces on the IHS. Files are received from the remote orchestrator for updating the first shared-use peripheral device. The IHS updates the first shared-use peripheral device using the received files. A coupling is detected of a coupling of a second shared-use peripheral device to the IHS, such as resulting form movement to a different shared-use workstation. If compatible, the second shared-use peripheral device is also updated using the received files. An IHS that is regularly coupled to different peripherals at different shared-use workstations may be selected to effectively distribute updates to these peripherals.

Abstract: A wireless loadbar weighing system is described, including a first loadbar and a second loadbar, where the first loadbar and the second loadbar are configured to support a weighing platform in use. Each of the first loadbar and the second loadbar are configured to measure force applied by the weighing platform, and produce first measured force data and second measured force data respectively. Each of the first loadbar and the second loadbar include a processing module including a wireless communication device. At least one of the first loadbar and the second loadbar is configured to wirelessly transmit, to a remote device for further processing and/or display, at least one of: the first measured force data and the second measured force data, and a weight measurement of a mass supported by the weighing platform determined based on the first measured force data and the second measured force data.

Abstract: Systems and methods for modernizing workspace and hardware lifecycle management in an enterprise productivity ecosystem are described.

Abstract: Systems and methods for modernizing workspace and hardware lifecycle management in an enterprise productivity ecosystem are described. In some embodiments, a client Information Handling System (IHS) may include a processor and a memory, the memory having program instructions that, upon execution by the processor, cause the client IHS to: receive, from a workspace orchestration service, one or more files or policies configured to enable the client IHS to instantiate a first workspace based upon a first workspace definition; allow a user to execute a non-vetted application in the first workspace; determine that the first workspace is compromised; and receive, in response to the determination, from the workspace orchestration service, one or more other files or policies configured to enable the client IHS to instantiate a second workspace based upon a second workspace definition, where the second workspace definition allows execution of a vetted application corresponding to the non-vetted application.

Abstract: Systems and methods for securely deploying a collective workspace across multiple local management agents 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 workspace orchestration service from a first local management agent, first context information and a first split key; receive, at the workspace orchestration service from a second local management agent, second context information and a second split key; determining, by the workspace orchestration service, that the first and second context information match a collaborative workspace policy; in response to the determination, authenticate the first and second split keys; and in response to the authentication, transmit a collaborative workspace definition to the first and second local management agents.

Abstract: Systems and methods for modernizing workspace and hardware lifecycle management in an enterprise productivity ecosystem are described.

Abstract: Systems and methods for workspace deployment using a secondary trusted device are described. In some embodiments, a first 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 first IHS to: establish a first connection with a second IHS, where the second IHS is configured to establish a second connection with a workspace orchestration service, and where the workspace orchestration service is configured to: receive device identification information of the first IHS from the second IHS; and authenticate the device identification information against a database provided by a manufacturer of the first IHS; and in response to a successful authentication, establish a third connection with the workspace orchestration service.

Abstract: An information handling system is configured to remotely monitor a managed resource that includes managing an entitlement for access to a secured component of the managed resource. The information handling system is configured to determine whether a function to be performed on the managed resource requires access to the secured component of the managed resource. The information handling system is further configured to transmit an application programming request to perform the function on the managed resource, wherein the application programming request includes a data object with the entitlement to access the secured component. In response to a verification of the authenticity of the data object is successful, then to process the data object that includes to invoke a plugin that is associated with the application and to execute the application with the entitlement as an argument.

Abstract: Embodiments provide access to enterprise data via a secured virtual environment hosted on an Information Handling System (IHS), with the integrity of the IHS validated prior to launching the virtual environment. The integrity of the IHS may also be continuously validated during operation of the launched virtual environment. Policies for accessing the enterprise data are stored in a secured memory that is isolated from the operating system of the IHS. A virtual environment is configured, according to the policies, with resources for a particular user to access the enterprise data. If the integrity of the IHS is validated by a trusted resource on the IHS, the virtual environment is launched. During operation of the virtual environment, the trusted resource periodically confirms the integrity of the IHS. If the integrity of the IHS is not verified or policy changes are identified, access to the secured workspace may be revoked.