Per multiple cases with AAD Auth support, the PKU2U policy has to be enabled on the client as well. Proposing to update the mentioned Note and add "and the client"
> [!NOTE]
> KU2U is disabled by default on Windows Server. Remote Desktop connections from a hybrid Azure AD-joined server to an Azure AD-joined Windows 10 device or a Hybrid Azure AD-joined domain member Windows 10 device fail. To resolve this, enable PKU2U on the server and the client.
Description:
As reported in issue ticket #6676 (Broken links), the link URL "S mode
devices" (www.microsoft.com/windows/view-all-devices) returns error 404
unless you access the link from a computer using the locale EN-US (only
existing version of the page, non-localized and non-auto-adjusting).
Thank you to RAJU2529 (VARADHARAJAN K) for reporting this issue.
Changes proposed:
- Add /en-us/ to the URL microsoft.com/windows/view-all-devices
- Remove redundant EOL whitespace
- Consistency: add 1 blank line after the page title and next Heading
Ticket closure or reference:
Ref. #6676 (already closed (prematurely), as an incorrect report)
Description:
As reported in issue ticket #6668
(Markdown oddities under Windows 10 Family section), several endpoint
URLs show up in italics/cursive text instead of showing the asterisk as
intended (and visible in other endpoint URLs). This is a result from
inconsistent use of the MarkDown escape character, backslash, to block
the next special character from being read as a formatting character.
Thanks to Tafkae (Lisa H.) for reporting this issue.
Changes proposed:
- Add backslash before all and any asterisk not used in formatting
- Remove all EOL (end-of-line) whitespace (blanks)
- Remove excessive blanks in the numbered list
- Add 1 blank line between the metadata section and the page title
- Add 1 blank space between each table pipe character and its cell text
- Add hyphens to align the width of the second row with the title row
Ticket closure or reference:
Closes#6668
