My company redirects My Documents to a server. For some reason on Windows 7 when I try to save an Office Document to My Documents it takes 50 seconds to save at times. When we used Windows XP we didn't have this problem. It doesn't happen every time, but it is fairly often. I'm not 100% sure that it just pertains to Office documents. I haven't noticed any other problems copying files to My Documents (which seems like it would essentially be a save operation). I'll keep trying different things to get more information. Any thoughts? Thanks.

Does it take 50 seconds to save counting from when you click the Save button? When you experience the problem also try this to narrow the problem down: 1. Save to the local hard drive, does this take a long time as well?2. Save to the same server as you have your documents file, but to a location that you do not have as offline files. Does this work better?3. Disconnect from the network (or choose Work offline in Windows Explorer) and try to save the same Office document to the same location, does this work better?Blogging about Windows for IT pros at www.theexperienceblog.com

For what its worth, I have exactly the same problem. We are using SBS 2003.

For what its worth, I have exactly the same problem. We are using SBS 2003. Interesting, could you also try steps 1-3 in the list above and see what the output is? Thanks!Blogging about Windows for IT pros at www.theexperienceblog.com

Our redirected folders are hosted on Windows Server 2003 R2. I can answer a few of the questions now and I'll try to get the rest answered on Tuesday when I go back to work. "Does it take 50 seconds to save counting from when you click the Save button?" correct "Save to the local hard drive, does this take a long time as well?" No. The part that makes it especially annoying to troubleshoot is that it's an intermittant problem. I've tried looking through event logs on the client (win7), but so far I'm not seeing anything. I've looked briefly at the logs on the server (2k3 R2) and don't see anything there either yet.

1. Saving to local drive is always quick. 2. Saving to a folder that is not marked as always offline does seem to be quicker. 3. I seem to be missing an option in Windows Explorer to work offline. I'm sure there used to be such an option in previous versions of Windows.

Hi, We have seen similar issues in this forum. You may refer the following thread to troubleshoot. Windows Search and Offline Files If there is any update for this issue, please post here.Arthur Xie - MSFT

Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options\Network security: LAN Manager authentication level Please change to “Send LM & NTLM - use NTLMv2 session security if negotiated”. I just made this setting in a GPO and applied it to the Windows 7 client. It did not help. Does anything need to be applied to the server?

You may try this: 1. Click Start, click Run, type Regedit in the Open box, and then click OK.2. Locate and click the following registry key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MrxSmb\Parameters 3. Click Edit, click New, and then click DWORD value.4. Type InfoCacheLevel to replace New Value #1, and then press ENTER.5. Click the InfoCacheLevel DWORD value in the right pane, click Edit, and then click Modify.6. Under Value data, select hexadecimal and type 10, and then click OK.7. Quit Registry Editor.Arthur Xie - MSFT

The Paramaters key is missing in my registry under mrxsmb, should I create it? I'm trying it anyway, will post if it makes a difference.

I've just encountered the problem again, so no fix yet.

Yeah I've been on vacation in Vegas for the past week so I haven't been able to work on this issue more. I'll try to get back on it this week when I get back. It is still a problem, but I haven't yet tried the last registry tweak that Arthur posted.

Also look in the Event Viewer under Applications and services logs - Microsoft - Windows - Offline files - Operational for any events related to the time when you experience the problems.Blogging about Windows for IT pros at www.theexperienceblog.com

Will try this when back at work again.

I'm having the exact same issue at work. Has any progress been made?

No...it's still broken. I've been too busy to work on it. You might try the last suggestion by Arthur...I don't believe I got around to trying it. Please post back if you find anything out.

Still no word on this? I am having this issue at a couple of my offices. Windows 7 client and server is a Windows 2003 R2 SP2 file server.

Still an issue for us as well. We have the same setup (Windows 7 clients and Windows 2003 R2 file server).

So how do we go about letting Microsoft know how big of a problem this is for customers that use redirected folders? I'd like to move forward with my Windows 7 deployment, but I really thought this would be fixed by now. As I deploy more users this is becoming an increasingly bigger problem.

Start a support case with Microsoft is one option that will get you far, and lead to a solution if it is a bug. You could also try to work around it, i.e. install a test machine with Windows Server 2008 R2 and see if the problems remain, in cases like this it is important to narrow down where the bug actually is, i.e. client OS, server OS, network, offline files cache etc.Blogging about Windows for IT pros at www.theexperienceblog.com

Has anyone had this problem in programs other than Office programs?

Run ProcessMonitor in background and look if you can see what takes so long."A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/

I'm troubleshooting this with Microsoft support. Can anyone verify whether this happens when the redirected folder is located on Server 2008 or 2008 R2? Thanks.

hi, please check this KB http://support.microsoft.com/kb/981872 . Did any of you also facing the same scenario described in the KB?

I have the same issue with VISTA/Office 2007 or Windows 7/Office 2010 saving to a 2008 Server.

Sorry I thought I followed up on this, but I just saw I never did. This problem was in fact fixed by applying this hotfix http://support.microsoft.com/kb/981872 The hotfix is included in Windows 7 SP1