I believe what Josh is going for is to not have to manually generate a license file in the license manager for each of his 60 Scanconnect installs.  Manually generating and handling 60 licenses files and setting everything up would negate any benefit by doing this unattended.  Is there any way to pass some kind of /RIOLicenseServer parameter through the ScanConnect Setup.exe as to install Scanconnect unattended through command prompt and have it retrieve and register the license through the RIO license manager, just like if you were to install Scanconnect manaully and choose the "Activate using RIO License Manager" radio button.

Alright, I get the confusion now, sorry about that (and then I was on vacation, go fig).

First off, I didn't mean we have something in the works, just that we had identified that this would be something that would probably be desired and did not, at the time, have a better solution in place. I will see if it's possible for us to do unattended LM registration through Setup in the future, but it's not an active item at present. I agree that it seems like a lack in the current system, and I'll see if we can get that functionality in some way in the future. It would be as completely new functionality though, not as a bugfix.

To the specific case, good idea with ARPSYSTEMCOMPONENT. I see why that doesn't work, but it made me think of a different idea. It's a couple steps (and I probably wouldn't suggest it if it wasn't clear that I'm pretty sure you know what you are doing here) , but it should actually resolve the add/remove programs issue. The reason the ARP information doesn't show up is that it's actually installed by a different component, through Setup, for various reasons. So what you could do is install both Setup+ARP first, and then Scan Connect through the msi. Here's the steps you'd take:

  1) Make a copy of your Scan Connect installation and remove the two ScanConnect msi files from the Setup directory. This will cause Setup to just skip the main SC installation package.

  2) Run a silent install on that Setup package. Since the main SC package isn't present, it won't give you hardware instance issues. This will setup the Add/Remove programs element as well as some other niceties.

  3) Install the Scan Connect msi directly through msiexec along with your license file.

I tried this one out, and in the end it should basically get you what you are looking for. You'll be able to bulk install Scan Connect without having to individually register each instance in the LM separately, while still having a complete installation.

To the licensing question itself, yes, the license agreement stipulates that you must be licensed for the amount of machines that you install Scan Connect on. License manager registration is not strictly speaking mandatory for that.

I'm OK using the setup.exe for deployment...

"

Unattended Install

Unattended installation allows an administrator to perform custom unattended installations of ScanConnect either from the command prompt or using SMS.

Syntax

There is a specific format for the string you will use to perform a command line or unattended installation of Laserfiche ScanConnect.

"InstallerPath/Setup.exe" SetupParameters Properties "

So you're saying I can generate 1 license from the RIO License Manager and use that for deploying to 60 some workstations?  How will that work since it uses a hardware fingerprint ID for each machine?

Which machine should I generate the license against?  The RIO LM server?

Thanks for the reply!

Brandon and Josh, that is exactly my point. The section I pointed to, through msiexec in this one case, will address exactly that. There's no way to do /RioLicenseServer (although that's a good idea to have) but we've already got a method for you for Scan Connect. Or rather, we have a method that works for now since we expected this to come up and a more complete solution as you've suggested here isn't implemented yet. But it's got to go through the msiexec instructions at the very bottom of the guide.

We will have to pass on upgrading to 8.3 until the bugs are worked out in the installer.  Running the MSI would require us to build an uninstall package for 8.0, push that out to everyone first, then run the install for 8.3...

We'd be OK with using MSI and building an uninstall package ourselves for 8.0 if you could register against the license manager AND it showed up in add/remove programs...but it doesn't.

Do you have a timeframe of when these bugs would be worked out?

Thanks

I'm not sure what you mean by bugs. I provided a specific set of instructions for exactly what you are looking for. Are they not working?

As far as uninstalling Scan Connect 8.0, you certainly shouldn't need to create an uninstallation package yourself. I believe the command line is:

"C:\ProgramData\{7CE6EDBD-894D-4D6A-AE16-8C28C2C2F02E}\Laserfiche ScanConnect 8.exe" REMOVE=TRUE MODIFY=FALSE /s

It's been a while since I've worked with Scan Connect 8.0 though, so if that's not correct you can see what that value of HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\Laserfiche ScanConnect 8\UninstallString is (the /s is just to run in silent mode so it won't be in that string).

Is ScanConnect 8.3 licensed per machine or can we have as many installs as we want of it?

This route does not register the individual machines against the License Manager, only the one I manually registered.  What's the point of having ScanConnect 8.3 register against our License Manager?

The app doesn't show up in add/remove programs after being installed using Microsoft's installer.  Using setup.exe does.  I tried adding in the "ARPSYSTEMCOMPONENT=0" switch with the MSI installation, no luck.

From what I gathered from your earlier reply, you made it sound like a more "complete solution" was in the works:

"Brandon and Josh, that is exactly my point. The section I pointed to, through msiexec in this one case, will address exactly that. There's no way to do /RioLicenseServer (although that's a good idea to have) but we've already got a method for you for Scan Connect. Or rather, we have a method that works for now since we expected this to come up and a more complete solution as you've suggested here isn't implemented yet. But it's got to go through the msiexec instructions at the very bottom of the guide."