We would be happy to help, but we do have a couple of questions.
What is the device/scanner Manufacturer, Model, and OS in use?
What is the software you are using during the scanning process?
The Avalanche Scan Config option does not really set any parameters within the scanner. It is primarily used to apply network settings that were printed out from an Avalanche server. It is capable of applying registry keys if they were included to the scan to config profile.
Why would you need to have a remote desktop connection into the terminal server?
If you're scanning into a remote desktop environment you likely are using the device scanner wedge to handle the scan processing. I suggest increasing the intercharacter delay within your wedge application to something like 10-20ms.
The devices are Motorola MC9190-G Mobile Computers, using Windows Embedded Handheld 6.5 Classic. The terminal server they are connecting to is running the Sequential Parts Delivery suite by InSequence.
I read up about Scan Config by finding the manual for Avalanche here. I haven't been with this company very long, and there have been several instances where I had to learn things as I went along.
Thank you for any help.
That's how the vendor software works; each device uses a different login profile, depending on what role is being accomplished.
I'll have to figure out how to modify the scanning wedge. Thank you for the advice.
Update: I found a PDF file showing where that "Intercharacter Delay" setting was. On the affected devices, the delay was at 0...whereas, on a working device, the delay was at 10. I changed the delay to 10...and after that, the scan decoded properly! Thank you very much for the advice!