Provides an overview of the functionality and
relationship of the protocols that make up the client-server and
server-to-server behavior of Active Directory. The Active Directory protocols
provide directory services for the centralized storage of identity and
account information, as well as storage for other forms of data such as group
policies and printer location information, a foundation for authentication
services in a domain environment, domain services, and directory replication
services in Windows. The Active Directory protocols are specified in [LDAP],
[MS-ADTS], [MS-SRPL], [MS-DRSR], [MS-SNTP], [MS-LSAD], [MS-LSAT], [MS-DSSP],
[MS-SAMR], [MS-SAMS], [MS-WSDS], [WFXR], [WSENUM], [MS-WSTIM], [MS-ADDM],
[MS-WSPELD], and [MS-ADCAP].

Provides an overview of the functionality and
relationship of the protocols implementing Certificate Services, which includes
the certificate enrollment protocols specified in [MS-WCCE], [MS-ICPR], and
[MS-WSTEP], the certificate enrollment policy protocols specified in
[MS-XCEP] and [MS-CRTD], and the certificate remote administration protocol
specified in [MS-CSRA]. Certificate Services protocols are used for
certificate enrollment, certificate policy, and remote administration of
certificate services. The Certificate Services protocols (except the server
role of [MS-XCEP]) operate in two modes: Standalone and Enterprise.

Provides an overview of the functionality and
relationship of the File Access Services (FAS) protocols, which enable
network file access and sharing in Windows and allow a client computer to
discover, access, and share files that are hosted on, and made available by,
another computer. The FAS protocols are specified in [MS-BRWS], [MS-CIFS],
[MS-DFSC], [MS-FSA], [MS-FSCC], [MS-RAP], [RFC1094], [RFC1813], [RFC4918],
[RFC5661], [MS-SMB], [MS-SMB2], [MS-SMBD], [MS-WDV], [MS-WDVME], and
[MS-WDVSE].

Provides an overview of the .NET Framework protocols
that map to the .NET Framework distributed technologies that enable network
communications. This includes the protocols implemented in the Windows
Workflow Foundation (WF), Windows Communication Foundation (WCF), identity
and directory services, data access, ASP.NET, and .NET Remoting technologies
of the .NET Framework.

Provides an overview of the functionality and
relationship of the protocols implemented in the Remote Desktop services in
Windows, which includes the protocols specified in [MS-RDPBCGR], [MS-TSGU],
[MS-TSTS], [MS-TSWP], [MS-RDPEDC], [MS-RDPEGDI], [MS-RDPCR2], [MS-RDPNSC],
[MS-RDPRFX], [ MS-RDPEPS], [MS-RDPELE], [MS-RDPECLIP], [MS-RDPEDYC],
[MS-RDPEFS], [MS-RDPESP], [MS-RDPEPC], [MS-RDPESC], [MS-RDPEA], [MS-RDPEAI],
[MS-RDPEMC], [MS-RDPEPNP], [MS-RDPEUSB], [MS-RDPERP], [MS-RDPEV],
[MS-RDPEXPS], [MS-RDPERP], [MS-RDPEUDP],[MS-RDPEGFX], [MS-RDPEMT],
[MS-RDPEECO], [MS-RDPEVOR], [MS-RDPEI], and [MS-RDPEAR]. Using the Remote
Desktop protocols, a user of a remote client can initiate a user session on a
server and then run programs, save files, and use network resources. This
supports the hosting of multiple simultaneous user sessions on servers.
Remote Desktop protocols support scenarios such as redirecting keyboard,
mouse, clipboard, media player content, print jobs, smart card data, and file
system data between the RDP client and the server.

May 2019

The documents below were updated in March 2019 for Windows
Server 2019/Windows 10 and/or to reflect content updates.

Specifies the Failover Cluster: Management API
(ClusAPI) Protocol, an RPC-based protocol that is used for remotely managing
a cluster.

This document has been updated for Windows 10 and
Windows Server 2019 as follows:

