OpenInsight Authorisation Process


reauthI have recently been asked several times about the OpenInsight Reauthorisation process, how easy it is to use the process and what issues people might face.

The process is extremely easy when planned for because you have to get everyone off of the system and you need to make sure that there are no locks on the system, services running, etc.

The OpenInsight License Renewal and Installation/Upgrade Authorisation Process .pdf file that is located in the Documents folder under your OpenInsight installation contains ‘full’ details, but I have created a couple of videos and uploaded them to my usual RevSoftUK YouTube channel.

There are two videos.  The short video shows how quick and easy it is to authorise systems when the correct procedure is followed.  The longer video goes into a little more detail about why we need this process and some of the usual gottchas that we come across.  The longer video also has a couple of annotations about running the reauth.exe routine with administrator privileges if users don’t have adequate permissions and also about restarting the OEngineServer and other services that might be needed to run the application.

I hope that these videos are useful to developers and end users when reauthorizing their OpenInsight based systems for the annual renewals and also when adding additional users.

This process is applicable to OpenInsight 8.0.3 to 8.0.8, 9.x and it might be different for other versions of OpenInsight (i.e. the forthcoming OI10).

LB.EXE


We were recently approached by one of our OpenInsight supported clients with an OpenInsight executable which had been quarantined by a piece of security software.  The file which is simply called LB.EXE was flagged up as a ‘possible’ ransomware virus.

With all of the recent headlines about ransomware programs and the nightmare that they pose to people who open the ransomware file, I jumped on this one straight away.  A search on my computer quickly found the LB.EXE file in my copy of OpenInsight 9.4.  I googled LB.EXE and found no reported issues and running it through Norton and ThreatExpert also showed no issues to be concerned about.

My next stop was the support team here at Revelation Software and I learned that LB.EXE is a legitimate file that was used for the Database Manager in older versions of OpenInsight and it is therefore a legacy program that can now be removed if you are running version 8.x or 9.x of OpenInsight.

If you are still running older versions of OpenInsight, I would strongly recommend looking at upgrading to version 8.0.8 at the very least and preferably OpenInsight 9.4, being the currently supported version of the development suite.