All,
I have a remote site(Tampa) with users complaining of slow search of a shared folder in the NY office file server. I have tested this and confirmed that NY users are not complaining of the slow browse/search/lookup of the same shared folder. I believe its the latency between the VPN and also the shared folder is HUGE. I was thinking of what solutions that might fix this...let me know if you think they can be solutions
- index the shared folder in the remote workstations
- index the shared folder in the file server of the shared folder Windows 2008 R2
- publish the remote app of the shared folder in Terminal Service
- (Last choice) is copy the shared folder to the remote site since that the users in that location use it most.
Please let me know what you think which solution might be better.
I have a remote site(Tampa) with users complaining of slow search of a shared folder in the NY office file server. I have tested this and confirmed that NY users are not complaining of the slow browse/search/lookup of the same shared folder. I believe its the latency between the VPN and also the shared folder is HUGE. I was thinking of what solutions that might fix this...let me know if you think they can be solutions
- index the shared folder in the remote workstations
- index the shared folder in the file server of the shared folder Windows 2008 R2
- publish the remote app of the shared folder in Terminal Service
- (Last choice) is copy the shared folder to the remote site since that the users in that location use it most.
Please let me know what you think which solution might be better.