https://community.intel.com/t5/Intel-vPro-Platform/vPro-hostname-and-domain-name/m-p/190850#M72 <P>bbelko,</P><P>There are multiple reasons you should configure the hostname and domain name in the MEBx. The most important being that if you don't define an FDQN that can be resolved by DNS, then after configuration you might not be able to connect to AMT. Another important reason is security, if you're planning on using either Kerberos authentication or TLS then you will need to define a hostname and domain name. Beyond that, things like 802.1x, EAC (End-point Access Control), and Fast Call for Help all require an FQDN to be defined in MEBx to work.</P> Tue, 23 Jul 2013 17:48:57 GMT Alan_A_Intel 2013-07-23T17:48:57Z https://community.intel.com/t5/Intel-vPro-Platform/vPro-hostname-and-domain-name/m-p/190849#M71 <P>I am wondering for what purpose we need to configure hostname and domain name in MEBx configuration? Just for test I leave it blank and I can connect to such machine via vPro using FQDN. So I assume that DNS lookup is performed </P> Fri, 19 Jul 2013 09:35:59 GMT https://community.intel.com/t5/Intel-vPro-Platform/vPro-hostname-and-domain-name/m-p/190849#M71 BBelk1 2013-07-19T09:35:59Z https://community.intel.com/t5/Intel-vPro-Platform/vPro-hostname-and-domain-name/m-p/190850#M72 <P>bbelko,</P><P>There are multiple reasons you should configure the hostname and domain name in the MEBx. The most important being that if you don't define an FDQN that can be resolved by DNS, then after configuration you might not be able to connect to AMT. Another important reason is security, if you're planning on using either Kerberos authentication or TLS then you will need to define a hostname and domain name. Beyond that, things like 802.1x, EAC (End-point Access Control), and Fast Call for Help all require an FQDN to be defined in MEBx to work.</P> Tue, 23 Jul 2013 17:48:57 GMT https://community.intel.com/t5/Intel-vPro-Platform/vPro-hostname-and-domain-name/m-p/190850#M72 Alan_A_Intel 2013-07-23T17:48:57Z