At the same time Microsoft released the Windows Server 2016 Technical Preview 2 bits to MSDN subscribers, they also released the Release Notes on a page on the Microsoft Download Center.
On this page you can view the critical issues, that have currently been identified, that might require avoidance or workaround to get Windows Server 2016 Technical Preview 2 installed and running.
Below is the list with the current important issues for Windows Server 2016 Technical Preview 2:
Logging on
In some instances during logon, the computer might stop responding or might display a black screen. If this occurs, in all cases press Ctrl+Alt+Del to proceed with logging in.
For example, the first time you log on after installation is complete, you will be prompted to change the Administrator password. If you fail to do this within two minutes or click Cancel, the computer might appear to be unresponsive. Similarly, a person who attempts to log on using an expired password could experience the same symptoms.
In another case, once you have joined the computer to a domain, the computer might become unresponsive with the message Please wait for the Local Session Manager. Press Ctrl+Alt+Del to proceed with logging in
Update KB3061186 fixes this issue.
Desktop Experience
If you have installed the Desktop Experience feature and then try to uninstall it, the uninstallation will fail with an error. There is no workaround at this time.
Converting UI mode
If you attempt to switch from Server with a GUI mode to Server Core mode in one step (that is, if you try to uninstall the Server-GUI-Mgmt-Infra and Server-GUI-Shell features at the same time), the uninstallation will fail. This will occur regardless of the uninstallation method, including using Server Manager, dism.exe, or Windows PowerShell.
To avoid this, uninstall Server-GUI-Shell first, and then uninstall Server-GUI-Mgmt-Infra.
Group Policy
In this release, the following Group Policy Objects are not implemented:
- Specify intranet Microsoft update service location
- Do not connect to any Windows Update Internet locations
- Allow signed updates from an intranet Microsoft update service
Remote Desktop Services
If you use Server Manager to configure a Remote Desktop Services environment with a self-signed certificate, the action will fail.
To avoid this, use the New-SelfSignedCertificate Cmdlet for Windows PowerShell to create the certificate and save it as a .pfx file. Then use that certificate with Server Manager to configure the Remote Desktop Services environment.
If you attempt to deploy Windows 10 Technical Preview as a guest operating system in a Virtual Desktop Infrastructure (VDI), Sysprep.exe fails with error 0x87af0005. There is no workaround at this time, so evaluate VDI scenarios using Windows 8.1 as the guest operating system.
If you create a VDI in a clustered environment, you cannot use the Remote Desktop Connection broker to mark a virtual machine for high availability. Also, if you migrate a virtual machine from one virtualization host to another, users will no longer be able to connect to it.
To avoid this, mark virtual machines as highly available using Failover Cluster Manager or with clustering Windows PowerShell commands. If a virtual machine gets lost by the broker after a migration, an administrator must explicitly add the virtual machine back into the collection. To do this, use the Remote Desktop Management Windows PowerShell Cmdlet Add-RDVirtualDesktopToCollection.
Server roles
If you attempt to install File Server Resource Manager or Print-Scan-Server at the same time as any other role or feature that requires a restart, none of the roles or features will actually install successfully, although the installation will appear to be successful.
To avoid this, install File Server Resource Manager or Print-Scan-Server separately from any other roles or features. You can install these roles either before or after other roles and features, but be sure to complete any restarts before installing the other roles and features.
Updates
In this release, updating the system with automatic updates, sconfig.exe Option 5, or Windows Update in the Control Panel does not work.
To apply updates to Windows Server Technical Preview, open a command prompt and run sconfig.exe. In sconfig.exe, select Option 6, “Download and Install Updates.” Windows Update will scan the system and query the update location you have configured with either Windows Update or Windows Server Update Server, and then install any new updates.
