CoreyWilson
IS-IT--Management
Hello all,
My Citrix clients were/are having an idle timeout issue with there mapped network drives, where they receive an x after a prolong period of inactivity. I had not changed this from the default until three days ago. On each of the servers I set the command net config server /autodiscconect:-1 and it says command succesfully applied. However some users still end up receiving these red x's EVEN if they were users logged off before applying the changes. I also set this one the server hosting each of the mapped network drives. All my citrix users use roaming profiles, and Im wondering if somewhere in there roaming profile it is saving this old setting and not updating it with the change I made to the servers to disable the timeout value on mapped drives. The biggest problem here is users personal address books as well there personal folders are stored on there network drives, so needless to say when and if they open outlook before opening a drive in the morning that is x'ed out they receive errors stating outlook cannot find the specified files and what have you.
Is there a trick to resolving this issue? Also, I restarted all three servers last night and reset this command as soon as they came up to ensure it was loading clean and no user sessions were active.
Thanks!
My Citrix clients were/are having an idle timeout issue with there mapped network drives, where they receive an x after a prolong period of inactivity. I had not changed this from the default until three days ago. On each of the servers I set the command net config server /autodiscconect:-1 and it says command succesfully applied. However some users still end up receiving these red x's EVEN if they were users logged off before applying the changes. I also set this one the server hosting each of the mapped network drives. All my citrix users use roaming profiles, and Im wondering if somewhere in there roaming profile it is saving this old setting and not updating it with the change I made to the servers to disable the timeout value on mapped drives. The biggest problem here is users personal address books as well there personal folders are stored on there network drives, so needless to say when and if they open outlook before opening a drive in the morning that is x'ed out they receive errors stating outlook cannot find the specified files and what have you.
Is there a trick to resolving this issue? Also, I restarted all three servers last night and reset this command as soon as they came up to ensure it was loading clean and no user sessions were active.
Thanks!