Protocol Content Previews and Errata

Important updates for developers about the Windows and SQL Protocols Documents

08/24 – 20 Preview Documents Released for Windows Server Operating System

Preview versions of the 20 Windows Protocols documents listed below are now available at: [MS-ADTS]: Active Directory Technical Specification [MS-CMRP]: Failover Cluster: Management API (ClusAPI) Protocol [MS-CSVP]: Failover Cluster and Validation Protocol (ClusPrep) [MS-DHA]: Device Health Attestation Protocol [MS-DSCPM]: Desired State Configuration Pull Model Protocol [MS-FASP]: Firewall and Advanced Security Protocol [MS-LCID]: Windows Language Code… Read more

07/17 – Errata added for [MS-ADTS]: Active Directory Technical Specification

In various sections, added information about the msDS-ThreadStates rootDSE attribute, in support of [MSKB-4025334] Microsoft Corporation, “July 18, 2017 – KB4025334” (see… Read more

8/15 – Errata added for [MS-ADTS]: Active Directory Technical Specification

In two sections, added information that applies to the Active Directory implementation of VLV through Windows Server 2012 R2 without [MSKB-3106637] installed, or through Windows Server 2012 with [MSKB-3106637] installed:… Read more

2/8 – Errata added for [MS-ADTS]: Active Directory Technical Specification

Two changes in Section, DomainDescriptionElements, to correct the element names InterDomainTrustAccounts and InterDomainTrustAccountDescription  to InterdomainTrustAccounts and InterdomainTrustAccountDescription:… Read more

Protocols Errata Mega Post

Last week’s release (2016-01-25) was a larger-than-normal one, totaling 42 separate Errata items across 22 different Windows Protocols specifications. Here’s a handy listing of the specs impacted by that release, along with the number of new Errata in that doc MS-ADTS – 4 ErrataMS-CSRA – 1 ErrataMS-DNSP – 4 ErrataMS-DRSR – 2 ErrataMS-ECS – 1… Read more

1/11 – Errata added for [MS-ADTS]: Active Directory Technical Specification

In Section, Subnet Object, added that the subnet name for an IPv6 subnet must be in compact format so that no two strings can refer to the same subnet and clarified that ‘leading zeroes’ refers to the additional zeroes used to fill out the field and that subnet strings are case-insensitive:… Read more