You are viewing limited content. For full access, please sign in.

Question

Question

Directory Server is Showing Different Hardware Fingerprint

asked on December 11, 2015

I was working with a client and when viewing the hardware fingerprint of the server in Directory Server it showed a different hardware fingerprint than the one that is shown in the executable.

Is this a known issue? Is there any specific reason why this might be happening?

0 0

Replies

replied on December 11, 2015 Show version history

Directory Server and the exe for showing HFWP should return the same fingerprint for any machine. However, I can think of a few reasons it would appear different:

  1. LFDS does not actively determine the fingerprint unless you click "Look Up". If it is pre-populating without clicking the Look Up button, it is pulling from existing data for that machine. If that's the case, it's possible that there was either a mistake when initially saving, or the HWFP has changed.
  2. Similar to 1., there was an issue in LFDS 9.2.1 where using the automatic lookup after the hardware fingerprint was changed did not save that new value. To workaround this, you should manually replace the hardware fingerprint for an application instance and save. This issue is resolved in LFDS 10.
  3. Are you comparing the same kind of fingerprint? Some products, or versions of products, require different machine information. There are two versions of the hardware fingerprint, and the mac ID, all of which should be shown in the hardware fingerprint EXE.

 

If you've checked on these both and they're still looking different, can you provide more information on how you're viewing the fingerprint?

1 0
replied on December 11, 2015

I am viewing both of the hardware fingerprints on the same machine.  Directory Server is also installed on the same machine as the server.  

It also is a virtual environment.

0 0
replied on December 11, 2015

If you are using LFDS 9.2, then the situation could be that you've registered an application instance to that same machine previously, so it has cached the original fingerprint value. Then at some point, the fingerprint value changed. Now when you register new application instances to that same machine, LFDS will use the old cached value which is no longer valid.

If that's the case, then manually enter in the new fingerprint value (do not press the "Lookup" button) and then save the application instance registration. This will update the cached fingerprint value so the next time you register an application instance on that same machine, it will use the new cached value.

Note that in LFDS 10, we've fixed the matter so that when you do press "Lookup" to get the new fingerprint value, it will also properly update the cached value.

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.