A blog by Jose Barreto, a member of the File Server team at Microsoft.
All messages posted to this blog are provided "AS IS" with no warranties, and confer no rights.
Information on unreleased products are subject to change without notice.
Dates related to unreleased products are estimates and are subject to change without notice.
The content of this site are personal opinions and might not represent the Microsoft Corporation view.
The information contained in this blog represents my view on the issues discussed as of the date of publication.
You should not consider older, out-of-date posts to reflect my current thoughts and opinions.
© Copyright 2004-2012 by Jose Barreto. All rights reserved.
Follow @josebarreto on Twitter for updates on new blog posts.
The File Server team often talks to customers about file server migration and file server consolidation projects. Many times, these are customers running Windows Server 2003 that can point to a number of issues they wanted fixed. In most cases, those issues have been identified and corrected in Windows Server 2008 and Windows Server 2008 R2. Here are 8 of these issues (just to name a few) from recent conversations with customers:
1. CHKDSK Time
Windows Server 2003 problem:
Windows Server 2008 R2 facts:
A recent white paper published by the Storage and File System team at Microsoft (which owns NTFS) mentioned a couple of interesting data points:
2. File Server Scalability
3. Failover Cluster Setup
4. Shares Per File Server
5. Encrypted Files
6. Large File Transfers on High Latency Networks
7. Transferring Lots of Small Files
8. Caching in the Branch
If you have a Windows Server 2003 File Server still around, I cannot stress enough how much you’re missing. The Windows Server team has worked hard in the last 8 years to fix these and many other issues (including the work in the recently released Service Pack 1). I hope the 8 items listed here can entice you to consider an upgrade to Windows Server 2008 R2 or Windows Storage Server 2008 R2.
If you compare Windows Server to NAS appliances running other operating systems, make sure you use Windows Server 2008 R2 (or Windows Storage Server 2008 R2) in a similar configuration (similar number of disk spindles, similar types of disks, similar RAID configuration, similar networking speeds, etc.). You want to make sure you have the latest Windows on both sides, so they can negotiate up to SMB 2.1 and you can get the full benefits mentioned. You’ll find that Windows Server 2008 R2 with SMB 2.1 can deliver industry-leading file server capabilities and performance.
Get started right now by downloading an evaluation version of Windows Server 2008 R2 with Service Pack 1 from http://technet.microsoft.com/en-us/evalcenter/dd459137.aspx
A new blog post covers a set of Windows Server 2003 File Server problems that were fixed in Windows Server
Hi folks, Ned here again. Despite the reputation for cutting edge technology, a lot of IT departments
This is a great article. I will show this to all my customers who are still on 2003. I did some testing with SMB 2.1 and love the performance improvements.