Configure Shadow Copy on desktops via group policy or script.
I would like to enable shadow copy on desktops. I have found a command which will allow me to modify the amount of space which is used, but haven't been able to create a restore point or shadow copy from command line or group policy.
ASKER
We have a multiple clients who we take care of with servers that range from SBS 2008, SBS 2011, Essentials 2011, and Standard Server OS's as well. Also Windows 7 through Windows 10.
I have thought about deploying through group policy and running a script so there are previous versions of the desktop files each morning.
I know of redirected folders, but most of the servers don't have the space needed to carry all of the users files.
I have thought about deploying through group policy and running a script so there are previous versions of the desktop files each morning.
I know of redirected folders, but most of the servers don't have the space needed to carry all of the users files.
There is not a One Size Fits All solution for you if you have clients running all those different type of Servers. Also, "Previous Versions" in Windows 7+ is not the same as Volume Shadow Copy on a Server.
While the technology to create these snapshots is similar, the snapshots on the Workstation are done only at the time of a "Restore Point" for the entire C: drive. (Usually this is done automatically when any app is updated). You may only be able to fit a few (3 or 4) previous versions on a workstation's hard drive, while on a server you would generally have about 30 or 40.
If you want to enable System Restore via GPO, you'll find the setting in:
Computer Configuration > Policies > Administrative Templates > System > System Restore
But as I stated, these will not provide the same type of protection as VSS does on a server.
In Windows 8.1 or Windows 10 also have a service called "File History" which is similar to Apple's Time Machine. This service is designed to be used with an external USB drive... they should not be stored on the workstations main drive as you could potentially fill up the entire drive and crash the system.
Server 2012 Essentials has the ability to capture File History from these machines and back it up centrally, but other server versions cannot do this.
To be honest, the thing that stands out the most from your comments is that the servers don't have the space needed to do this correctly by centralizing all of your backup and protection efforts. Instead you are now trying to manage a decentralized solution with many, many more points of failure -- which in the end will cost significantly more than if the servers were properly sized.
When clients never have enough money to set things up properly to begin with, yet they seem to have plenty of money to develop band-aid solutions afterwards, it usually means they weren't educated well enough at the time the solution was deployed. Now you have a choice of helping them make more bad decisions or hopefully steering them towards a better one.
Jeff
TechSoEasy
While the technology to create these snapshots is similar, the snapshots on the Workstation are done only at the time of a "Restore Point" for the entire C: drive. (Usually this is done automatically when any app is updated). You may only be able to fit a few (3 or 4) previous versions on a workstation's hard drive, while on a server you would generally have about 30 or 40.
If you want to enable System Restore via GPO, you'll find the setting in:
Computer Configuration > Policies > Administrative Templates > System > System Restore
But as I stated, these will not provide the same type of protection as VSS does on a server.
In Windows 8.1 or Windows 10 also have a service called "File History" which is similar to Apple's Time Machine. This service is designed to be used with an external USB drive... they should not be stored on the workstations main drive as you could potentially fill up the entire drive and crash the system.
Server 2012 Essentials has the ability to capture File History from these machines and back it up centrally, but other server versions cannot do this.
To be honest, the thing that stands out the most from your comments is that the servers don't have the space needed to do this correctly by centralizing all of your backup and protection efforts. Instead you are now trying to manage a decentralized solution with many, many more points of failure -- which in the end will cost significantly more than if the servers were properly sized.
When clients never have enough money to set things up properly to begin with, yet they seem to have plenty of money to develop band-aid solutions afterwards, it usually means they weren't educated well enough at the time the solution was deployed. Now you have a choice of helping them make more bad decisions or hopefully steering them towards a better one.
Jeff
TechSoEasy
ASKER
I understand that the desktops run copies differently. We have educated the users that they need to save to the server and not their local computer, but users still save to their PC's and some save personal pictures and and other items on them. I was looking for a CYA solution we could implement for these users. Running a system restore point would be great. Is there a location on the server where I could schedule a restore point to be created via group policy say once a week instead of when a change occurs on the PC?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Also, keep in mind, VSS does not protect against disk failure!
ASKER
We were looking into this as an option to circumvent the viruses such as cryptowall.
Also, the way that "shadow copies" works in Windows 7 is vastly different than in Windows 8.1+ (which includes Windows 10).
So it may help if you outline your overall goal instead and maybe we can help you achieve it in the most efficient way?
Jeff
TechSoEasy