Centralizing MS Applications across an IP WAN.

[EllaMonroe]

Our firm has recently centralized all of our Windows based applications to our headquarters in NY and ever since the responce time for opening, modifying, ect... is horrible, basically it is not workable. We were trying to centralize this type of traffic for the ease of use of backing up only one site, physical security via all our branches ect... The idea was good. Now, my next step is to recommend that the file servers come back, locally to each office. I do not want this.

It seems the IP WAN (Local Telco Private MPLS) we have between each site does not like CIFS traffic or something like that. We have looked at utilization stats of our traffic and we are nowhere near the limit so why the delay - (latency between HQ and worst branch office is 60ms - Best 8ms).

My question to the forum is, what can be done to optimize MS applications that must traverse an IP WAN. I would like to stay away from redeploying file servers at each site simply for this purpose. We are paying for a Private WAN across all our sites but cannot use it for something as simple as MS office tools centralized to our HQ. Across the current WAN we have video and voice and that is fine, mind you it has been optimzed and created to traverse a WAN as such,the Windows enviroment has not.

Please advise.. Thank you

 

[tf1]

I guess this is a large firm with several sites? The problem with what you are trying to achieve is that Office apps are not good over WANs and that you have to be very careful that all path locations are maintained when locations are changed. You can usually overcome necessary path changes for templates and documenta by using Redirect in Windows active directory pointing old templates and documents to the new location, but this can become complex.

In the long-term, I suggest that you look at Citrix as a soultion. The setup costs will seem high but the long-term benefits are also high. Advantages include low bandwidth requirements, you can set up identical desktops throughout the firm making way for easy hot-desking, mobile/home users can connect securely over low bandwidth connections and see the same desktop they see at work, plus when you replace the desktops, you can purchase/lease low cost terminals rather than PCs. It is also much easier to control security.


Regards: tf1

 

[fneily]

You state -"We were trying to centralize this type of traffic for the ease of use of backing up only one site, physical security via all our branches ect". I've personally heard this in government (Social Security Administration) and private business (ATT&T) and as a contractor. A bunch of stuff. The IT department is just too lazy to support multiple copies of Office. Look at how this "brilliant" suggestion has paid off. Whoever made this decision should be fired.
At Social Security, we switched to a citrix server (

http://www.citrix.com).

That's find for off hours with little traffic. Not for 10,000 people across the U.S.
You'll constantly have problems as long as you don't go back to local applications. There's no reason not to have local applications. Gee, people can still work if the network crashes. Duh.
Good luck.