Vista 32Bit & MS Office 2007 Slow File Save

Office environment: Brand new environment with Windows Server 2008 and 5 clients, of which one is XP with Office 2003 and four are Vista 32Bit with Office 2007. All clients are new Dell machines. MS Firewall is disabled for outbound and inbound. All virus and firewall applications are disabled or not yet installed. Network drive mapping has been rebuilt and verified. Share permissions verified. Tuning has been disabled. There are no disconnected network drives.

Problem: When running any MS office application on a Vista client, e.g. Excel, Word or Powerpoint, and then saving a file that has been altered, it takes 40 seconds for the save to occur. The save does occur and is definitely update on the network drive. When running Adobe, Notepad or any other non MS Office application, the save is immediate.

When running the MS Office applications from the XP client, saves to the network drive are immediate. No degradation whatsover.

File Save and File Save As from the MS Office applications take the same amount of time to save - approximately 45 seconds.

I have searched/scubbed numerous forums and have tried everything that I have been able to uncover in terms of recommendations, yet have the same results. The oddity is that the XP Client does not have any problem whatsover in terms of File Save or File Save As degradation.

I suspect the problem may be associated with the combination of Vista and MS Office 2007 on a client and some obscure option that is causing this.

I am open to any and all ideas/recommendations/suggestions to resolve the problem. Thanks in advance for you help and please offer any ideas.

You didn't say this, but saving on VPN takes a while. Anyhow... you may want to check out this link.

Vista Slow Issues

Also make sure you have SP2 installed on Vista and SP2 for Office 2007.

SP2 installed for both Server and Vista boxes. There is not a VPN in play. Why would XP work without degradation when saving an MS Office application file in the same network environment?

kevdardy said:

SP2 installed for both Server and Vista boxes. There is not a VPN in play. Why would XP work without degradation when saving an MS Office application file in the same network environment?

Click to expand...

You said SP2 was installed for server and vista pcs. Did you state SP2 was installed for Office 2007?

Yes, SP2 is on the Office 2007.

Is it only slow to save MS Office files? What if you save a file in Wordpad? What if you save a MS Word file as txt? Are files also slow to open? Also, have you checked for fragged drive?

Saved .pdf via Adobe without problem. Used Paint, created file and saved without a problem. File Open is quick. I haven't tried Wordpad. I haven't tried to save a MS Word file as a .txt file. Drive wouldn't be fragmented since it is a new install. Will try Wordpad and saving a MS Word file as a .txt file. Thanks helping and your responsiveness. I will get back after I try those two things.

Lemur! Tried Wordpad and save was immediate. Tried MS Word, created a new document and saved as .txt. Took 45 seconds. I really believe it is tied to MS Office applications exclusively. Any more ideas?

Others question from previous post. Does it take a long time to open files?

File open is immediate. No degradation on file open. Only degradation in file save and file save as when using Excel, Powerpoint or Word MS Office 2007 applications. Can copy a file from the Vista box to the mapped network drive and is immediate.

The last suggest would have been to save as .doc instead of .docx, but you already indicated .txt took 45 seconds.

WHAT ABOUT... if you disable your virus scanner. Actually, you do have just ONE scanner, right? Just as a test. In fact, what if you rebooted your computer into safe mode and timed the save of a document in Word vs. Wordpad? Okay, that's a couple of experiments for you. Report back...

Are you saving to a mapped network drive???

This may be a possible solution - Vista 32Bit & MS Office 2007 Slow File Save

Hi kendardy

I have a very similar setup and the exact same problem. I finely had to use one of my 4 MSDN incidents to get a solution. After over 4 hours on the phone with a Microsoft tech and countless test and reboots it was fixed by disabling SMB2 on the server.

Add a REG_DWORD entry named Smb2 with a value of 0 to
HKLM\System\CurrentControlSet\Services\LanmanServer\Parameters

Then reboot the server.

http://blogs.technet.com/askperf/archive/2008/05/30/two-minute-drill-overview-of-smb-2-0.aspx

Presto-Chango it worked. There is evidently some kind of issue with SMB2 and Office.

I know I am using Windows 7 x64 clients but I was told that the issue may well exist with vista.

Hope this helps.
Jim