● In three sections,
updated the tables listing values for the dwFlags field to include five new
values and their meanings. Additionally, in the section describing
ApiGetClusterVersion2 (Opnum 102) for Protocol Version 3, clarified the
descriptions for lpwMajorVersion and lpwMinorVersion, and updated the tables
listed in the associated behavior notes to reflect values for the most recent
product versions.

Specifies the Failover Cluster: Setup and Validation
Protocol (ClusPrep), which remotely configures cluster nodes, cleans up
cluster nodes, and validates that hardware and software settings are
compatible with Failover Clustering.

This document has been updated for Windows 10 and
Windows Server 2019 as follows:

● In the details for
IClusterSetup Server: Added a section for a new method, GetUpgradeVersion
(Opnum 12). Also clarified the description of the GetFunctionalLevel (Opnum
6).

● In the details for
IClusterStorage2 Server: In the description for CprepPrepareNodePhase2 (Opnum
6), changed name of AttachDisksOnSystemBus to Flags and added table listing
possible values and their meanings.

Specifies the Domain Name Service (DNS) Server
Management Protocol, which defines the RPC interfaces that provide methods
for remotely accessing and administering a DNS server. It is a client and
server protocol based on RPC that is used in the configuration, management,
and monitoring of a DNS server.

This document has been updated for Windows 10 and
Windows Server 2019 as follows:

● Added one new
constant, DnsPolicyCriteriaEDNSSubnet, and included it in the
DNS_RPC_CRITERIA_ENUM enumeration.

This document has been updated for Windows 10 and
Windows Server 2019 as follows:

● In Section 1.7,
Versioning and Capability Negotiation, added the 0x021E policy version to the
section content and to the Policy Version table of behavior note 1, with
applicability to Windows Server v1903 and Windows 10 v1903 operating systems.

● In Section 2.2.14,
FW_PORT_KEYWORD, updated port keyword names 'FW_PORT_KEYWORD_MAX_V2_25' and
'FW_PORT_KEYWORD_MAX_V2_28' in the enum _tag_FW_PORT_KEYWORD type definition
to 'FW_PORT_KEYWORD_MAX_V2_24' and 'FW_PORT_KEYWORD_MAX_V2_25', respectively;
also updated the same in the descriptions list and in behavior note 3.

● In Section 2.2.21,
FW_ADDRESS_KEYWORD:

-- Added the following new
address keywords and values to the enum _tag_FW_ADDRESS_KEYWORD type
definition and corresponding descriptions to the descriptions list:

FW_ADDRESS_KEYWORD_CAPTIVE_PORTAL = 0x0200

FW_ADDRESS_KEYWORD_MAX_V2_29 = 0x0200

-- Updated the value of
FW_ADDRESS_KEYWORD_MAX = 0x0200 to FW_ADDRESS_KEYWORD_MAX = 0x0400 in the
enum _tag_FW_ADDRESS_KEYWORD type definition and in the description list.

Specifies The Group Policy: Firewall and Advanced
Security data structure extension, which provides a mechanism for an
administrator to control the Firewall and Advanced Security behavior of the
client through group policy by using the Group Policy: Registry Extension
Encoding protocol [MS-GPREG].

This document has been updated for Windows 10 and
Windows Server 2019 as follows:

● In Section 1.7,
Versioning and Capability Negotiation, added the 0x021E policy version to the
Policy Version table of behavior note 1, with applicability to Windows Server
v1903 and Windows 10 v1903 operating systems.

● In Section
2.2.2.13, Address Keyword Rules, added and described the 'CaptivePortal'
token, as a representation of the FW_ADDRESS_KEYWORD_CAPTIVE_PORTAL enumeration
value.

Specifies version 2 of the Mobile Device Enrollment
Protocol (MDE), which enables enrolling a device with the DMS through an
Enrollment Service (ES). The protocol includes the discovery of the
Management Enrollment Service (MES) and enrollment with the ES.

This document has been updated for Windows 10 and
Windows Server 2019 as follows:

