HPDM - Not discovering T530 ThinOS Devices

[Equit]

I have a new WIndows Server 2016 Standard installation with HPDM 4.7 SP8 installed using SQL Express.

All services are running:

But it won't discover my devices.
In the DHCP pool it show's my devices:

Even after a factory reset it still won't discover my devices.
I can ping them from my server.

If I manually add them I see the following:

When I try to send Get Asset Information, it just stays orange and won't complete...

Please help... since i'm stuck on this issue for days now.

[Chen_HPDM]

Check if the DM agent is alive on the Thin OS device by exeucting:

ps ax | grep agent

you should be able to see something like

/usr/sbin/hpdmagent

Switch to /usr/sbin and execute ./hpdmagent if the process doesn't exist.

If this is a remote thin client you are not able to reach, please use the HPDMPortCheck.exe to check.

..\HP Device Manager\Console\bin\HPDMPortCheck\HPDMPortCheck.exe -a  10.249.4.202

[Equit]

Chen,

I did what you said and I'm getting the following:

root@HPace2d31795b7:/writable/home/user# ps ax | grep agent
11731 pts/3    S+     0:00 grep --color=auto agent

When I execute the port check I see the following:
C:\Program Files (x86)\HP\HP Device Manager\Console\bin\HPDMPortCheck>HPDMPortCheck.exe 10.249.4.202 -a
HPDM Agent port 40001 TIMEOUT.

So I am guessing I am having a firewalling issue(tho there no firewalls between ... )

Thx for the advice!! I'll go troubleshooting some more.

[Chen_HPDM]

Hi Equit,

It seems that the DM Agent is not running on your ThinPro unit.

Try: Switch to /usr/sbin and execute ./hpdmagent to start the process.

[Equit]

I see no firewalling issue. Is it possible the Agent is not running at all at the Thin Client?

See my previous message. I think that is a problem?

[Equit]

Chen,

I now see the follwing:

root@HPace2d31795b7:/usr/sbin# ps ax | grep agent
27922 ? Sl 0:00 ./hpdmagent
28557 ? S 0:00 ./hpdmagent
28651 pts/3 S+ 0:00 grep --color=auto agent

I dont think I'm doing it the right way:

root@HPace2d31795b7:/usr/sbin# ./hpdmagent
root@HPace2d31795b7:/usr/sbin# ps ax | grep agent
27922 ? Sl 0:00 ./hpdmagent
28557 ? S 0:00 ./hpdmagent
28651 pts/3 S+ 0:00 grep --color=auto agent
root@HPace2d31795b7:/usr/sbin#
root@HPace2d31795b7:/usr/sbin# ps ax | grep agent
27922 ? Sl 0:00 ./hpdmagent
30065 pts/3 R+ 0:00 grep --color=auto agent
root@HPace2d31795b7:/usr/sbin#
root@HPace2d31795b7:/usr/sbin# sudo ./hpdmagent
root@HPace2d31795b7:/usr/sbin# ps ax | grep agent
30963 ? S 0:00 ./hpdmagent
31019 pts/3 S+ 0:00 grep --color=auto agent
root@HPace2d31795b7:/usr/sbin#

C:\Program Files (x86)\HP\HP Device Manager\Console\bin\HPDMPortCheck>HPDMPortCheck.exe 10.249.4.202
HPDM Agent port 40001 TIMEOUT.

[Chen_HPDM]

Port check should work now.

Try rediscover the thin client to see if works.

[Equit]

C:\Program Files (x86)\HP\HP Device Manager\Console\bin\HPDMPortCheck>HPDMPortCheck.exe 10.249.4.202
HPDM Agent port 40001 TIMEOUT.

[Chen_HPDM · Accepted solution]

root@HPace2d31795b7:/usr/sbin# ps ax | grep agent
30963 ? S 0:00 ./hpdmagent

This indicate the agent process is running on the client side.

Now we need to figure out if there is any thing like NAT, firewall between subnet 10.249.4.202 and  10.255.52.0 (I assmue this is where your DM Console is installed).

Can you please provide more info on these two subnets?

[Equit]

The ThinClient is recieving it's IP-adress from a local DHCP-server (10.249.3.200)

IP-Settings for ThinClient are:
IP 10.249.4.202

Subnet 255.255.128.0

Gateway 10.249.0.254

DNS 10.255.52.11 / 10.255.52.12

IP-Settings for the HPDM Server:
IP 10.255.52.21

Subnet 255.255.255.0

Gateway 10.255.52.1

DNS 10.255.52.11 / 10.255.52.12

Firewall settings HPDM Server:

Firewall settings ThinClient:

It is possible to ping each other on IP and on Name.

Both machines are on a different network.