System Documents
The System Documents are legacy overview documents that prescribe the usage and architectures of Windows protocols specific to the MCPP Licensing Program. Microsoft has developed a new set of Overview Documents that are organized by Windows technical area rather than by licensing program. Their design, based on feedback, more clearly illustrates how Windows protocols that are functionally related work together, with practical examples that demonstrate common usage scenarios. The new Overview Documents can be found here.
| Specification | Description |
|---|---|
|
Describes the family of protocols that comprise the Active Directory System. Active Directory also documents abstract state shared between the system's protocols. This document should be read by anyone interested in implementing the Active Directory System, as it provides a high-level introduction to the functionality of the system and serves as documentation for which protocols must be supported by an implementation of the Active Directory System. |
|
|
[MS-AUTHSO]: Windows Authentication Services System Overview |
Describes a representative sample of authentication tasks that use the Windows Authentication Services System. Tasks described in this document incorporate protocols that in turn use authentication protocols, which include Interactive Domain Logon, Internet Web Access with HTTP, file services with SMB [MS-SMB] [MS-SMB2], and remote operations with RPC [MS-RPCE]. Negotiate [MS-SPNG], Kerberos [MS-KILE], NTLM [MS-NLMP], and APDS [MS-APDS] are some of the protocols that may be employed during authentication tasks. |
|
Describes the functionality of autoenrollment and how it uses certificate enrollment protocols. It provides examples of some of the common usage scenarios. It does not restate the processing rules and other details that are specific for each protocol. These details are described in the protocol specifications for each of the protocols and data structures that this task uses. |
|
|
Provides a system overview of the protocols in the Microsoft Certification Authority (CA) system. The CA system uses public key cryptography to issue certificates that can be used for a variety of purposes including encryption and authentication. This document describes the intended functionality of the CA system and how the protocols in this system interact. It provides examples of some of the common usage scenarios. |
|
|
Describes the Windows Content Caching and Retrieval System. It includes a description of the protocols, data structures, and mechanisms (such as security) required to enable a system of content caching and retrieval to interoperate with Windows systems that use the feature known as BranchCache™. |
|
|
Describes two sets of logical procedures (Defined Tasks) used when Collaboration Clients locate each other on a network using the directory services provided by an Internet Locator Service (ILS) Server.These Tasks involve a set of protocols for locating potential collaborative partners. Collaboration itself is performed through instances of the NetMeeting application.These Tasks require communication between the NetMeeting client and the ILS Server to enable NetMeeting clients to discover other NetMeeting clients available on the server.This document describes the intended functionality of the Collaboration Services Tasks and how the protocols in this system interact. It provides examples of some of the common user scenarios. It does not restate the processing rules and other details that are specific for each protocol. These details are described in the protocol specifications for each of the protocols and data structures that make up this system. |
|
|
Microsoft Windows networks are often configured with a domain controller providing centralized storage of accounts and administration of many computers. Many network-related operations depend on domains in order to complete various tasks. The Domain Interactions System includes the most common domain interaction tasks, such as locating a domain controller, joining a domain, and removing a domain member.This document specifies how the protocols that comprise the offerings from Microsoft are used together to maintain a relationship with the domain. This includes protocols that are used to communicate with a domain controller and maintain state, protocols that are used to augment authentication and authorization actions, and protocols that are used to interact with domain controllers. |
|
|
Describes the intended functionality of the File Access Services System, how it interacts with systems and applications that need file services, and how it interacts with administrative clients to configure and manage the system. File Access Services uses multiple protocols for file access and file server administration. This document lists those protocols and describes how they are used to implement the File Access Services System. |
|
|
Describes how the protocols in the Group Policy System work together to support this functionality. It describes how this system interacts with the administrative tools used to define and apply policy settings, the data stores where the policy settings are stored, and the various client-side and server-side components that extend the policy application and policy administration functionality of the system. |
|
|
The Multiplayer Games System is designed to transport game and user data to support multiplayer gaming scenarios. The protocols in this system provide game session management as well as functionality for controlling options for sending data and voice. Control options for data include reliability, guaranteeing data delivery sequencing, and coalescence of packets. The DirectPlay System also provides functions for using network address translation (NAT). This document describes the intended functionality of the DirectPlay System and how it interacts with applications. The DirectPlay System supports multiple protocols for multiplayer gaming. This document lists those supported protocols and how they interact in a combined system. |
|
|
Provides a system overview of the protocols in the Message Queuing system. The Message Queuing (MSMQ) system is a communications service that enables reliable and secure asynchronous messaging between applications over a variety of deployment topologies. This document describes the intended functionality of the Message Queuing system and how the protocols in this system interact. It provides examples of some of the common usage scenarios. |
|
|
Describes the intended functionality of the Media Streaming Server System and how it interacts with systems or applications that need to stream media. A streaming media system is designed to distribute digital media content from an encoder or a capture application to a media server, and finally, to a media player for rendering or playback of that content. The Media Streaming Server System protocols are a series of protocols designed to achieve that task. |
|
|
[MS-NAPSO]: Network Policy and Access Services System Overview |
Describes a series of Tasks required to allow client computers to gain access to a NAP-protected network; also describes how various components work together to aid in ensuring the health and protection of networked systems. |
|
Describes a distributed system of Print Servers that manage printers and make them available to Print Clients. One or more servers may be used, each server independently managing one or more printers. Clients use the component protocols to submit print jobs, manage jobs, receive job notifications, and administer printer drivers and Print Queues. |
|
|
Describes the intended functionality of the Rights Management Services System, how it interacts with systems or applications that create or consume rights protected content, and how it interacts with management clients that need to configure and manage the system. |
|
|
Transaction processing is designed to maintain a computation system in a known, consistent state. It allows multiple individual operations to be linked together as a single, indivisible operation: an atomic transaction. Broadly speaking, transaction processing involves updating data, which may be distributed across multiple systems, so that either all the changes happen or none of the changes happen. This document describes the intended functionality of the Transaction Processing Services System, how it interacts with systems or applications that need transaction processing, and how it interacts with management clients that need to configure and manage the system. Transaction Processing Services System supports multiple protocols for transaction processing and management. This document lists those supported protocols and how they interact in a combined system. |
|
|
Describes the Terminal Services System, a system that enables a remote client to display and interact with a desktop or application running on a distant server. A remote client connected to the server can use software and resources available to the server according to license restrictions. This document describes the relationship of the system of protocols that comprise the Terminal Services System, background information about the system, use cases that exercise the component protocols, abstract data models of system components, internal system architecture, and details about the communications that occur between system components. |
|
|
Windows management systems are designed to allow a user to monitor, troubleshoot, and conduct hardware and software inventories of remote computers.This document describes the intended functionality of the Windows Management Services System, how it interacts with applications that need computer management, and how it interacts with management clients that need to configure and manage the system. The Windows Management System supports multiple protocols for computer management. This document lists those supported protocols and how they interact in a combined system. |
|
|
The Windows Protocols system includes the set of protocols that are part of the Microsoft Communications Protocol Program (MCPP). This includes protocols implemented in a Microsoft Windows 2000 Professional, Windows XP, Windows Vista, or successor desktop operating system that are used to interoperate or communicate with a Microsoft Server operating system product. This document provides a system overview for protocols and systems described in the protocols technical documents (TDs), Protocol Family system documents (PFSDs), and Defined Tasks system documents (DTSDs) that are included in the MCPP program. It provides a system overview of how these systems and protocols relate to each other. |
|
|
Describes the intended functionality of the Windows Server Update Services System and how the protocols in this system interact. It provides examples of some of the common user scenarios. It does not restate the processing rules and other details that are specific for each protocol. These details are described in the protocol specifications for each of the protocols and data structures that make up this system. |
Licensing Information
Microsoft makes these technical specifications available to view and download at no charge and without restriction. Many of the specifications, however, include patented inventions. Some of those patents are available at no charge under the Open Specifications Promise or the Community Promise. The remaining patents are available through various licensing programs. For information about those programs, please visit the Microsoft Open Specifications website or email the Open Specifications Team.
Support and Resources
-
Open Specifications Forums: These MSDN forums are available to answer technical questions regarding the technical specifications and support developers implementing the technical specifications.
-
Open Specifications Developer Center: This Developer Center provides access to resources designed to assist developers implementing the technical specifications, including white papers, tools, and training videos.
-
Microsoft Open Specifications: This website provides information on licensing programs for patents covering the technical specifications as well as access to a variety of support and other resources such as test tools, training videos, interoperability events (including plugfests and interoperability labs), and case studies.
