Riporto in questo post delle importanti e utili note, riportate sul sito Technet, per chi volesse provare in anteprime la nuova release di Windows Server TP2.
These release notes summarize the most critical issues in the Windows Server® Technical Preview operating system, including ways to avoid or work around the issues, if known. For information about by-design changes, new features, and fixes in this release, see What’s New in the Windows Server Technical Preview and announcements from the specific feature teams. Unless otherwise specified, each reported issue applies to all editions and installation options of Windows Server Technical Preview.
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.
Important: Upgrades to or from this release are not supported.
If you attempt to upgrade to this release, the network adapter might stop functioning. If this occurs, you might be able to restore network functionality by uninstalling the network adapter and then re-enabling it.
To do this, in Device Manager (Devmgmt.msc), right-click the network adapter and point to Uninstall. Then right-click any item in Device Manager and point to Scan for hardware changes. The network adapter should be automatically detected and re-enabled.
Note: This issue only affects installations made from the ISO image.
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 user 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. To apply it, follow the steps in the Updates section of this topic.
The Edge browser cannot be started. It is also used to deliver certain Help content, so you might encounter an error when accessing Help.
To correct this, change the default browser to Internet Explorer. To do this, open Control Panel, select Programs, select Default programs, select Set your default programs, and then click Internet Explorer in the panel on the left. Click Set this program as default.
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.
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 .
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
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.
Certain Windows shortcuts will fail to open. Personalize and Display settings are known to be affected.
To avoid this, access these settings through Control Panel.
In this release, updating the system with automatic updates, Sconfig.cmd Option 5, or Windows Update in the Control Panel does not work.
To apply updates to Windows Server Technical Preview, do either one of the following:
Open a command prompt and run Sconfig.cmd. In Sconfig, 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.
Visit the Microsoft Update Catalog. Use the Search box to search for Windows Server Technical Preview 2. Click Add for each update you want to install, and then click Next. Review the basket, click Next, and then click Download. Finally, in the folder for each update you downloaded, run the .msu file.