Provisioning trouble with Intel SCS

Provisioning trouble with Intel SCS

Hi,

I'm trying to provision my AMT systems in enterprise mode but have been unsuccessful so far. I have tried using the USB key method and entered the key pairs manually. The log file of the SCS shows the following:

2007-03-25 19:45:50,Exception while provisioning AMT: (913) No rows found in get UuidMap,SeverityError,AMTServeradministrator,

2007-03-25 19:43:50,Exception while provisioning AMT: (913) No rows found in get UuidMap,SeverityError,AMTServer administrator,

2007-03-25 19:42:47,Exception while provisioning AMT: (913) No rows found in get UuidMap,SeverityError,AMTServer administrator,

6 posts / 0 new
Last post
For more complete information about compiler optimizations, see our Optimization Notice.

I put the logging to verbose and this is the new output to the log file.

2007-03-25 20:37:51,Exception while provisioning AMT: (913) No rows found in get UuidMap,SeverityError,AMTServeradministrator,

2007-03-25 20:37:51,Exception while provisioning AMT: (913) No rows found in get UuidMap,SeverityError,AMTServeradministrator,

2007-03-25 20:37:51,Provisioning AMT: DEBB91D02538DB118F15000EA68F75B9,Information,AMTServeradministrator,DEBB91D0-2538-DB11-8F15-000EA68F75B9

2007-03-25 20:37:51,Provisioning AMT: EDD8629A903D11DBBBDAFE699FC00018,Information,AMTServeradministrator,EDD8629A-903D-11DB-BBDA-FE699FC00018

2007-03-25 20:37:29,Incoming connection from 192.168.0.10:16994, version 2, count 0, uuid DEBB91D02538DB118F15000EA68F75B9,Information,AMTServeradministrator,

2007-03-25 20:37:10,Incoming connection from 192.168.0.11:16994, version 2, count 0, uuid EDD8629A903D11DBBBDAFE699FC00018,Information,AMTServeradministrator,

I found out why this problem is happening, I misunderstood the provisioning process. The actual operation poses some problems though.

Here is how I understood the AMT provisioning process:

  1. The new AMT client is given a key pair via USB setup or is configured manually by a technician through the BIOS interface.
  2. The AMT client communicates with the SCS and is partially provisioned; it is then added to the New Intel AMT Systems part of the SCS console.
  3. From there the administrator assigns a provisioning profile to use.
  4. SCS completes the provisioning process.

It seems I was wrong about steps 2 and 3. Here is the provisioning process the way it works with the Intel SCS:

  1. The new AMT client is given a key pair via USB setup or is configured manually by a technician through the BIOS interface.
  2. The administrator adds the new AMT Device to the SCS database manually or it is done through an API call to the SCS. The following information must be set:
    1. UUID
    2. Fully Qualified Doma
      in Name
    3. Active Directory Domain Name
    4. Provisioning profile to use
  3. SCS completes the provisioning process.

The main problem I foresee with this is step 2 as this means that a device cannot be provisioned at all until it has been added to the SCS database, either manually or through some external application. This is all good and well when all the required information is available. A provisioning profile can be set be set before hand and the FQDN and Active Directory Names can be set by the administrator, but what if we dont know the UUID of the device?

We can do hardware scans on systems to obtain the UUID, but this all seems a little back to front. Any ideas?

Are you asking if there is a way to proceed with the Setup and Config process without knowing the UUID?

Follow me on Twitter: @GaelHof
Facebook: https://www.facebook.com/GaelHof

Have you downloaded the patches for the SCS release? The link below contains patches, FAQs, and more scripts that can be used for determining UUID and doing manual Setup and Configurations..

http://downloadfinder.intel.com/scripts-df-external/filter_results.aspx?strTypes=all&ProductID=2609&OSFullName=Windows+Server*+2003&lang=eng&strOSs=84&submit=Go%21

GH

Follow me on Twitter: @GaelHof
Facebook: https://www.facebook.com/GaelHof

Hi,

Thanks for the reply. I managed to right eventually. The initial cofusion was caused by the naming convention of the "New Intel Amt systems" and "Intel AMT systems" nodes in the SCS Console. It seems that new devices are added to the "Intel AMT systems node from where you can give them provisioning information. I was looking for them in the "New Intel AMT system" node.

Leave a Comment

Please sign in to add a comment. Not a member? Join today