I have a problem with the Host Name Update in vPro PCs.
not branded (local manufacturer);
MotherboardDQ965GF (AMT 2.1.3);
latest BIOS update (25, Nov, 2007);
Windows XP Pro SP2;
latest ME drivers;
Intel vPro Test Utility (ctpenu03.exe) passed;
Microsoft Windows Server 2003 R2 Domain;
Microsoft Windows Server 2003 R2 DNS;
Microsoft Windows Server 2003 R2 DHCP;
Landesk Management Suite 8.8
When I update the PC name in Windows and/or join the PC to the Domain, the corresponding fields (hostname/domain) in the vPro BIOS Section, don't update.
We have older PCs (AMT 1.x) and, when I change the Computer Name in Windows, the corresponding field in the vPro BIOS Section change.
- Intel® vPro™
Take a look at http://communities.intel.com/docs/DOC-1431 AMT Reflector. It will give you the ability to sync the OS and AMT hostnames for clients running in SMB mode. Are you using TLS based authentication in Enterprise mode? If you are using non-TLS then AMT Reflector should let you sync the OS and AMT hostnames. If you are using TLS you will need to delete the client from LANDesk and then do a manual re-provision of the client and manually sync the hostname.
I tried to use Reflector, but it didn't work very well.
I succeeded in GETTING AMT Information, but I got an ERROR when I try to SET the AMT Host Name.
I found that both INTEL COMMANDER and DIRECTOR can be used to update AMT Host Name from a console and they do work.
However, I think that the vPro Host Name Update Feature should be RESTORED: it's very useful, since OS Name can frequently change!!!
It could be very useful a Commander/Director Feature to SYNC OS Name and AMT Host Name for a SET of computer.
I represent the team that produced AMT Reflector. We're attempting to replicate the issue you describe about getting an error when trying to SET the AMT host name. Can you describe the difference / additions in your configuration to that described in our intro video & guide document (available here --> http://communities.intel.com/docs/DOC-1431).