HP Device Manager labelling imported Thin Clients as 'Unidentified'

[Aviska88]

Hi all,

I'm hoping someone has come across this before.

I've got a fleet of HP t530 thin clients running ThinPro 8.0 that were discovered and imported into HPDM using an IP range, the devices are online and communicating correctly with HPDM. The device properties show:

• HP t530 Thin Client
• ThinPro 8.0.0
• Agent version 5.0.3675.41638

However all devices are being placed under the 'Unidentified' OS family rather than ThinPro 8.0 so I can't deploy any ThinPro 8.0 templates or task sequences to them. If I switch to the ThinPro 8.0 category and try to deploy a template, HPDM reports that no valid devices are available.

What's confusing is that HPDM clearly knows the devices are running ThinPro 8.0.0, as it's displayed in the Operating System column.

Has anyone seen this before?

• Is there a way to force the devices to be re-categorised from Unidentified to ThinPro 8.0?
• Does the HPDM agent need to re-register somehow?
• Would deleting and re-discovering the devices fix it, or is there another recommended approach?

I'd prefer to avoid reimaging or factory resetting 30+ devices if possible.

[Pallipurath]

Hi @Aviska88 

Welcome to the HP Support Community.

Thank you for posting your query.

The issue you are describing is likely caused by a mismatch between the HPDM Agent version and the ThinPro OS version, which triggers a new categorization policy introduced in HP Device Manager 5.0.14.

Why your devices are labeled 'Unidentified'

In HPDM 5.0.14, HP implemented a rule where devices running an unsupported or mismatched configuration are automatically moved to the 'Unidentified' tab. While ThinPro 8.0 is not yet "End-of-Support" (its EOS is April 2025), HPDM 5.0.14 is highly specific about which agent versions correspond to which operating systems.

According to the HPDM 5.0.14 Release Notes, there is a clear discrepancy in your current setup:

• Your Agent Version: 5.0.3675.41638 is explicitly listed as the agent for HP ThinPro 7.2.
• The Required Agent Version: For HP ThinPro 8, the correct agent version for this release is 5.0.3676.41638.

Because the device is reporting a ThinPro 7.2 agent on a ThinPro 8.0 OS, HPDM cannot correctly "identify" the device within its supported OS families and moves it to the 'Unidentified' tab.

Resolution: Update the HPDM Agent.

To resolve this and have the devices re-categorized into the 'ThinPro 8.0' family, you must update the HPDM Agent to the version matching the OS.

• Send an Update Agent Task: The standard procedure to resolve agent version issues is to use the HPDM Console to send an Update Agent task to the affected thin clients.
• Tab Restrictions: Be aware that for devices in the 'Unidentified' tab, HPDM 5.0.14 policy states that only the Wake-on-LAN task is typically available. If the "Update Agent" task is grayed out or unavailable in that tab, you may need to move the devices into a manual folder or try the "Update Agent" command via a right-click if the restriction is only on template deployments.
• Manual Discovery/Import: If the devices still do not re-categorize after an update, the sources suggest using the Import Devices dialog from the Console rather than the Automated Device Importer, as the automated tool sometimes fails to recognize existing devices correctly.

Answers to your specific questions:

• There is no "force" button in the GUI; categorization is automatic based on the reported OS and Agent version. Correcting the agent version is the intended way to "force" this update.
• It doesn't necessarily need to re-register, but it must be updated to the version HPDM 5.0.14 expects for ThinPro 8 (v5.0.3676).
• If the agent remains version 5.0.3675, re-discovery will likely result in the same 'Unidentified' status. However, a manual refresh of the Device View (highlighting a device and pressing F5) is a recommended workaround for general console display issues.

Note on Support: Your HP t530 thin client is confirmed as fully supported (F) for ThinPro 8 and 8.1 in HPDM 5.0.14, so once the agent is corrected, you should have full management capabilities.

Click Here 

Click Here 

Click Here

I hope this helps.

Take care and have an amazing day!