memory keys on thin clients using W2K3

[amoss24]

I am running a room containing 30 wise thin client terminals on a Windows 2003 server running terminal services.

When using a USB memory key on a terminal it takes a long time for the key to activate and become usable, but using usb floppy or cd drives the connection is instant and i dont have problems with any other ports on the terminals.

Does anyone else have this problem with slow usb keys, or know a fix to speed things up.

Note: if the memory key is not a fat file system, the key tends to get blanked when its plugged in.

thanks all

oh yes one more thing im using rdp 5.1, on the terminals with drive mapping

[nonsence]

i can't give ya specific info on how to fix your problem but i can give you two tips

1) as far as i remember, you can't mount drive letters while using a terminal session. so you need to mount stuff inside folders. BUT i never tried this for usb disks, only on pgp disks.

2) older usb flash drives are mounted by Windows as physical hard drives, while the newer drives get mounted as removable devices. this at least tells me that drivers and firmware upgrades have taken place since the few years that usb drives came out.

so this hints at the small possiblility that you are having a driver related issue...... but most likely not.

i would look into the first point. and i would check security policies to see if terminal session users can add drivers, add devices, and mount file systems, etc etc. just cus you log in as an admin doesn't mean you can do everything.

[phatty]

We use WYSE terminals the usb drive shows up as a system drive, shows up as a Floppy Drive.

I too have problems with the drives taking an eternity to become useable but not when relatively empty (say 5MB of spreadsheets) when its actually quite quick.

As it gets worse as the disk fills up I can only assume that it is because the USB ports on the termminal are 1.1 and it is having to access the entire contents of the disk before they are accessable.