This article lists the hotfixes that are currently available for users who have installed the File Services technologies on a Windows Server 2012-based computer or a Windows Server 2012 R2-based computer. File Services provides technologies that help you manage storage, enable file replication, manage shared folders, provide fast file searching, and enable access for UNIX client computers. This article also lists the hotfixes that are currently available for users who use File Services on Windows 8-based computers or Windows 8.1-based computers.
This article contains lists of Microsoft Knowledge Base articles that describe the currently available fixes. The article is divided into two sections. The first section applies to Windows Server 2012 and to Windows 8, and the second section applies to Windows Server 2012 R2 and to Windows 8.1. Each section is divided into subsections for different component drivers: SRV, MRXSMB, and RDBSS. In general, the SRV drivers should be updated on the server or client computer that is hosting the data. The MRXSMB and RDBSS drivers should be updated on the server or client computer that is initiating access to the data. If you are unsure about which component should be updated on which computer, you can update all three component drivers on both the computer that is hosting the data and the computer that is accessing the data.
"Invalid device" error when you try to rename a file on a Network File System client that is running Windows 8, Windows 8.1, Windows Server 2012, or Windows Server 2012 R2
This hotfix contains the most current version of Nfsclnt.exe,Nfsrdr.sys and Nfsnp.dll.
To apply this hotfix, you must be running Windows 8.1 or Windows Server 2012 R2 and April 2014 Update 2919355. Available for individual download.
The Server Message Block (SMB) model consists of two entities: the client and the server.
On the client, applications perform system calls by requesting operations on remote files. These requests are handled by the redirector subsystem (rdbss.sys) and by the SMB mini-redirector (mrxsmb.sys), both of which translate the requests into SMB protocol sessions and requests over TCP/IP. Starting with Windows Vista, the SMB 2.0 protocol is supported. The mrxsmb10.sys driver handles legacy SMB traffic, and the mrxsmb20.sys driver handles SMB 2.0 and SMB 3.0 traffic.
On the server, SMB connections are accepted, and SMB requests are processed as local file system operations through NTFS and the local storage stack. The srv.sys driver handles legacy SMB traffic, and the srv2.sys driver handles SMB 2.0 traffic. The srvnet.sys component implements the interface between networking and the file server for both SMB protocols. File system metadata and content can be cached in memory via the system cache in the kernel (ntoskrnl.exe).
Figure 1 provides an overview of the different layers through which a user request on a client computer must go to perform file operations over the network on a remote SMB file server by using SMB 2.0.
Figure 1. Windows SMB components
Services for Network File System (NFS) in a Windows Server 2012 environment
Services for NFS includes the following components:
Server for NFS
This component corresponds to the server-side implementation of the NFS file-sharing protocol. Server for NFS enables a computer that is running Windows Server 2012 or Windows Server 2012 R2 to act as a file server for UNIX-based client computers.
Client for NFS
This component corresponds to the client-side implementation of the NFS file-sharing protocol. Client for NFS enables a Windows-based computer that is running Windows Server 2012 (or Windows 8) to access files that are stored on a UNIX-based NFS server.
Windows Server 2012 includes both the Server for NFS and Client for NFS components. However, Windows 8 includes only Client for NFS.
For more information and a step-by-step guide for the services for NFS, go to the following Microsoft website:
Microsoft Services for NFS provides a file-sharing solution for enterprises that have a mixed Windows and UNIX environment. This communication model consists of client computers and a server. Applications on the client request files that are located on the server through the redirector (Rdbss.sys) and NFS mini-redirector (Nfsrdr.sys). The mini-redirector uses the NFS protocol to send its request through TCP/IP. The server receives multiple requests from the clients through TCP/IP and routes the requests to the local file system (Ntfs.sys), which accesses the storage stack.
Figure 2 shows the communication model for NFS.
Figure 2. NFS Communications
For more information about currently available hotfixes for the File Services technologies in Windows Server 2008 and Windows Server 2008 R2, click the following article number to go to the article in the Microsoft Knowledge Base:
2473205 List of currently available hotfixes for the File Services technologies in Windows Server 2008 and in Windows Server 2008 R2
For more information about performance tuning, see the "Tuning parameters for SMB file servers" section of the following MSDN article:
Windows Server 2012 Datacenter, Windows Server 2012 Essentials, Windows Server 2012 Foundation, Windows Server 2012 R2 Datacenter, Windows Server 2012 R2 Essentials, Windows Server 2012 R2 Foundation, Windows Server 2012 R2 Standard, Windows Server 2012 Standard, Windows 8 Enterprise, Windows 8 Pro, Windows 8.1 Enterprise, Windows 8.1 Pro