We are using Metaframe XP FR2. We will have some workstations connecting both using Program Neighborhood (when in our office), and using NFuse (when accessing the citrix server over the internet). Some notebooks are also connecting both ways and they don't all have floppy drives. In the Citrix Connection Configuration tool under Client Settings I have selected "Connect client drives at logon" to allow those workstations and notebooks that do have floppy drives to be able to use them when a citrix based application requires them to use the floppy drive. The A: drive is not hidden on the server. (The clients also may have need to access their local hard drives this way too).
Two users have no floppy drives on their notebooks and when they attempt Windows explorer functions such as "Save as" they experience a delay during which the machine appears to freeze for about three to five minutes (presumably while the explorer function tries to find the floppy drive). How can I address this problem? There should not be an A drive for these machines unless the drive has been plugged in by the user. How do I handle this for PN and Nfuse when (1) the workstation has no floppy but has a Zip disk or LS120, and (2) when it is a thin client with no drives of any kind?
Thanks for any help.
Two users have no floppy drives on their notebooks and when they attempt Windows explorer functions such as "Save as" they experience a delay during which the machine appears to freeze for about three to five minutes (presumably while the explorer function tries to find the floppy drive). How can I address this problem? There should not be an A drive for these machines unless the drive has been plugged in by the user. How do I handle this for PN and Nfuse when (1) the workstation has no floppy but has a Zip disk or LS120, and (2) when it is a thin client with no drives of any kind?
Thanks for any help.