Remote App - saving files locally are extremely slow
looking workarounds or if doing silly. piloting few remote locations , using office 2007 on ts farm via remote apps. apps launch fine , responsive. however, when want them save file locally, appears saves using \\tsclient\c\documents\etc. appears when save local file, being uploaded through ts server, down local computer large files on these locations limited bandwidth, taking long 10-15mb files save.
what options? , expected behavior remote app? thanks!
sounds going expected behavior.
what happens, client in remote office opens remoteapp, , opens document (assume document sitting on local machine in remote office). file in memory on terminal server , stays there until doc saved/closed. when saved, saving redirected drive (\\tsclient...), via virtual channels. means, file going terminal server client on wan (it not goign temrinal server first when saving, because there). if file large, gonna take while.
now. if remote offices connected main network (where terminal server is) nailed vpns, can try mapping drive in terminal server session shared drive on clients local computer, , saving file mapped drive. saving file using tcp. , might faster. wont work if instead going through ts gateway.
another option have users save files file server on same network terminal server.
hope helps,
kristin l. griffin
co-author of windows server 2008 terminal services resource kit (and super big fan of microsoft rdv team!!!)
Windows Server > Remote Desktop Services (Terminal Services)
Comments
Post a Comment