01-07-2013 01:26 PM
The HP Device Manager documentation states that HP thin clients with the HPDM agent will automatically do a DNS lookup for a DNS entry of "hpdm-gateway" to identify an HPDM gateway and connect to it. However in practice our t510s running ThinPro 4 are looking for a DNS entry of "auto-update", which they obviously fail to find. We have a large network and I don't necessarily want to stick out a global non-descript name of "auto-update" for the HPDM in DNS. Is there some way to configure what DNS entry it looks for so that it will actually find our HPDM? I specified it manually in the agent under "current gateway" and then pulled the image from that device and pushed it to another device, and the second device did not retain this information. I do not want to do DHCP tagging to identify the HPDM server as that would involve a committee of our networking team to monkey with DHCP, and was told a DNS entry of "hpdm-gateway" would be sufficient. Ideas? We are running HPDM 4.5 and t510s with ThinPro 4 vT6X42019.
07-02-2014 12:30 PM
Our network is set up with one Windows server as the HPDM repository, gateway, and server. It detects all 50+ devices across all subnets with only the "hpdm-gateway" DNS entry. No "auto-update" required. Have you opened all the necessary ports on your gateway/server? There's a list of necesssary ports in the HPDM guide.