/build/static/layout/Breadcrumb_cap_w.png

How to package Kofax Capture 10?

I am trying to package Kofax Capture 10 now. The official installation guide has a section to install the package using MSI. The package also has many prerequisites as below:

 

VirtualReScan (VRS)

 

Sentinel Key Driver 7.5.0 or later

 

Visual C++ 2005 Runtime Service Pack 1 (32-bit version)*

 

Visual C++ 2008 Runtime Service Pack 1 (32-bit version)*

 

Visual C++ 2010 Runtime Service Pack 1 (32-bit version)*

 

.NET Framework 3.5 Service Pack 1

 

Visual Basic 6.0 Runtime Service Pack 6

 

Supported database

 

I am trying to package the above prerequisites one by one excluding the ones already in our production image, e.g. .net framework 3.5sp1.

 

My question is, how to repackage VRS?

 

I have tried to use "msiexec /i kofax VRS.msi /qb" to install it. But a "Kofax VRS Administratiron Console" window popped up. I had to click on Next button, then click on Next on the page of selecting a fax machine. Any way to make the package complete silent install?

 

Thanks.

 


0 Comments   [ + ] Show comments

Answers (3)

Posted by: sanhivi 11 years ago
Third Degree Green Belt
1

Hi,

I have created Kofax capture 9.0 application. Please check this may be helpful for you.
(1) This is a setup which will get installed from server location.
(2) This setup will install VC++ 2005 and 2008 SP’s, Virtual Rescan, Sentinel Drivers, Wibu Drivers and Kofax Capture application.
(3) Virtual Rescan is a setup which will call vendor msi with 1033.MST. So do the modifications in 1033.MST which are necessary (root drive, reboot suppress etc..)
Installed setupof virtual Rescan with
/S /V"INSTALLDIR=\"%PROGRAMFILES%\Kofax\Capture\ImgCtls\" /qn %VENDOR_LOG1%"
(4) Sentinel Driver setup will install one msi, but need to call the sentinel driver with the below parameters.
/S /V"ADDLOCAL=\"USB_Driver,Parallel_Driver\" /qn %VENDOR_LOG2%"
(5) Wibu drivers are a setup32.exe which will install some drivers and files/registries. This we can make silent by making some changes in the setup.ini file which is available with setup32.exe and call this exe directly which will install silently.
(6) Finally Kofax capture application will get installed with vendor msi. we need to call this with mst by doing necessary changes in the mst and passing below arguments.
/i "%INST%\KofaxCapture\Capture.msi" TRANSFORMS="%INST%\KofaxCapture\ZFS-ENG-KofaxCapture-9.0-NAFO-R1.mst" SETTINGS="%TEMP%\CaptureMSI1.txt" /qn %VENDOR_LOG3%
CaptureMSI1.txt file will have below information in it.
INSTALL_TYPE="Workstation"
SERVERDIR="\\abcd\xyz"
INSTALLDIR="C:\Program Files\Kofax\Capture"
STATION_ID="Computername"

We need to copy the file first into %Temp% location, then wrote one vb script to modify the STATION_ID by getting the computer name of the installation build then passed this argument to the mst.
(7) Finally update of kofax capture called with /S command if it is there.
 

Regards,

Sanhivi


Comments:
  • Thanks for your help!
    I had a look at the "Execute Immediate" MSI Script using Wise, there is below script:

    If UILevel<>"2" AND (....skipped some code here...) Then
    Execute Installed Program vrsadministrationconsole.exe Command Line /activate (ActivateVRSLicense)
    End

    I was using msiexec /qb to install the package before. Once I change it to /qn, the UILevel <>"2" is not satisfied, so the admin console window does not pop up any more.

    Another question is: Everyone is saying the Kofax Capture package needs to be installed from the server location.

    1. Is that the license server? My vendor gave me a unc2kofax.exe file to be installed onto the Startup folder of the Start menu to run. After that Kofax Capture could successfully connect to the license server from License Utility even I installed the package from another network location (not the server). So I assume it is not necessary to install the package from the server if there is such kind of executable like unc2kofax.exe.

    2. What issue will happen if it is not installed from the server?

    Thanks for your time! - nbafifa02 11 years ago
  • This "CaptureMSI1.txt" file is a renamed "CaptureMSI.txt" that is written in %TEMP% during the regular setup install. If you ever need a Standalone variant of that, this is how to get it and incorporate in the MSI install.

    Regards,
    Edwin - evasive2008 6 years ago
Posted by: homey 9 years ago
White Belt
0
Hello

Again I have only packaged Kofax Capture Client 9.0, but have managed to automate it with a VB script. From what I understand, it is only the first part of the install that needs to run fro the server, not the updates or any other extras, EG. Kofax Transformation Modules. Therefore my script only calls the first install from a server and everything else is packaged and deployed by SCCM. In our case Kofax also needs to be deployed from a regional server based on the user's location, so this has been factored into the script also. If the machine is not on an approved subnet, the install quits.

Set FSO = CreateObject("Scripting.FileSystemObject")
Set Shell = CreateObject("Wscript.Shell")
Set EnvVar = Shell.Environment("PROCESS")
Set objReg = GetObject("winmgmts:\\.\root\default:StdRegProv")

