2
I manage several computers running Windows 7 with Microsoft Office 2010 and Microsoft Office 2013. Our users store and access many of the Microsoft Office files on a network share. For a typical file around 100KB:
- Copying the file from the network drive to a local drive: < 1s.
- Opening the file with Notepad: < 1s.
- Opening the file with LibreOffice < 1s.
- Copying the file to a local drive and then opening it locally: < 1s.
- Opening the file with Microsoft Office (e.g. Word for .docx): < 20s.
In the last case, the dialog shows "Downloading ... (0%)" and hangs there until the file finally opens. Obviously, from results 1-3, this is not reflective of the network drive performance.
I have followed instructions from here, adjusting the Office version number as needed. This seems to describe the problem well, but the fix doesn't work.
I have also tried various one-off registry edits to disable validation. They also do not work, but I'm open to any suggestions.
The network shares are shared by Samba 3. Some of the client machines are running antivirus and some aren't running any at all, so that can't be the issue.
Can anybody offer any thoughts? I don't care about security scanning the files, checking whether they're valid, or any other such operations. I just need Microsoft Office programs to open the files in a reasonable time, so even the most heavy-handed working solution will be fine.
If you copy the document to the local hard drive, does it open faster? – Atzmon – 2016-06-05T06:01:01.317
have you tried disabling Anti virus? Are the users using roaming profiles, and/or do they have their My Documents folder redirected to a server? – Ƭᴇcʜιᴇ007 – 2016-06-05T06:01:24.593
@Atzmon I added a new point 4 above addressing this. – rg6 – 2016-06-06T13:24:55.390
@TECHIE007 Some have antivirus, but some have no antivirus running at all. They all experience the issue in the same way. The users have roaming profiles managed by an AD server over which I have no control. All their profile folders are local. This share is mapped as an additional drive within a separate department, but their credentials to access the drive rely on their Kerberos (AD) TGT. – rg6 – 2016-06-06T13:27:16.500