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

Question

Question

Hardware fingerprint changes, Notification Needed!

asked on August 31, 2020

Hello Everyone,

I had my system go down this weekend because of a change to the HWFP on my LF server. I had no idea until people started calling me to ask why things were not routing correctly. I had no notification from the system that anything was out of order because Workflow just stopped working. So my question is, how can I get notifications from Laserfiche if the licenses become invalid because of an HWFP change? 

0 0

Replies

replied on August 31, 2020

Hi Lucas-

I just figured out how to do automated emails from events, which would probably work for you with regards to the license issue. The gist:

  1. Task Scheduler can be set up to trigger an action based on an event. You can set it to monitor the LF Server node in Event Viewer and then limit to specific IDs (you'll see the ID of the license issue in the Event Log).
  2. Task scheduler launches PowerShell as the command, then points to a .ps1 script as the argument.
  3. Your PS script will grab the most recent event from a specific Event Viewer node and can also be limited to just the ID number mentioned in point 1. The details are then sent through SMTP.
  4. In order to not get spammed, I put a "pause" at the end of my script to wait 15 minutes, and then on the Task Scheduler settings said that if an existing task is still running, don't do anything.

 

I learned this all from Google so that I could set up alerts for Import Agent.

Task Scheduler Action:

 

PowerShell script:

$A = Get-WinEvent -MaxEvents 1  -FilterHashTable @{Logname = "Laserfiche-ImportAgent-Service/Admin"}
$Message = $A.Message
$EventID = $A.Id
$MachineName = $A.MachineName
$Source = $A.ProviderName


$EmailFrom = "SENDADDRESS@domain.com"
$EmailTo = "TOADDRESS@domain.com"
$Subject ="Alert From $MachineName"
$Body = "EventID: $EventID`nSource: $Source`nMachineName: $MachineName `nMessage: $Message"
$SMTPServer = "YOURSMTPSERVER.domain.com"
$SMTPClient = New-Object Net.Mail.SmtpClient($SmtpServer, 25)
$SMTPClient.Send($EmailFrom, $EmailTo, $Subject, $Body)

Start-Sleep -s 900

 

4 0
replied on September 1, 2020

That's a great idea. Once I saw the task scheduler for an event I remembered I have done that before. I'll give this a try and let you know the results, but it does sound exactly like what I want. Thanks. 

0 0
replied on September 1, 2020

Hi Lucas,

The best thing to do is eliminate HWFPs in the first place. Laserfiche has an alternative license validation mechanism called "domain-locking" where the licenses check the servers' Active Directory domain (e.g. "contoso.com") instead of a HWFP.

You can switch to to a domain-locked license at no cost. Simply ask your Solution Provider to submit the request for you with the domain name. Once processed on our end, renew your primary license in LFDS and regenerate/replace all the old HWFP lf.licx application licenses with new domain-locked ones.

Cheers,

Sam

3 0
replied on September 1, 2020

Hello Samuel, 

This alternative license sounds great. What are the downsides to it?  

0 0
replied on September 1, 2020

Not so much a "downside" as a "restriction to be aware of", the domain licenses currently require that all servers hosting Laserfiche applications are domain-joined. The usual scenario where that comes into play is with a non-domain-joined "DMZ" server. 

We're addressing that limitation in the next point release of LFDS (10.4.5) though. It will allow reversion to HWFP validation for individual applications so the DMZ instance can use HWFP and everything internal can use domain validation.

2 0
replied on September 1, 2020

That's what I was worried about. I do have a machine that is in a DMZ so that I can have mobile available to users without having to be on a VPN.  

All my other boxes are on the domain so I would require this mix of license types. 

What the timeline for the next release of LFDS? 

0 0
replied on September 1, 2020

Quite soon - tentatively later this month. You won't have to wait long.

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

Sign in to reply to this post.