We have a client with a document management system that has a plug-in to the Microsoft office applications. Historically all data was saved on a central File server over a VPN hosted in a data center. The file server was 2008 (with SBS2011) originally. We have migrated the infrastructure to the Azure cloud with the following configuration:
All files are now stored on the FP-02 server ( all servers are 2012 R2, default image), this server is running at 5-10% CPU and 25-30% memory and so does not seem under stress. Local to Azure Ping is in the region of 10ms for latency.
Users on the local client machines use the office application (word/excel/outlook) for the day to day work. When saving a document they select a Doc Management tab on the office application top ribbon, inside they have an option to "Save As" when selected a popup screen opens listing all the mapped drives for the computer and when selected provide a Tree view of the folder structure contained inside. When selecting one of the bigger drive locations (14Gb) the file structure takes between 10 and 15 seconds to load/populate (each time). When navigated the correct location the save function again takes between 10-15 seconds to complete. When navigating using explorer via mapped drives the speed is as expected and the folder structure opens/closes as if the files were local.
I have installed the Windows Search feature on the file server in an attempt to speed anything up in the background (Indexing), could there be changes between the historical 2008 and the new 2012 that the DMS application need to take into account OR are there any settings within the new 2012 file server that can be enable to improve the saving/navigation speeds. Any suggestions you can offer would be much appreciated.