2.2.1.4.2 Server Core Data (TS_UD_SC_CORE)
The TS_UD_SC_CORE data block contains core server connection-related information.
|
|
|
|
|
|
|
|
|
|
1 |
|
|
|
|
|
|
|
|
|
2 |
|
|
|
|
|
|
|
|
|
3 |
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
header |
|||||||||||||||||||||||||||||||
|
version |
|||||||||||||||||||||||||||||||
|
clientRequestedProtocols (optional) |
|||||||||||||||||||||||||||||||
|
earlyCapabilityFlags (optional) |
|||||||||||||||||||||||||||||||
header (4 bytes): A GCC user data block header, as specified in User Data Header (section 2.2.1.3.1). The User Data Header type field MUST be set to SC_CORE (0x0C01).
version (4 bytes): A 32-bit, unsigned integer. The server version number for the RDP. The major version number is stored in the high two bytes, while the minor version number is stored in the low two bytes.
-
Value
Meaning
0x00080001
RDP 4.0 servers
0x00080004
RDP 5.0, 5.1, 5.2, 6.0, 6.1, 7.0, 7.1, 8.0, and 8.1 servers
0x00080005
RDP 10.0 servers
0x00080006
RDP 10.1 servers
0x00080007
RDP 10.2 servers
0x00080008
RDP 10.3 servers
0x00080009
RDP 10.4 servers
0x0008000A
RDP 10.5 servers
0x0008000B
RDP 10.6 servers
0x0008000C
RDP 10.7 servers
0x0008000D
RDP 10.8 servers
0x0008000E
RDP 10.9 servers
0x0008000F
RDP 10.10 servers
0x00080010
RDP 10.11 servers
0x00080011
RDP 10.12 servers
-
If the server advertises a version number greater than or equal to 0x00080004, it MUST support a maximum length of 512 bytes for the UserName field in the Info Packet (section 2.2.1.11.1.1).
clientRequestedProtocols (4 bytes): A 32-bit, unsigned integer that contains the flags sent by the client in the requestedProtocols field of the RDP Negotiation Request (section 2.2.1.1.1). In the event that an RDP Negotiation Request was not received from the client, this field MUST be initialized to PROTOCOL_RDP (0). If this field is not present, all of the subsequent fields MUST NOT be present.
earlyCapabilityFlags (4 bytes): A 32-bit, unsigned integer that specifies capabilities early in the connection sequence.
-
Value
Meaning
RNS_UD_SC_EDGE_ACTIONS_SUPPORTED_V1
0x00000001
Indicates that the following key combinations are reserved by the server operating system:
WIN + Z
WIN + CTRL + TAB
WIN + C
WIN + .
WIN + SHIFT + .
In addition, the monitor boundaries of the remote session are employed by the server operating system to trigger user interface elements via touch or mouse gestures.
RNS_UD_SC_DYNAMIC_DST_SUPPORTED
0x00000002
Indicates that the server supports Dynamic DST. Dynamic DST information is provided by the client in the cbDynamicDSTTimeZoneKeyName, dynamicDSTTimeZoneKeyName, and dynamicDaylightTimeDisabled fields of the Extended Info Packet (section 2.2.1.11.1.1.1).
RNS_UD_SC_EDGE_ACTIONS_SUPPORTED_V2
0x00000004
Indicates that the following key combinations are reserved by the server operating system:
WIN + Z
WIN + TAB
WIN + A
In addition, the monitor boundaries of the remote session are employed by the server operating system to trigger user interface elements via touch.
RNS_UD_SC_SKIP_CHANNELJOIN_SUPPORTED
0x00000008
Indicates that the server supports skipping the MCS Channel Join Request PDUs (section 2.2.1.8) and MCS Channel Join Confirm PDUs (section 2.2.1.9) in the Channel Connection phase of the RDP Connection Sequence (section 1.3.1.1).
If this flag is set, the server considers all MCS channels as joined after the MCS Attach User Confirm PDU (section 2.2.1.7) has been sent (section 3.3.5.3.8).
-
If this field is present, all of the preceding fields MUST also be present.