Hi guys, we experience a strange issue with proxy-autoconfig (proxy.pac).
This function is used to determine when the client should use the corporate proxy or go directly to the internet based on which subnet its on.
We tracked down the problem to be caused by the following lines which the LANDesk-agent appends to the client computers hosts-file:
# 127.0.0.1 localhost
127.0.0.1 computername # LMS GENERATED LINE
Please notice that the original line is commented out by the LANDesk agent.
If we remove the line Landesk added, the proxy.pac-script works just fine.
What is the purpose of Landesk changing the clients hosts-file like this? Is there a way to work around this issue?
I haven't solution for your problem, but in my company, when a HP computer have Intel AMT activated, the line below is add in the host file:
127.0.0.1 HPSystem # LMS GENERATED LINE
I hope that can help you
Hi Pleix, thanks for the answer. I've been digging around some more and tried changing the line in the HOSTS-file to something else, and then the PAC-script works fine, but when I restart the service "Intel Active Management Technology Local Management Service", it changes the line back again to:
127.0.0.1 mycomputername #LMS GENERATED LINE
Hopefulle we find a way to change this behaviour. I'll do some more digging and check with the Intel vPro community. http://communities.intel.com/community/openportit/vproexpert
I suspect that this might be a HP-specific workaround to be able to AMT-provision the devices well. A few of the OEM's have folks jump through a few unusual hoops when it comes to AMT I've come to learn over the time, and this looks like one of them (I don't have HP systems, so this is theorizing at this point, but if the AMT provisioning works, and we forcibly do this for HP-systems, it stands to reason that this is so).
- Paul Hoffmann
LANDesk EMEA Technical Lead
Hi Paul, thanks for the reply.
I looks like you are right, it is indeed the LMS-driver (Local Management Service, and not LANDesk Management Service as I suspected) which adds this line to the hosts-file. This machine is a Lenovo so I guess HP is not to blame but rather IBM/Lenovo or maybe its Intel themselves which adds this to the base-package.
I guess I'll try removing this line and see if still AMT works.
It wasn't a dig at HP per se - it was more of an explanation that I've seen various OEM's do apparently "strange" things when it comes to AMT that don't seem to be documented anywhere, and then end up with stuff like this resulting in the scratching of heads .
In general, AMT seems to be particularly prone to "special workarounds" or whatnot, for one reason or another. Maybe just someone got burned on version 1 of AMT, and whatever workaround was in place then is still in place now? Historical artifacts like that could explain a fair bit ...
- Paul Hoffmann
LANDesk EMEA Technical Lead.