If you are seeing any failures in your log around setting the hostname during a Remote configuration it could be due to a underscore in the host name. Check out Terry Cutlers post on altiris juice @ http://juice.altiris.com/tech-tip/1622/underscore-not-supported-in-intel-amt-hostnames . Terry references the RFC952 - DoD Internet host table specification @ http://www.faqs.org/rfcs/rfc952.html. Here are the assumptions from that specification.
ASSUMPTIONS
1. A "name" (Net, Host, Gateway, or Domain name) is a text string up
to 24 characters drawn from the alphabet (A-Z), digits (0-9), minus
sign 
, and period (.). Note that periods are only allowed when
they serve to delimit components of "domain style names". (See
RFC-921, "Domain Name System Implementation Schedule", for
background). No blank or space characters are permitted as part of a
name. No distinction is made between upper and lower case. The first
character must be an alpha character. The last character must not be
a minus sign or period. A host which serves as a GATEWAY should have
"-GATEWAY" or "-GW" as part of its name. Hosts which do not serve as
Internet gateways should not use "-GATEWAY" and "-GW" as part of
their names. A host which is a TAC should have "-TAC" as the last
part of its host name, if it is a DoD host. Single character names
or nicknames are not allowed.
Activation Blog
7 Posts tagged with the vpro_expert_center tag
Nick & I got together this week and evaluated a few platforms for their AMT settings in the BIOS. In this video, Nick explains how to get into each BIOS and where the options for AMT are ( or for that case where they are NOT ).
Here are a few screen shots of two of the platforms. We are also going to publish out a matrix of the systems with drivers, bios settings that Frank has been working on.. stay tuned for the link.
I witnessed our Internal IT guys defining a BKM that I thougth was very relevant to share out to the community, therefore let me explain.
Challenge: How can you use a mgmt console to read the AMT version so you can write a report in your mgmt console?
Output: You need to have a value placed into the registry that has data whether it's all of the BIOS, MEBx, SOL, HECI, etc.. driver versions, then you can read this data into a mgmt report.
Solution: run MEInfowin.exe and redirect the output to a text file using the “>” operator
Example --
Then use your mgmt console to read these values & report out. The internal IT guys are doing this to check versions.
Thanks Intel IT folks for the BKM.
The USB Key Provisioning Utility (UKPU) tool is designed to create a valid USB key for provisioning Intel® AMT Systems. The UKPU tool prepares a USB Flash drive, copies the requested setup.bin to the drive, and also verifies that the setup.bin is saved using the proper procedures necessary to ensure that it is detected by Intel® AMT.
The tool has a 'repair' mode that allows you to take an existing USB Key and reconstruct it to ensure the setup.bin is visible to Intel® AMT. In addition, you can set up a USB Key using any renamed setup.bin file on your computer, and the tool will automatically ensure it is renamed to 'setup.bin' when setting up the key.
Here's a 3 minute video overview of the tool's capabilities (Click here to view video on YouTube):
Both binary only & open source licensed source versions available at the download site.
DOPD SW Engineering Team
Today we offer the USB Key Provisioning Utility (UKPU) focused on one-touch provisioning and the Intel® AMT Reflector which offers a unique implimentation allowing an Intel® AMT client to access/manage some Intel® AMT functionality locally via the OS without entering the management engine directly (usually via BIOS).
Click here to learn more about Intel® AMT Reflector or here to download directly. 
Click here to learn more about USB Key Provisioning Utility (UKPU) or here to download it directly. 
Tell us what you think!
DOPD SW Engineering Team
