Cannot access previous versions of files on Windows Storage Server 2003 (Volume Shadow Copy) x64 client
I am trying to access deleted network files with Shadow Copy from my Windows 7 x64 client. The files are located on a a Windows Storage Server 2003 with shadow copy enabled. However, when I click on the "Previous Versions" tab of the folder properties, I see a number of shadow copies with the current date and time. If I open one, it is just a copy of the current folder. I can access previous versions just fine from other client operating systems.Daryl Sensenig
February 4th, 2010 7:26pm

We have a similar case in the following thread. can't see previous versions on network drives in Windows 7 RC It seems that that issue was resolved with some system updates. Maybe we also need to wait for a period of time. I suggest you disable the firewall on both computers. If the issue still occurs, try to change the NTLM authentication level. Network security: LAN Manager authentication level The policy is: Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options\Network security: LAN Manager authentication level Please change “Send LM & NTLM - use NTLMv2 session security if negotiated”.Arthur Xie - MSFT
Free Windows Admin Tool Kit Click here and download it now
February 8th, 2010 10:50am

I don't think this is exactly the same issue. I have installed all the latest updates. Also, in my case, I can see previous versions, but they all show today's date and time. However, I would like to try changing the network security settings. Would I change it on the policy that applies to the server or the client or both? Daryl Sensenig
February 9th, 2010 12:14am

Hi, If you check the policy in Windows Server 2003 you will find that NTLM is the default level. It is different with Windows 7, in which NTLMv2 is the default level. Therefore you just need to change it in Windows 7.Arthur Xie - MSFT
Free Windows Admin Tool Kit Click here and download it now
February 9th, 2010 10:48am

I changed the setting in my local Group Policy. However, that still did not resolve the issue.Daryl Sensenig
March 8th, 2010 6:18pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics