Dell recommends Windows 8.

Windows 8 File History Pros & Cons

Brien Posey, Freelance Writer and Former CIO | 7/11/2013 | 25 comments

Brien Posey
The Windows 8 File History feature is designed to effortlessly protect end-user data by silently making backups of user files and providing file-versioning capabilities. It's no big secret that Microsoft designed File History as a consumer feature, but is File History suitable for business environments?

The short answer to the question is yes, with some caveats. File History doesn't contain any built-in restrictions that prevent an enterprise from enabling and using it. Of course, just because you can do something doesn't necessarily mean that you should. File History is a feature that is targeted at consumers, not enterprises. As such, there are a number of reasons why it might not be practical for use in corporate environments.

One of the big reasons why an enterprise organization might not benefit from using the File History feature has to do with the types of data that File History is designed to back up. Microsoft did not design File History to be a comprehensive backup solution. During the development of Windows 8, Microsoft realized that only about 5 percent of Windows 7 customers had the native backup application enabled.

Because of this, Microsoft set out to create a more targeted backup solution that required a lot less effort on the part of the end user. The problem with this approach is that File History does not back up the entire PC, or even an entire drive. Instead, File History only backs up user libraries, the desktop, favorites, and contacts. File History cannot be configured to back up applications or other folders that might contain data.

This is a problem in corporate environments because organizations with domain networks almost always use profile folder redirection to redirect user libraries to a network share. However, File History will not protect redirected libraries. Similarly, Windows offers the ability to add additional folders to the default library collection. Network folders that are added to the libraries cannot be protected by File History. These two limitations mean that File History can only protect user data that is stored locally on the desktop and in a protected folder.

Another reason File History might not be suitable for use on corporate networks has to do with the fact that File History could potentially undermine some of the organization's data storage requirements. Most larger organizations have data retention requirements that form the basis of their data lifecycle management policies. Document versions stored within File History could potentially exceed the retention threshold.

Even if the idea of storing user data for an excessive amount of time is not an issue for an organization, the security of that data probably is. File History is designed to protect data against loss, not to protected against unauthorized access. That being the case, it should come as no surprise that there is very little security surrounding the backup copy of user data.

File History works by designating an external hard drive as a dedicated storage repository for backing up protected data (data can also be written to the network). If removable storage is used for File History backups, then there is always the risk of sensitive data walking out the door as a result of someone stealing the external drive. Even if the drive itself is not stolen, File History can potentially be problematic in environments where multiple users share a common PC. There have been unconfirmed reports of one user being able to access backups of another user's data on shared PCs.

Although the File History feature does have its place, enterprise environments are probably better off using a different file-versioning and data-protection solution. For example, SharePoint offers file-versioning capabilities, and there are several backup applications that give users the ability to restore (or revert to a previous version of) file data.

If you do decide that the File History feature is not appropriate for use in your organization, then you should consider using Group Policy settings to disable it. To do so, open the Group Policy Editor and navigate to Computer Configuration | Administrative Templates | Windows Components | File History. You can use the Turn Off File History setting to prevent users from using the File History feature.

Related posts:

View Comments: Newest First | Oldest First | Threaded View
Page 1 / 3   >   >>
Tuscany   Windows 8 File History Pros & Cons   9/30/2013 1:09:02 AM
Re: Boundary between consumer & enterprise

@Susan   I think your understanding is correct.  Automation always triumphs  end-user involvement especially in the area of backups.

Tuscany   Windows 8 File History Pros & Cons   9/30/2013 1:05:48 AM
Re: Boundary between consumer & enterprise

" It not a good idea to see a feature work in consumer world and say, "wow, that worked nice for them(consumers). So, lets deploy that to our enterprise environment."


@Zaius     I agree.  This used to be pretty clear and then Apple began to enter the workplace.  It has caused manufacturers to rethink the influence of the consumer market.   Sure, the consumer market has influence, but it should not override the concerns of a OEM to provide a constant enterprise offering.

