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.

Need help to install Kofax Capture 9.0 application. For version 8.0 I first had to install VRS, cause otherwise I got an error during the silent install of the. This Kofax Capture 10.2 product documentation can be downloaded from the Kofax Capture 10.2 Release Notes Documents Article (# 12748) or the Kofax Capture 10.2. Need help to install Kofax Capture 9.0 application. For version 8.0 I first had to install VRS, cause otherwise I got an error during the silent install of the. Look at most relevant Kofax 9 unattended install websites out of 4.26 Thousand at KeyOptimize.com. Kofax 9 unattended install. Silent, customized.

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.

Hero Quest 2 Pc there. I repeat this was for version 8.0, but parhaps it will help you out as well. 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 Lone Ranger 2 Wow Slider Software. there. 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).