Let me just state at the outset that I am fully aware of the folly of using a server as a workstation and if someone could convince my sales staff that saving the $500.00 it would cost to put in a bottom feeder PC for the receptionist to use is a false economy I would be a very happy camper. Actually I would be happy if you could get one of my sales guys to admit that server and workstation are spelled using different letters of the alphabet; all they see is a big, fast computer.
That having been said, has anyone else had the experience of using scanning software (TWAIN interface scanner drivers, haven't tried ISIS drivers) on a Terminal Services box? When TS is installed in app sharing mode it seems to break all communication between the scanning software and the TWAIN driver but, and here's the interesting part, the bundled Kodak imaging application works just fine. Why not use the bundled app? The end user is, to be circumspect, not overly gifted with synaptic connections so we have labored long and hard to reduce the required steps for scanning documents into the database app to a single button click. Having to retrain the user to use not only the Kodak imaging app but the TWAIN interface app is not something that I or my IT guys have enough man-hours available to accomplish anytime before the sun becomes a small, dark cinder.
I have installed the TWAIN driver and app before adding TS and after installing TS but in all instances the communication is broken when TS is installed. Administrator mode is not an option (although testing shows that scanning is not broken in admin mode) because I have local users in my AR department who must access the remote server via TS to run a medical billing application.
I realize that this is a long shot but what the heck.
Thanks,
md
That having been said, has anyone else had the experience of using scanning software (TWAIN interface scanner drivers, haven't tried ISIS drivers) on a Terminal Services box? When TS is installed in app sharing mode it seems to break all communication between the scanning software and the TWAIN driver but, and here's the interesting part, the bundled Kodak imaging application works just fine. Why not use the bundled app? The end user is, to be circumspect, not overly gifted with synaptic connections so we have labored long and hard to reduce the required steps for scanning documents into the database app to a single button click. Having to retrain the user to use not only the Kodak imaging app but the TWAIN interface app is not something that I or my IT guys have enough man-hours available to accomplish anytime before the sun becomes a small, dark cinder.
I have installed the TWAIN driver and app before adding TS and after installing TS but in all instances the communication is broken when TS is installed. Administrator mode is not an option (although testing shows that scanning is not broken in admin mode) because I have local users in my AR department who must access the remote server via TS to run a medical billing application.
I realize that this is a long shot but what the heck.
Thanks,
md
