Hi,

I am working on "Kofax Capture 9.0" application. This application has to be installed from server location.

Can any body has idea how to package this application means what are the necessary steps we should follow for this application.

Thanks,
Sanhivi
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
Yes, a couple of people have had ideas. And they posted them on AppDeploy. Perhaps you'd like to use AppDeploy's 'Search' facility.....?
Answered 04/28/2011 by: VBScab
Red Belt

Please log in to comment
0
Hi,

I have read everything related to Kofax application...
But i require how to install the individual apps silently.... like Wibu Driver installation....

Thanks in advance....
Answered 04/29/2011 by: sanhivi
Second Degree Green Belt

Please log in to comment
0
In seeking answers to life's problems, you'll find that it helps to ask the right questions in the first place.
Answered 04/30/2011 by: VBScab
Red Belt

Please log in to comment
0
What I remember from Kofax 8 (besides the fact that's it's a pain to package) is the following:

3 major parts in the setup:

1) KTM = MSI installer
2) VRS = VirtualRescan = MSI installer
3) Setup.exe, indeed has to be run from the server, and best of all, needed a reboot in the middle.

For version 8.0 I first had to install VRS, cause otherwise I got an error during the silent install of the setup.exe. The main install was made silent using an .ini file called ACInsOut.ini and the following command-line:

setup.exe /s /i:C:\Temp\ACInsOut.ini /NoVRS

It's possible that the ini file had to be on the local machine, not on the network, for this to work, I don't remember.
Then I made a second script for the post-reboot part. I had to remove some regkeys to trick the installer into thinking the installation could be finalised.
There's a thread on these forums that I'm sure you can find with a little search, that details all the stuff I needed to tweak. I poured it all into 2 vbs scripts (pre- and post-reboot) and ran it with our distribution system.

I repeat this was for version 8.0, but parhaps it will help you out as well.

Rgds,

PJ
Answered 05/02/2011 by: pjgeutjens
Red Belt

Please log in to comment
0
I am in the process of developing a package for Kofax 9.0 for our workstations. Our deployment was complicated by the fact our users are not local administrators on their machines and we could not use a generic account to perform the installation. We also create our collections in SCCM based on AD queries so the application is advertised to users and not to machines so the install had to run when the user was logged in. I am still developing, but I have had initial success in the following manner in SCCM 2007 SP2. The only interaction required is that the user must log back into their machine as themselves following the reboot after the prerequisite install.

I divided the install into separate SCCM programs within the same package. I created a mandatory assignment to run the the application install program and made the prerequisite install program a "run this first" requirement for the application installer. The programs are set to run as administrator (for SCCM the administrator is LOCALSYSTEM) and allow user to interact (so that installation progress is displayed).

I followed the Kofax documentation for a disconnected network install using the setup.exe and an 2 ini files - one for the prerequisites (KC9_Prereq.ini) and the other for the application install (KC9_ServerIni.ini).

Prereq install
Initially, I tried to run the prereq install from SCCM via the command line: setup.exe /auto /i:KC9_Prereq.ini , but the setup was returning a 1 and SCCM was interpreting this as a failure and would not subsequently launch the application install. So I ran the setup from a wrapper script that passed the same parameters to the setup, returned a 0 to SCCM and restarted the machine. I set the "after running" option in the SCCM program to "Program restarts computer."

Here are the contents of my KC9_Prereq.ini - Plug in your SerferFilesPath siteservername etc as needed.
[Main]
InstallType=Workstation
SuppresFinalReboot=No

[SystemFiles]
SystemFilesOnly=Yes
SkipSystemFilesUpdate=No
SuppressSystemFilesReboot=Yes

[Path]
;This path represents the environment you are installing from, this path will vary based on environment.
ServerFilesPath=\\yourkfoaxserver\CaptureSV
;This is the destination path on the workstation, this is the default.
WorkstationPath=C:\Program Files\Kofax\Capture

[Identification]
SiteName=yoursiteservername
;RebootUserID=######
;RebootUserPassword=************
;RebootUserDomain>=yourdomain

Following the prereq reboot, the user must relog as themselves. After logging in, SCCM resumes the install.

Application install:
I execute the setup from a wrapper script passing the following: setup.exe /auto /i:KC9_ServerIni.ini . ini contents listed below.

[Main]
InstallType=Workstation
SuppresFinalReboot=No

[SystemFiles]
SystemFilesOnly=No
SkipSystemFilesUpdate=Yes
SuppressSystemFilesReboot=Yes

[Path]
;This path represents the environment you are installing from, this path will vary based on environment.
ServerFilesPath=\\ip.ip.ip.ip\CaptureSV
;This is the destination path on the workstation, this is the default.
WorkstationPath=C:\Program Files\Kofax\Capture

[Identification]
SiteName=yoursiteservername
;RebootUserID=######
;RebootUserPassword=************
;RebootUserDomain>=yourdomain

I am assuming you could remove the requirement to have the user log back in and execute the process from a single program ins sccm if you have access to a generic ID with local administration privileges on the machine. If you can provide generic credentials to perform the install, you can adjust the ini file to not skip system files, allow system file reboot and specify reboot user ID, pass and domain as your generic. This would allow the application to execute the prerequisite installer, reboot, autologin, and resume the application install. For us that would require leaving the credentials for the generic in a clear text file on the deployment share so this was not an option...

Similarly, if the software was advertised to machines, not users, I am assuming you could set the programs to run whether or not a user was logged in and avoid the user login altogether.

Hope this helps,

Jason
Answered 05/10/2011 by: speechdevil
Yellow Belt

Please log in to comment
0
Check the license terms and make sure that they allow per-user installs. To number the applications I've encountered which do I wouldn't need many fingers.
Answered 05/11/2011 by: VBScab
Red Belt

Please log in to comment
Answer this question or Comment on this question for clarity