By Dona Sarkar and Brandon LeBlancHello Windows Insiders!
Today we are pleased to release Project Honolulu Technical Preview 1803 to Windows Server Insiders. Also available is the Insider preview package of Remote Server Administration Tools (RSAT) for Windows 10 Insider build 17110 or higher.
- Project Honolulu Technical Preview 1803
- Remote Server Administration Tools Build 17108
This preview build of Remote Server Administration Tools (RSAT) can be installed on Windows 10 Insider build 17110 or higher.
FIXED: DNS server tools are now correctly installed as part of the RSAT package.
FIXED: Shielding data files and template disks can now be created by their respective wizards in the RSAT package.
KNOWN ISSUE: The x86 RSAT package may fail during installation on Windows 10 builds older than 17110, and on builds other than the 171xx series.
What’s New in Project Honolulu Technical Preview 1803 Release Summary
In this iteration, we resolved 430 bugs, as well as the following feature improvements –
Major new functionality in this release — we have added Azure Active Directory (AAD) based access control. Using AAD identities, you can configure conditional access policies that require Multi-Factor authentication, device compliance, and more. You can find instructions to configure this in the Azure Active Directory section of the Gateway access documentation.
Known issue with AAD authentication: If you are using a self-signed certificate, AAD authentication will fail in Microsoft Edge. To work around this issue, you must use a valid certificate or choose to trust the self-signed certificate on your machine where you are running the Edge browser.
We’ve updated the logging schema to include more details for auditing and troubleshooting. Previously, the only details logged were the module, user on the target node, and the PowerShell script or CIM call executed. Now events are logged with these parameters:
- Module: which tool triggered the action being logged
- CIM call, PowerShell script name, or file uploaded
- Gateway from which the action occurred
- UserOnGateway: the username used to access the Honolulu gateway
- UserOnTarget: the username used to access the target node (if different from the gateway user)
- LAPS: Boolean showing whether LAPS was used to connect to the target node