Dell Products Inc.

Stokes Imaging Services

Carlton A Andrews

Joseph Kozlowski

David Konetski

Girish S Dhoble

Charles D Robison

Ricardo Luis Martinez

Nicholas Diciurcio Grobelny

Yuan-Chang Lo

Todd Erick Swierk

Philip M Seibert

Gary Douglas Huber

Andrew T Fausak

Anantha K Boyapalle

Douglas Miles Anson

Abeye Teshome

Roy William Stedman

Munif Farhan

Frank Howard Molsberry

Sandeep V Karandikar

Liam B Quinn

Sinem K Gulbay

Srikanth Kondapi

William Sauber

Charles Delbert Robison, Jr

Karthik Krishnakumar

Warren Wade Robbins

Bruce C Bell

Gregory James Breinholt

Phillip M Seibert

Clint H O'Connor

Danilo Ong Tan

Jason Alan Shepherd

Oleg Rombakh

Thomas Alexander Shows

Ryan Nicholas Comer

Kyle Eric Cross

Dirie N Herzi

Erin Lane Price

Frank Quintanilla, Iii

Clifton J Barker

Satya Mylvara

Nathan Francis Martell

Jason Kolodziej

Mark L Rehmann

Manish Bhaskar

Kurian George

Subramanian Ganesan

Mario Anthony Limonciello

Chad Skipper

Thomas Vrhel

William Nix

Michael Todd Boyum

Clint H OConnor

Joesph Kozlowski

Systems and methods for providing trusted local orchestration of workspaces are described. In some embodiments, an Information Handling System (IHS) may include a processor and a system memory coupled to the processor, the system memory having program instructions stored thereon that, upon execution, cause the IHS to: receive an orchestration code from a workspace orchestration service; record, using a trusted controller coupled to the processor, a log comprising: the orchestration code, and an indication of a sequence of operations performed during an instantiation of a workspace by the local management agent; provide a copy of the log to the workspace orchestration service; and establish a connection between the workspace and the workspace orchestration service in response to the workspace orchestration service's successful: (i) authentication of the orchestration code, and (ii) verification of the sequence of operations.

Trusted local orchestration of workspaces

Systems and methods for managing the degradation of IHS performance due to software installations 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: identify a workload; in response to the identification, configure a performance measurement; calculate a level of performance degradation of the IHS based, at least in part, upon the performance measurement; and in response to the level of performance degradation meeting a threshold value, provide an indication to a user or Information Technology (IT) administrator.

Managing the degradation of information handling system (IHS) performance due to software installations

Systems and methods for detecting security attacks using workspace orchestration logs are described. In some embodiments, a workspace orchestration server may include a processor and a memory coupled to the processor, the memory having program instructions stored thereon that, upon execution, may cause the server to: maintain a first workspace orchestration log, receive a second workspace orchestration log from a client Information Handling System (IHS), and identify the security attack, at least in part, in response to a discrepancy between the first and second workspace orchestration logs.

Detecting security attacks using workspace orchestration logs

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.

Management of communications during the orchestration of workspaces by multiple remote orchestrators

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.

Telemetry collection auto-tuning for workspaces

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.

Systems and methods for orchestrating IHS updates

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.

Systems and methods for managing shared-use peripheral devices

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.

Client initiated cloud-delivered device management check-in allowance and arbitration

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.

Co-managing firmware configuration and updates

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.

Systems and methods for updating peripheral devices

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 controller to trigger an embedded controller to wake a BIOS of the information handling system and forward the incoming low power communication technology data traffic to in-band applications on the information handling system if the information handling system location status is determined to be in one trusted zone location and the controller to ignore the received low power communication technology data traffic if the information handling system location status is in one untrusted zone location.

System and method for machine learning applied to in-band to out-of-band communications management

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 coupled to the processor, the memory having program instructions stored thereon that, upon execution by the processor, cause the client IHS to: transmit, by a local management agent to a workspace orchestration service, an access request and context information; receive, at the local management agent from the workspace orchestration service, one or more files or policies configured to enable the local management agent to instantiate a workspace based upon a workspace definition, wherein the workspace orchestration service is configured to: (i) calculate a security target and a productivity target based upon the access request and the context information, and (ii) create the workspace definition based upon the security target and the productivity target; and instantiate the workspace.

Systems and methods for modernizing workspace and hardware lifecycle management in an enterprise productivity ecosystem

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.

Systems and methods for configuring settings of an IHS (information handling system)

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.

Systems and methods for workspace continuity and remediation

Growing community of inventors

Austin, TX, United States of America

Carlton A Andrews