Today, Microsoft released the first Insider Preview build of Windows Server, part of the Insider Program that it announced back in May. Obviously, it's the first taste of the Redstone 3 Development Branch that Server customers have seen so far, so there are quite a few new features.
But of course, that also means that there are a whole bunch of known issues (since it's the first of its kind, there are obviously no fixes):
Local vs remote management: Some command-line tools and PowerShell modules may not be available for use locally on a Server Core installation. To remotely manage Server Core by using the full set of GUI tools, command-line tools, and PowerShell modules, use Remote Server Administration Tools for Windows 10, available for download from the preceding link.
If a user attempts to update to the latest OS build on a device that has .NET Framework 3.5 installed, the update may fail because of a side-by-side (SXS) assembly missing error (0x80073701), and the device will roll back to the previous build. To work around this issue, uninstall .NET Framework 3.5, perform the OS update, and then reinstall .NET Framework 3.5. (The last step is optional if the user does not have apps that are dependent on .NET Framework 3.5.)
Some devices using a common 64-bit chip architecture may not be able to update to the latest OS build because of an unexpected error (E_UNEXPECTED, error code 0x8000FFFF).
An app may become unresponsive because of an application hang end task error (0xCFFFFFFF) in the Windows firewall API library (FirewallAPI.dll), which occurs when the library is blocked on an advanced local procedure call (ALPC) while attempting to diagnose a connection failure and retrieve information during network isolation.
Cluster Sets: A couple of key functionalities to enable end-to-end testing of Cluster Sets scenarios are not present in this build, so defer all evaluation of this scenario to a future build.
Bugcheck during volume creation: A stop error may occur during volume creation in a cluster. The recommended workaround is, after restarting the computer, to delete the volume and try creation again.
Bugcheck during volume repair: A stop error may occur during volume repair in a cluster. The recommended workaround is to restart the computer. No corruption or data loss is expected.
AEP is not supported in this build.
Clone support for Hyper-V isolated containers does not work, this can be disabled temporarily and will be fixed in subsequent Insider Preview builds. See the Insider section on https://aka.ms/containersfor more details
Obviously, an Insider Preview for Windows Server probably isn't something that you'd run in a production environment; if you do, you should certainly be aware of known issues, and also know that there will be different issues with upcoming builds. Of course, it's definitely a great way to test out new features that will be coming with the next major update.
4 Comments - Add comment