You know that an RTM is coming when the trickle of final documentation becomes a stream out of Microsoft. We had a few guides appear last week; 3 appeared overnight:
- Microsoft Multipath I/O (MPIO) Users Guide for Windows Server 2012: This document details changes in MPIO in Windows Server 2012, as well as providing configuration guidance via the GUI, or via our new MPIO module for Windows PowerShell, which is new for Windows Server 2012.
- Combined Active Directory Schema Classes and Attributes for Windows Server: his download contains the classes and attributes in the Active Directory schema for Windows Server. It contains the classes and attributes for both Active Directory Domain Services (AD DS) and Active Directory Lightweight Directory Services (AD LDS). There are individual text files in LDIF format, which are also bundled into an archive file for single download, if desired. Each file contains the classes or attributes, as appropriate, for the entire Active Directory schema, although system-generated (or instance-specific) properties have been removed to simplify machine parsing. The file names indicate the following: whether a file is for AD DS or AD LDS, whether it contains classes or attributes, and the version of Windows Server for which the file is intended.
- Application Compatibility and API Support for SMB 3.0, CSVFS, and ReFS: The Application Compatibility with Resilient File System document provides an introduction to Resilient File System (ReFS) and an overview of changes that are relevant to developers interested in ensuring application compatibility with ReFS. The File Directory Volume Support spreadsheet provides documentation for APIs support for SMB 3.0, CSVFS, and ReFS that fall into the following categories: file management functions, directory management functions, volume management functions, security functions, file and directory support codes, volume control code, and memory mapped files.
Won’t be long now
This blog post is the property of Aidan Finn (@joe_elway / http://www.aidanfinn.com) and may not be reused in any manner without prior consent of Aidan Finn. You may quote one paragraph from this blog post if you link to the original blog post.