Windows Server Insider Preview Build 17079 Released to Windows Insiders

A new Windows Server Insider build is now available. Microsoft has delivered another new Windows Server Insider Preview Build 17079 to Windows Server Insiders.

The latest build is a preview build of the next Semi-Annual Channel release of Windows Server. It brings some new features, improvements, and known issue.

Here’s a look of change-log in Windows Server Insider Preview Build 17079:

New in Windows Server Insider Preview Build 17079

• In-place OS Upgrade: Customers are now able to upgrade their Windows Server, version 1709 installations to the current preview build using In-place OS Upgrade. This feature is available starting in build 17079. This feature also enables customers to perform build-to-build upgrade of the next released preview build.Running setup.exe, customers should be presented with the option to “Keep personal files and apps”, which causes the migration steps in setup.exe to run and upgrade Windows Server while preserving applications, data, and user settings.

Developers and Containers

• • Optimized Server Core container base images (30% smaller). Available on Windows Insider Docker Hub here
  • MSMQ now installs in a Server Core container
  • Key Application Compatibility bug fixes

For more details, please see the Window Virtualization Blog here.

Available Content

Server Insiders have the choice of Server Core Edition in ISO or VHDX format. The images are pre-keyed – no need to enter a key during setup.

Symbols are available on the public symbol server – see Update on Microsoft’s Symbol Server blog post and Using the Microsoft Symbol Server. As before, matching Windows Server container images will be available via Docker Hub. For more information about Windows Server containers and Insider builds, click here.

Known issues in Windows Server Insider Preview Build 17079

• [NEW] When Hypervisor Code Integrity (HVCI) is enabled, a system may fail to start. On affected systems, firmware locates UEFI runtime services in memory described as Memory-Mapped I/O (MMIO).
• Running nanoserver-insider containers on a Windows Server Core host will fail, and may crash the host.
  As a workaround, you can add “—isolation=hyperv” when running or building the containers such as “docker run –isolation=hyperv microsoft/nanoserver-insider”.

Known Issues with In-place OS Upgrade

(1) Drives that are protected with BitLocker should have BitLocker suspended (disabled) before In-place OS Upgrade, and resumed (enabled) after In-place OS Upgrade.

(2) AD Domain Controllers might not upgrade correctly – please backup any AD DC before applying In-place OS Upgrade.

You can share or follow us on Twitter, add us to your circle on Google+ or like our Facebook page to keep yourself updated on all the latest info from Microsoft, Google, Apple and the Web.