Marif   Windows 8 File History Pros & Cons   7/25/2013 1:36:05 PM
Re: Boundary between consumer & enterprise
@SaneIt: from a home user perspective, I don't want to have more than a couple restore points on my machine. And a few time when I needed them to work, they worked properly. But for an enterprise, you are right these backups cannot afford to be deleted just to get some space. This is against the rule why the backup was taken at the first place.
sohaibmasood   Windows 8 File History Pros & Cons   7/23/2013 12:58:12 PM
Re: Boundary between consumer & enterprise
Marif, you are correct. Manual work must be done in cases where the software doesn't support automated backup. Compliance issues might occur if periodic backups are not maintained. 
sohaibmasood   Windows 8 File History Pros & Cons   7/23/2013 12:55:45 PM
Re: Boundary between consumer & enterprise
Deleting restore points is a nuisance and as tech guys we all have seen it happen over the years. I agree with you that ideally those backups should have been moved earlier before the point where the system barely works. Somethings with end users never change and I believe this is one of them. Nobody realizes the importance of backup until they fall into a trap. 
RPatrick   Windows 8 File History Pros & Cons   7/22/2013 7:14:22 AM
Pros and Cons
"This is a problem in corporate environments because organizations with domain networks almost always use profile folder redirection to redirect user libraries to a network share."

SaneIT   Windows 8 File History Pros & Cons   7/22/2013 7:10:52 AM
Re: Boundary between consumer & enterprise
When someone fills their OS drive with backup files to the point that it just barely boots those files don't typically get the benefit of being backed up when a user is looking for things to clear out.    Ideally, yes they would be backed up first but I've been through this hundreds of times with users deleting restore points to get back up and running then calling me to find out what they deleted.
Marif   Windows 8 File History Pros & Cons   7/21/2013 2:12:22 PM
Re: Boundary between consumer & enterprise
@shoaibmasood:Yes backup is the need of the day today that is why most of the new systems and databases already have the capability of maintaining logs. Only such systems needs to be considers for compliance which are not running on these high end serves and databases. 
anthony.nima   Windows 8 File History Pros & Cons   7/19/2013 11:49:04 PM
Re: Boundary between consumer & enterprise
@Susan: Yes make sure other parties will not have anything to do with it since IT is solely responsible for it. Involvement of other parties will be risky.         
Susan Fogarty   Windows 8 File History Pros & Cons   7/19/2013 10:04:31 AM
Re: Boundary between consumer & enterprise
Marif, thanks for the reality check. If compliance is the whole reason for the backup in the first place, you definitely want to make as easy for IT and take it out of the users' hands.
Page 1 / 3   >   >>

The blogs and comments posted on do not reflect the views of TechWeb,, or its sponsors., TechWeb, and its sponsors do not assume responsibility for any comments, claims, or opinions made by authors and bloggers. They are no substitute for your own research and should not be relied upon for trading or any other purpose.

More Blogs from Brien Posey
Brien Posey   9/5/2013   10 comments
One of the main benefits of virtual desktop infrastructure is the ability to run many virtual machines on a single host, making the most efficient possible use of the resources available. ...
Brien Posey   8/28/2013   57 comments
By now you know that Windows 8.1 will release to the public on October 18. You may not know that with Windows 8.1, Microsoft is releasing a brand new version of Internet Explorer, IE 11.
Brien Posey   8/22/2013   22 comments
Operating system upgrades have always been something of a crapshoot. We as administrators make every effort to follow all of the recommended best practices, but it is difficult to know ...
Brien Posey   8/15/2013   20 comments
Significant changes are coming to Microsoft TechNet. If your organization uses TechNet software for planning or testing, you may need to modify your approach.
Brien Posey   8/6/2013   10 comments
The tool of choice for Microsoft operating system deployments is System Center Configuration Manager (SCCM). For those who have never worked through a bare metal Windows 8 deployment, it ...
Dell Information Resources
On-demand Video with Chat
The culture of work is changing. Tech-savvy and always-connected people want faster, more intuitive technology, uninterrupted services, and freedom to work anywhere, anytime, on a variety of devices.
Latest Archived Broadcast
Bring-Your-Own-Device (BYOD) is about more than just a device.
© 2019 UBM TechWeb - Privacy Policy