• ×
    Information
    Need Windows 11 help?
    Check documents on compatibility, FAQs, upgrade information and available fixes.
    Windows 11 Support Center.
  • post a message
  • ×
    Information
    Need Windows 11 help?
    Check documents on compatibility, FAQs, upgrade information and available fixes.
    Windows 11 Support Center.
  • post a message
Guidelines
Seize the moment! nominate yourself or a tech enthusiast you admire & join the HP Community Experts!
Archived This topic has been archived. Information and links in this thread may no longer be available or relevant. If you have a question create a new topic by clicking here and select the appropriate board.

‎07-10-2018 04:19 AM

HP Recommended
Product: MT42
Operating System: Microsoft Windows 7 (32-bit)

Hi Everyone,

 

Past W-E we deployed our 3 Master images on 3 different ThinClient (MT41, MT42 & MT43).

 

When the deploy was terminated, I cleaned all the ThinClients entries in our HPDM (HP Device Manager) and make a new discover to get only the newly connected ThinClients. 

 

Bad news, there is only one ThinClient listed. I checked in the "Discover Device" task to get more details, and found all the ThinClient detected and listed with their Ip Address...

I Checked in the Other OS tabs but nothing.. Checked if any Filter was running on the list.. Nothing. 

 

So I update the HPDM to the version 9 (previously 😎 but no changes.

I try with an other HPDM installation from my lab and same problem.

 

I Finally understand that all the ThinClient get the same Device ID therefore they all have a diffrent MAC Address on their Ethernet Adaptater (and Wi-Fi adaptater).

 

After debugging it more deeply, I found that the FortiClient (VPN) that we installed on the ThinClient had configured a new Network Adaptater with always the same MAC ADRESS ( 00:09:0F:FE:00:01 ) and place this adapter in Position "0".

Because of this first position, HPDM based the Device ID on this Adaptater and display only one ThinClient because of duplicated Device ID.

 

 

So the question is :

Is there a Way to configure de HPDM to base the Device ID on an other Network Card position by default?

Or an other persistent Solution that avoid a new deployment or manual intervention on each ThinClient ?

 

Thanks  !

 

Kevin

 

Archived This topic has been archived. Information and links in this thread may no longer be available or relevant. If you have a question create a new topic by clicking here and select the appropriate board.
† The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the Terms of Use and Rules of Participation.
Didn't find what you were looking for? Ask the community
† The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the <a href="https://www8.hp.com/us/en/terms-of-use.html" class="udrlinesmall">Terms of Use</a> and <a href="/t5/custom/page/page-id/hp.rulespage" class="udrlinesmall"> Rules of Participation</a>.