Intel vPro - Manual (Page 23)

Intel® vPro™ and Intel® Centrino® Pro Processor Technology Quick Start Guide
23
Skip to Step 5: Discover Intel vPro Clients through the Management Console, on page 27.
Note: You can also test Remote Configuration using a LANDesk generated certificate. The appropriate
server certificates are already in place. However, the client hash needs to be placed into the Intel ME
BIOS on the Intel AMT 3.0 client. The client hash is automatically generated and stored at the
beginning of the AMTDiscService.log file. It will look something like this:
Fri, 30 Nov 2007 11:30:37 InitInstance()
Fri, 30 Nov 2007 11:30:37 LANDesk(R) Intel AMT Provisioning Service
Fri, 30 Nov 2007 11:30:45 sha1 hash: (32A1-F117-AB25-0E1B-482B-7EFE-C0BE-92A7-B090-
D416)
Fri, 30 Nov 2007 11:30:45 md5 hash: (D29A-E72B-1029-846C-CE50-4C52-82EC-8F24)
Fri, 30 Nov 2007 11:31:01 Hash added to DB
Fri, 30 Nov 2007 11:31:01 Server listens for incoming connections.
The administrator will need to place the sha1 hash in the ME BIOS on the client.
For further detailed information on obtaining and configuring certificates see file Installing VeriSign
Certificate for Landesk 8.8.pdf at web site http://communities.intel.com/docs/DOC-1639.
You can set several Intel ME and Intel AMT parameters in the LANDesk Management Suite (LDSM), just
as you would manually in the Intel MEBx directly on the individual client. Intel vPro parameters set in
the management console are applied to all Intel vPro machines being provisioned.
Step 4B: OEM Pre-configuration – Factory State to Configured State
Most OEMs are willing to provide the service of changing the Intel vPro client from factory state to setup
state by entering the password and client authentication information into the Intel MEBx on each client
system for you. This often requires an additional fee to the OEM. This method is most useful when an
Intel vPro client machines are to be delivered directly to the end user from the manufacturer.
The authentication information (security keys) can be provided to the OEM for loading into the client
system’s BIOS (via the Intel MEBx), or the OEM could provide you with a list of keys they generated.
The keys must match between the Intel vPro machines and the management console. The
management consoles have an option to import and export keys to facilitate this transaction.
If you ordered your Intel vPro client systems pre-configured with Intel MEBx password and client
authentication information already loaded by the OEM, then they are already in a Setup state. When
you connect the client systems to the network and power them on they will automatically authenticate
themselves with the provisioning server and provisioning will occur (assuming you performed Steps 1-3
above). Then they will be in a Configured state, ready to be discovered and managed by the