'___________________________________________________________________________
Dim strComputer, CmD,Q,LogFile,WorkDir
WorkDir = Split(WScript.ScriptFullName,WSCRIPT.ScriptName)(0)
Q = Chr(034)

set shellObj = WScript.CreateObject("WScript.Shell")
Set objNetwork = CreateObject("Wscript.Network")
strComputer = "."
Set objWMIService = GetObject("winmgmts:\\" & strComputer & "\root\cimv2")

'Identify Client Subnet to determine location
Set colAdapters = objWMIService.ExecQuery _
    ("Select * From Win32_NetworkAdapterConfiguration Where IPEnabled=True")

For Each objAdapter in colAdapters
    For Each strAddress in objAdapter.IPAddress
        arrOctets = Split(strAddress, ".")
        If arrOctets(0) <> "" Then
            strSubnet = arrOctets(0) & "." & arrOctets(1) & "." & arrOctets(2)
            x = 1
            Exit For
        End If
        If x = 1 Then
            Exit For
        End If
    Next
Next


'Map a drive to the appropriate regional server based on Client Subnet
Set colItems = objWMIService.ExecQuery _
    ("Select * From Win32_LogicalDisk Where DeviceID = 'X:'")

If colItems.Count = 0 Then
    Select Case strSubnet
        Case "192.168.XX"
            objNetwork.MapNetworkDrive "X:", "\\<SERVER1>\<INSTALLDIR>"
        Case "10.1.XX"
            objNetwork.MapNetworkDrive "X:", "\\<SERVER2>\<INSTALLDIR>"
        Case Else
            WScript.Quit(0)
    End Select
End If

'Extract path from mapped drive for server install variable
strUNC=FSO.GetDrive("X:").ShareName

'Install from mapped server
shellObj.Run "MSIEXEC /i " & Q & "X:\Capture.msi" & Q & " INSTALL_TYPE=" & Q & "Workstation" & Q & " SERVERDIR=" & Q & strUNC & Q & " /qn", 0, True

'Install update
shellObj.Run "MSIEXEC /p " & Q & WorkDir & "KofaxCapture-9.0.3_en.msp" & Q & " /qn", 0, True

'Remove Network drive to server
objNetwork.RemoveNetworkDrive "X:"   

WScript.Quit(0)

Posted by: homey 9 years ago
White Belt
0
Hello

Again I have only packaged Kofax Capture Client 9.0, but have managed to automate it with a VB script. From what I understand, it is only the first part of the install that needs to run fro the server, not the updates or any other extras, EG. Kofax Transformation Modules. Therefore my script only calls the first install from a server and everything else is packaged and deployed by SCCM. In our case Kofax also needs to be deployed from a regional server based on the user's location, so this has been factored into the script also. If the machine is not on an approved subnet, the install quits.

Set FSO = CreateObject("Scripting.FileSystemObject")
Set Shell = CreateObject("Wscript.Shell")
Set EnvVar = Shell.Environment("PROCESS")
Set objReg = GetObject("winmgmts:\\.\root\default:StdRegProv")

'___________________________________________________________________________
Dim strComputer, CmD,Q,LogFile,WorkDir
WorkDir = Split(WScript.ScriptFullName,WSCRIPT.ScriptName)(0)
Q = Chr(034)

set shellObj = WScript.CreateObject("WScript.Shell")
Set objNetwork = CreateObject("Wscript.Network")
strComputer = "."
Set objWMIService = GetObject("winmgmts:\\" & strComputer & "\root\cimv2")

'Identify Client Subnet to determine location
Set colAdapters = objWMIService.ExecQuery _
    ("Select * From Win32_NetworkAdapterConfiguration Where IPEnabled=True")

For Each objAdapter in colAdapters
    For Each strAddress in objAdapter.IPAddress
        arrOctets = Split(strAddress, ".")
        If arrOctets(0) <> "" Then
            strSubnet = arrOctets(0) & "." & arrOctets(1) & "." & arrOctets(2)
            x = 1
            Exit For
        End If
        If x = 1 Then
            Exit For
        End If
    Next
Next


'Map a drive to the appropriate regional server based on Client Subnet
Set colItems = objWMIService.ExecQuery _
    ("Select * From Win32_LogicalDisk Where DeviceID = 'X:'")

If colItems.Count = 0 Then
    Select Case strSubnet
        Case "192.168.XX"
            objNetwork.MapNetworkDrive "X:", "\\<SERVER1>\<INSTALLDIR>"
        Case "10.1.XX"
            objNetwork.MapNetworkDrive "X:", "\\<SERVER2>\<INSTALLDIR>"
        Case Else
            WScript.Quit(0)
    End Select
End If

'Extract path from mapped drive for server install variable
strUNC=FSO.GetDrive("X:").ShareName

'Install from mapped server
shellObj.Run "MSIEXEC /i " & Q & "X:\Capture.msi" & Q & " INSTALL_TYPE=" & Q & "Workstation" & Q & " SERVERDIR=" & Q & strUNC & Q & " /qn", 0, True

'Install update
shellObj.Run "MSIEXEC /p " & Q & WorkDir & "KofaxCapture-9.0.3_en.msp" & Q & " /qn", 0, True

'Remove Network drive to server
objNetwork.RemoveNetworkDrive "X:"   

WScript.Quit(0)

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