I just discovered that some parts of the Intel AMT V9.0 System always alters the %windir%/system32/drivers/etc/hosts file on my Win 2k12 R2 Server.
It changes the localhost address to the name, I use for the dedicated kvm-NIC. The kvm.project.local IP is set to 192.168.1.200 in the AMT system and you can connect the kvm with vnc plus.
Anyway, you can find the altered line as following:
# 127.0.0.1 localhost
127.0.0.1 kvm.project.local # LMS GENERATED LINE
Since I am running a DNS-Server on that machine, the altered line always causes trouble.
On this machine (a new Dell T20 with Intel AMT V9) I have three dedicated NICs running:
1.: kvm.project.local with 192.168.1.200
2.: server.project.local with 192.168.1.10
3.: vm.project.local with 192.168.1.50
I am wondering why the AMT systems alters the 127.0.0.1 address. An added line i.e. 192.168.1.200 kvm.project.local could make sense, but why 127.0.0.1 kvm.project.local?
How can I prevent the AMT from changing the hosts file?
I also found those postings, but they're not really eye-openers for me, because they didn't provide any information how to solve this issue.:
a) /thread/7093?start=0&tstart=0 https://communities.intel.com/thread/7093?start=0&tstart=0
and the official statement: b) /docs/DOC-1247# jive_content_id_LMS_generated_line_in_hosts_file https://communities.intel.com/docs/DOC-1247# jive_content_id_LMS_generated_line_in_hosts_file
"LMS generates this line when there is a mismatch between the OS FQDN and the Intel® ME FQDN. This can happen, for example, when you swap hard drives between computers."
I would be very happy if you could find some time to help or provide some hints. :-)
Greetings from Germany,
For more complete information about compiler optimizations, see our Optimization Notice.