Abstract: Technologies for secure offline activation of hardware features include a target computing device having a platform controller hub (PCH) including a converged security and manageability engine (CSME) and a number of in-field programmable fuses (IFPs). During assembly of the target computing device by an original equipment manufacturer (OEM), the CSME is provided a list of hardware features to be activated. The CSME configures the IFPs to enable the requested features, generates a digital receipt including the activated features and a unique device ID, and signs the receipt using a unique device key. Signed receipts may be periodically submitted to a vendor computing device, which verifies the signed receipts, extracts the active feature list, and bills the OEM for activated features of the PCHs. The vendor computing device may bill the OEM a maximum price for PCHs for which there is no associated signed receipt. Other embodiments are described and claimed.

Abstract: In one embodiment, the present invention includes a method for determining if a system is compatible with an up-binning or down-binning to a hardware resource of the system through RFID tag communication, receiving instructions from a remote server to upgrade the hardware resource if the system is compatible, and programming the hardware resource based on the instructions. In one such embodiment, the hardware resource may be programmed by use of programmable fuses to enable circuitry of the hardware resource. Other embodiments are described and claimed.

Abstract: In one embodiment, the present invention includes a method for determining if a system is compatible with an up-binning or down-binning to a hardware resource of the system through RFID tag communication, receiving instructions from a remote server to upgrade the hardware resource if the system is compatible, and programming the hardware resource based on the instructions. In one such embodiment, the hardware resource may be programmed by use of programmable fuses to enable circuitry of the hardware resource. Other embodiments are described and claimed.

Abstract: An embodiment may include circuitry that may be comprised in a host that may execute an operating system and/or in a server. The circuitry may generate, at least in part, and/or receive, at least in part, at least one request to initiate, at least in part, at least one operation at the host. The least one operation may facilitate, at least in part, examination remotely from the host of information stored at the host. The at least one operation may be performed independently from the operating system and also may be performed at least in part by the circuitry. The examination may facilitate, at least in part, remotely from the host, backup, recovery, and/or determination of corruption of mass storage data stored at the host. Of course, many variations, modifications, and alternatives are possible without departing from this embodiment.

Abstract: An information handling system having a processor and a computer readable medium accessible by the processor and having stored thereon a data structure operable as a directory service. The data structure includes a field comprising a service level object representing a service and comprising data defining roles for the service level object, policies for service level object, and service oriented architecture polices for the service level object. The data structure also includes a field comprising a hardware-level map object subordinate to and in relationship with the service level object, representing hardware or software supporting the service, and comprising data defining roles for the hardware-level map object, policies for the hardware-level map object, and service oriented architecture polices for the hardware-level map object.

Abstract: An information handling system having a processor and a computer readable medium accessible by the processor and having stored thereon a data structure operable as a directory service. The data structure includes a field comprising a service level object representing a service and comprising data defining roles for the service level object, policies for service level object, and service oriented architecture polices for the service level object. The data structure also includes a field comprising a hardware-level map object subordinate to and in relationship with the service level object, representing hardware or software supporting the service, and comprising data defining roles for the hardware-level map object, policies for the hardware-level map object, and service oriented architecture polices for the hardware-level map object.