The Storage Team Blog about file services and storage features in Windows and Windows Server.
Below you have a list of KB articles for Windows Server 2008 released or updated this May.
The virtual IP address of a Windows Server 2008 NLB cluster is bound to the NetBIOS host name of a particular server or of multiple servers
The Cluster network name resource and the File Share Witness resource may not come online on a Windows Server 2008 failover cluster node if a disjointed namespace is configured
You cannot confirm or cancel the changes in the "Add Target" dialog box in LUN Management because the "OK" and "Cancel" buttons are missing on a computer that is running the Russian version of Windows Server 2008
The "Current Directory" label and the input text box are missing in the "Clusters" dialog box in some language versions of Windows Server 2008
A handle leak occurs in a Server Message Block (SMB) session between two Windows Vista-based computers or between two Windows Server 2008-based computers
Multipath I/O disks may disappear after you use the Hot Add Processor feature to add a new CPU to a Windows Server 2008-based computer
Support WebCast: Microsoft SQL Server 2005 Failover Clustering on Windows Server 2008
VSS warning events are logged for non-LUN identifiers in the inquiry VPD page 0x83 data in Windows Server 2008
Group Policy settings are not applied on member computers that are running Windows Server 2008 or Windows Vista SP1 when certain SMB signing policies are enabled
How to set up dynamic boot partition mirroring on GUID partition table (GPT) disks in Windows Server 2008
Error message when you use SMB-to-NFS gateway software that exposes mounted NFS shared folders as SMB shared folders on a Windows Server 2008-based computer: "Stop 0x0000007E"
Folder redirection does not work correctly after you restart a computer that is running Windows Server 2008 or Windows Vista
When you stop a node in a Windows Server 2008 failover cluster, the groups that are hosted on that node may fail over to a random node instead of to the next available node