Was this page helpful?
Your feedback about this content is important. Let us know what you think.
Additional feedback?
1500 characters remaining
Export (0) Print
Expand All

7 Change Tracking

This section identifies changes that were made to this document since the last release. Changes are classified as New, Major, Minor, Editorial, or No change.

The revision class New means that a new document is being released.

The revision class Major means that the technical content in the document was significantly revised. Major changes affect protocol interoperability or implementation. Examples of major changes are:

  • A document revision that incorporates changes to interoperability requirements or functionality.

  • The removal of a document from the documentation set.

The revision class Minor means that the meaning of the technical content was clarified. Minor changes do not affect protocol interoperability or implementation. Examples of minor changes are updates to clarify ambiguity at the sentence, paragraph, or table level.

The revision class Editorial means that the formatting in the technical content was changed. Editorial changes apply to grammatical, formatting, and style issues.

The revision class No change means that no new technical changes were introduced. Minor editorial and formatting changes may have been made, but the technical content of the document is identical to the last released version.

Major and minor changes can be described further using the following change types:

  • New content added.

  • Content updated.

  • Content removed.

  • New product behavior note added.

  • Product behavior note updated.

  • Product behavior note removed.

  • New protocol syntax added.

  • Protocol syntax updated.

  • Protocol syntax removed.

  • New content added due to protocol revision.

  • Content updated due to protocol revision.

  • Content removed due to protocol revision.

  • New protocol syntax added due to protocol revision.

  • Protocol syntax updated due to protocol revision.

  • Protocol syntax removed due to protocol revision.

  • Obsolete document removed.

Editorial changes are always classified with the change type Editorially updated.

Some important terms used in the change type descriptions are defined as follows:

  • Protocol syntax refers to data elements (such as packets, structures, enumerations, and methods) as well as interfaces.

  • Protocol revision refers to changes made to a protocol that affect the bits that are sent over the wire.

The changes made to this document are listed in the following table. For more information, please contact dochelp@microsoft.com.

Section

Tracking number (if applicable) and description

Major change (Y or N)

Change type

2.2.1.1.1 RDP Negotiation Request (RDP_NEG_REQ)

Added a product behavior note regarding the support of the credential-less logon over CredSSP functionality.

Y

New product behavior note added.

2.2.1.2.1 RDP Negotiation Response (RDP_NEG_RSP)

Added a product behavior note regarding the support of the credential-less logon over CredSSP functionality.

Y

New product behavior note added.

2.2.1.3.1 User Data Header (TS_UD_HEADER)

Updated content for Windows 10 and Windows Server 2016 Technical Preview.

Y

Content update.

2.2.1.3.2 Client Core Data (TS_UD_CS_CORE)

Updated content for Windows 10 and Windows Server 2016 Technical Preview.

Y

Content update.

2.2.1.3.8 Client Multitransport Channel Data (TS_UD_CS_MULTITRANSPORT)

72414 : Added the SOFTSYNC_TCP_TO_UDP value definition.

Y

Content update.

2.2.1.4.2 Server Core Data (TS_UD_SC_CORE)

Updated content for Windows 10 and Windows Server 2016 Technical Preview.

Y

Content update.

2.2.1.4.6 Server Multitransport Channel Data (TS_UD_SC_MULTITRANSPORT)

Updated content for Windows 10 and Windows Server 2016 Technical Preview.

Y

Product behavior note updated.

2.2.1.4.6 Server Multitransport Channel Data (TS_UD_SC_MULTITRANSPORT)

72414 : Added the SOFTSYNC_TCP_TO_UDP value definition.

Y

Content update.

2.2.1.11.1.1 Info Packet (TS_INFO_PACKET)

72226 : Updated descriptions for INFO_REMOTECONSOLEAUDIO and INFO_NOAUDIOPLAYBACK.

Y

Content update.

2.2.5.2 Server Status Info PDU

72199 : Updated statusCode field values.

Y

Content update.

