Question

How to find old hardware fingerprint and host ID

Laserfiche

Updated August 29, 2018

asked on August 27, 2018

We moved a server this weekend on Hyper-V and added storage to it - now our licensing is broken. I need to find my old hardware fingerprint and host ID used in the previous activation to deactivate and reactivate. I have a ticket open w/ our VAR but our users are needing access ASAP. There has to be better way to do this than to have to rely on someone else to manage this.

1 0

Replies

replied on August 29, 2018

You can find the old fingerprint in your current license (for the Laserfiche server, it would be the lf.licx file in the install directory). Open it in a text editor and look for an element that looks like this:

<HostFingerprint>027FDAC598D41D38EAFD2367DF3750E2</HostFingerprint>

You can find the host ID by running the utility Lidija mentioned. That's tied to the ethernet card and wouldn't change from adding storage.

2 0

replied on August 28, 2018

Peter, I had the same problem a few months ago - if you still have the old server you can find it yourself. Here is how you find it:

There is a Laserfiche Hardware Fingerprint Utility on your server, in the Laserfiche Server installation directory, it is called "showhwfp.exe" and mine was at C:\Program Files\Laserfiche\Server. Open the utility and type in the fully-qualified domain name, after clicking Lookup, you will see the Hardware Fingerprint and Host ID.

Deactivation and activation is easier in my opinion through elevated CMD:

1. First change directory to your Server: cd /d C:\Program Files\Laserfiche\Server
2. Run deactivation after plugging in your info:

ActivationToolNet4.exe -deactivate -key YOURACTIVATIONKEY -fingerprint YOURFINGERPTINT -hostid 00-00-00-00-00-00

3. Similar thing for activation, but now you will replace the fingerprint and hostID with the new server's info.

Hope it helps!

0 0

You are not allowed to follow up in this post.

Question

Question

How to find old hardware fingerprint and host ID

Replies

Sign in to reply to this post.