The Security ISV Console (the application implementing the Manageability Interface) and the Manageability ISV Console (the application using the Manageability Interface) have certain responsibilities imposed on them.  The Security ISV responsibilities are listed so Manageability ISV’s will know what behavior they can expect from the interface.

Manageability ISV responsibilities :

   Must maintain list of FQDN’s of systems that they requested unlocked per each unlock request.

   Return the systems to a power state that locks the drives (S4 or S5).


Security ISV Console responsibilities:

   Implementation must track the FQDN’s of Intel® vPro™ systems.

   Implementation must update the JobState field in each instance of the ConcreteJob while a given job is processing (the numbers are the standard values per the CIM_ConcreteJob class definition). 

   New (2) – Job to unlock the systems has not started.

   Running (4) – Job to unlock the requested systems is in progress

   Completed (7) – Job has completed, and all systems in a given unlock request are either returned in the unlockedSystems string array or the failedSystems stringArray

   Upon a job completing, the implementation must return all systems that were either successfully unlocked or not unlocked in the unlockedSystems and failedSystems fields (respectively) of the GetUnlockedSystems function.

   The implementation must persist an instance of CIM_ConcreteJob for at least 30 minutes after the job is completed.

   Implementation must return the maximum number of systems accepted per unlock request, in the MaxSystemsPerRequest field of the instance of the AMT_RemoteEncryptionService class.

   (optional) The Implementation can choose to return the unlocked and failed systems in the GetUnlockedSystems function as they are updated prior to the job completing.

Copyright © 2006-2013, Intel Corporation. All rights reserved.