2.2.7.1.6 Input Capability Set (TS_INPUT_CAPABILITYSET)

72287 : Added content stating that the keyboardLayout, keyboardType, keyboardSubType, and keyboardFunctionKey fields SHOULD be set to zero, and the imeFileName field SHOULD be filled with zeros.

Y

Content update.

2.2.7.1.6 Input Capability Set (TS_INPUT_CAPABILITYSET)

Updated content for Windows 10 and Windows Server 2016 Technical Preview.

Y

Content update.

2.2.7.1.9 Offscreen Bitmap Cache Capability Set (TS_OFFSCREEN_CAPABILITYSET)

72584 : Updated the definitions for the offscreenCacheSize and offscreenCacheEntries fields.

Y

Content update.

2.2.8.1.1.3.1.1.1 Keyboard Event (TS_KEYBOARD_EVENT)

72223 : Added KBDFLAGS_EXTENDED1 to possible value table for field keyboardFlags.

Y

Content update.

2.2.8.1.2.2.1 Fast-Path Keyboard Event (TS_FP_KEYBOARD_EVENT)

72223 : Added description for FASTPATH_INPUT_KBDFLAGS_EXTENDED1 to possible value table for field eventHeader.

Y

Content update.

2.2.8.1.2.2.6 Fast-Path Quality of Experience (QoE) Timestamp Event (TS_FP_QOETIMESTAMP_EVENT)

Added section with content for Windows 10 and Windows Server 2016 Technical Preview.

Y

New content added.

2.2.9.2.1 Set Surface Bits Command (TS_SURFCMD_SET_SURF_BITS)

72539 : Updated with information that the encoded bitmap data is destined for a rectangular region of the primary drawing surface and that the destRight and destBottom fields SHOULD be ignored.

Y

Content update.

2.2.9.2.2 Stream Surface Bits Command (TS_SURFCMD_STREAM_SURF_BITS)

72539 : Updated with information that the encoded bitmap data is destined for a rectangular region of the primary drawing surface.

Y

Content update.

2.2.11.2 Client Refresh Rect PDU

67852 : Added behavior clarification for Refresh Rect PDU.

Y

New product behavior note added.

2.2.15.1 Server Initiate Multitransport Request PDU

Updated content for Windows 10 and Windows Server 2016 Technical Preview.

Y

Product behavior note updated.

2.2.15.2 Client Initiate Multitransport Response PDU

72414 : Renamed section and updated the hrResponse values definition.

Y

Content update.

2.2.16.1 Server Heartbeat PDU

72414 : Updated that the PDU SHOULD only be sent when no other PDUs have been sent to the client in a given heartbeat interval  .

Y

Content update.

3.2.5.3.2 Processing X.224 Connection Confirm PDU

72625 : Updated by stating that once the External Security Protocol handshake has successfully run to completion and all  authentication requirements have been fulfilled, the client SHOULD continue.

Y

Content update.

3.2.5.8.1.2 Sending Fast-Path Input Event PDU

Updated content for Windows 10 and Windows Server 2016 Technical Preview.

Y

Content update.

3.2.5.15.2 Sending the Initiate Multitransport Response PDU

72414 : Renamed the section and clarified that if the hrResponse field indicates a failure, the client MUST NOT attempt to create a sideband channel.

Y

Content update.

3.3.5.8.1.2 Processing Fast-Path Input Event PDU

Updated content for Windows 10 and Windows Server 2016 Technical Preview.

Y

Content update.

3.3.5.15.2 Processing the Initiate Multitransport Response PDU

72414 : Renamed the section.

Y

Content update.

5.5 Automatic Reconnection

Deleted the statement regarding the one-way HMAC transformation preventing an unauthenticated server from obtaining the original auto-reconnect random.

Y

Content update.

5.5 Automatic Reconnection

72532 : Clarified that the client random array size is 32 zero bytes.

Y

Content update.

6 Appendix A: Product Behavior

Updated content for Windows 10.

Y

Content update.

Show:
© 2015 Microsoft