06-02-2011 08:23 AM
Can anyone tell me why the Kofax export script 9.0 only supports standalone Kofax Capture installations as listed in the documentation or is there a workaround for Kofax Capture client/server installations.
This is not listed as a bug and is a major deviation from the export scripts of previous versions. I would think that the majority of Kofax Deployments in a production environment would be client/server.
07-07-2011 07:18 AM
I'd be very interested in hearing about what you encountered trying to use Kofax 9.0 release script with TRIM 7.1.
We've seen some intermittent issues using the release script with a Kofax KCNS environment so I'm curious if your experiences and workaround have any relationship to what we're encountering.
02-03-2014 12:11 AM - edited 02-03-2014 12:13 AM
Apologies for letting this topic die as I cannot remember receiving notification of your replies.
Using a UNC path to store scanned images result in errors during the export to HP TRIM queue processing.
1. Map a network drive on the Kofax server e.g.. “K:” to \\KofaxServer\capturesv\images.
2. During batch class configuration use K:\ for the image folder.
3. On each Kofax station with HP TRIM Export connector installed map a network drive e.g.. “K:” to \\KofaxServer\capturesv\images
When Kofax batch classes run on either the server or client it will be configured to use K:\ thus export to TRIM successfully.