This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
I have VSS service running on my Server 2003. I have workstations that are XP, Vist and Win7. VSS/shadow Copy seems to be functioning to some degree. The schedule runs fine (twice a day at 7:30 am and 12:00 pm.) If at my workstation (or anybody's) I can right click on a file and look at previous versions. What I get is a list of the file with all the same dates and times. It could be that I only have one previous version but it is the same as the current version on our server. Sometimes I have 5 or 6 "previous" version but they too have the same date and time as the current version. I am lost on what is causing it. Everything seems to be "functioning" for the fact it is doing it by the schedule and I have files being saved, they just are not the older versions. I tried saving each one listed thinking that it is an old version but it just is stating the date and time wrong int the dialog box. Nope, they are all the same as the current version. Any suggestion out there?
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
Answer accepted by question author
Hi jraesly,
Your Windows 7 question is more complex than what is typically answered in the Microsoft Answers forums. It is better suited for the IT Pro audience on Technet.
http://social.technet.microsoft.com/Forums/en/windowsbackup/threads
Hope this helps!
Halima S - Microsoft Support.
Visit our Microsoft Answers Feedback Forum and let us know what you think.
A more helpful answer would be to provide a link to an actual answer, rather than a link to another forum that does not contain an answer to the question.
This blog post provides a solution to this problem:
Although the article specifically mentions Small Business Server 2003, I applied the suggested fix to a Windows Server 2003 Standard Edition SP2 file server and it resolved the issue for Windows 7 systems in my environment.