● Added language
clarifying the role of the deviceenrollmentserviceerror detail element.

● Updated WSDL
fragment to remove unneeded fault node.

● Added content
relating to the "WhiteGlove" context items for this release of
Windows.

Specifies the Mobile Device Management Protocol (MDM),
a subset of the Open Mobile Association (OMA) standard protocol, which
provides a mechanism for managing devices previously enrolled into a
management system through the Microsoft Mobile Device Management Enrollment
Protocol [MS-MDE].

This document has been updated for Windows 10 and
Windows Server 2019 as follows:

● Added content
supporting Version 3.0 of the protocol in this version of Windows.

Specifies the Remote Desktop Protocol: Basic
Connectivity and Graphics Remoting, designed to facilitate user interaction
with a remote computer system by transferring graphics display information
from the remote computer to the user and transporting input from the user to
the remote computer, where it may be injected locally.

This document has been updated for Windows 10 and
Windows Server 2019 as follows:

Specifies the Remote Desktop Protocol: UDP Transport
Extension Version 2 which is used to exchange data, for example audio and
video, between a remote desktop client and remote desktop server over UDP
transport using a URCP based rate control.

● In Section
2.2.1.2.1, Acknowledgement Payload, changed "lesser than or equal to 255
" to "less than or equal to 255" in the delayAckTimeScale
field description.

● In Section 2.2.1.3,
PacketPrefixByte, changed the number that the Short_Packet_Length field
should be set to from 0 to 7 if the length of the RDP-UDP2 Packet that
follows the PacketPrefixByte is greater than 7 bytes.

● In Section
3.1.1.1.5, RDP-UDP2 Packet Network Format:

- described a dummy packet
and its processing rules when it follows the PacketPrefixByte structure.

- changed the number that
the Short_Packet_Length field should be set to from 0 to 7 if the RDP-UDP2
packet size is greater than or equal to 7 bytes.

● In Section
3.1.1.1.5.1, Sending RDP-UDP2 Packet, clarified when the Short_Packet_Length
field of the PacketPrefixByte structure must be set to 7.

● In Section 4.1.2,
On the Receiver when receiving the packet, changed RDPUDP_VERSION_4 to
RDPUDP_PROTOCOL_VERSION_3 in the first step..

Specifies the Windows Remote Registry Protocol, a
remote procedure call (RPC)-based client/server protocol that is used to
remotely manage a hierarchical data store such as the Windows registry.

This document has been updated for Windows 10 and
Windows Server 2019 as follows:

● Modified the
existing Windows product behavior note (section 3.1.1.4) that lists the
registry key paths that are ignored for requests to operate on the 32-bit
registry namespace. This update includes the registry key path that is
ignored on a 32-bit registry namespace on the current release of Windows.

Specifies the Service Control Manager Remote Protocol,
which is used for remotely managing the Service Control Manager (SCM), an RPC
server that enables service configuration and control of service programs.

This document has been updated for Windows 10 and
Windows Server 2019 as follows:

● Updated the list of
operations in opnum order, and added one new method, ROpenSCManager2.

Specifies the Server Message Block (SMB) Protocol
Versions 2 and 3, which support the sharing of file and print resources
between machines and extend the concepts from the Server Message Block
Protocol.

This document has been updated for Windows 10 and Windows
Server 2019 as follows:

● Added support for
compressions and decompression of messages.

March 2019

The document below was updated in March 2019 for Microsoft
.NET Framework 4.8.

This specification defines the XAML Schema Information
Set information items for the Windows Presentation Foundation (WPF) XAML
Vocabulary. The information items in the XAML Schema Information Set
presented in this specification can be used in conjunction with MS-XAML to
determine whether any particular XAML instance or XML document is valid WPF
XAML.

This document has been updated as follows:

● Added new
information items supported by .NET Framework 4.8.

March 2019

In addition, the following documents were updated in March
2019 to add Microsoft .NET Framework 4.8 as an applicable product: