How does Out of Band Management Provision systems that have been pre-provisioned?

Article:HOWTO7267  |  Created: 2007-04-30  |  Updated: 2007-04-30  |  Article URL
Article Type
How To


When a system had been pre-provisioned (manual entry of PID PPS, USB-key Provisioning, pre-provisioned from the manufacturer) the following process is used to Provision the system when it becomes active on the Network.

  1. First, OOBM tries to find out the Notification Server resource with exactly the same UUID as in the request. The possible tables we are searching in are
    • Inv_AMT_Computer_System—the table from Network Discovery solution (it also could be installed by our solution, if ND was not installed).
    • Inv_OOBSC_AMT_Device—this one being filled by our solution on synchronization (if it was done before).
    • Inv_OOBSC_AMT_Device—this one being filled by our solution on synchronization (if it was done before).
    • Inv_OOB_Capability—this one is ours from “AMT Inventory” server task (if we done it before). This one is filled in by the OOB discovery. OOB discovery is an executable that is downloaded and executed by Altiris agent’s Software Delivery subagent.
  2. If OOBM is unable to find resource by UUID, it then looks for the same IP in Notification Server table Inv_AeX_AC_TCPIP, which is one of the standard Notification Server inventory sent by Notification Server Agent from client computer.
  3. If OOBM finds Notification Server resource by UUID—we use the FQDN from Inv_AeX_AC_Identification, search complete.
  4. If OOBM finds Notification Server resource by IP—it checks further to verify that this resource is really correct one by trying to connect client via WMI and find out if we have same UUID on remote computer in “root\CIMV2” namespace and “Win32_ComputerSystemProduct” class. If we succeeded to connect and find the same UUID, we assume that this resource is correct and we are done.
  5. If there is no way to check using WMI, OOBM then uses DNS to resolve and look if the resolved names list have the same name, as resource found in Notification Server database:

§  If OOBM finds the same name, we assume that resource is correct to use and return its FQDN.

§  If list does not have same name as in Notification Server database, we are using first name from DNS resolution as FQDN (since AMT device name/IP should be able to resolve forth and back correctly).

Legacy ID


Article URL

Terms of use for this information are found in Legal Notices