On October 1, Microsoft released the technical preview of Windows 10 and, with much less fanfare, it also unleashed preview releases of Windows Server and System Center. Both server previews are available for download from the TechNet Server and Cloud blog.
I wanted to take a look at the Windows Server technical preview and discuss what we can glean from this release. With Microsoft being open to sharing this early build with the public — rough edges, warts and all — it would be improper to pass final judgment or even offer an evaluative opinion about what is currently in the software. We can speculate and offer some feedback, and I can help you decide whether Windows Server 10 is worth some of your time now to consider and get a feel for, but it is far too early to come to any binding conclusions about this product — for me and for you.
Rather, I want to share what I see are improvements and disadvantages at this point, and give you the context to figure out if this is a release you should follow during its development, and also what you might have to look forward to.
Note: In this piece, I’m going to refer to the Windows Server Technical Preview as Windows Server 10, and the Windows client Technical Preview as Windows 10, just to make it easier to understand.
When you look at what is in this preview release, it is easy to say, “Wow, there’s nothing monumental in here.” While that is true, it may be true only for now. And to say that also does a disservice to the many incremental improvements that really do solve some pain points for shops, particularly around virtualization and storage. Consider the following benefits:
Hyper-V enhancements. You can now upgrade clusters that are running Hyper-V on a rolling basis, fixing a huge problem in earlier versions where all members of a cluster had to be running the same version of an operating system. This removes a big availability obstacle when deploying new versions of an operating system, and allows you to access the improvements Windows Server 10 will bring on an incremental basis, machine by machine and server by server
The virtual desktop feature, which lets you have multiple desktops with windows and boxes separated between them (like a virtual multiple monitor setup), has made it into Windows Server 10.
You can also upgrade any of the members of a Hyper-V cluster or Scale-Out File Server running Windows Server 10 without any downtime for the hosted workloads, which ought to make people responsible for off-hours upgrades cheer. There is also support for secure boot for Linux virtual machines, and you can add virtual memory and virtual network adapters to generation 2 virtual machines running on Windows Server 10 without shutting down the virtual machines themselves (known as a “hot add”).
Significant changes in storage. One of recent Windows releases’ big focus points has been making storage cheap, fast and fault tolerant. For example, there is a wonderful new replication component that copies, block by block, storage — and of course any changes in those blocks — between two hosts. This means there is always a replica of storage that is just a few paces behind; this improves the reliability of many applications.
The new Windows Volume Replication feature copies blocks of storage between servers for highly available storage and cluster setups.
Additionally, there are new rules that administrators can customize and implement that will allow admins to define storage quality-of-service metrics. In other words, an administrator can mandate that a certain application or task get a minimum number of IOPS (I/O operations per second) in any given environment to assure performance, even if the throughput of other applications or workloads has to suffer to service that minimum.
A new version of the best Windows scripting language around. Windows PowerShell 5.0, which has been in preview since mid-April 2014, marks its operating system debut in Windows 10 and Windows Server 10. This new release includes improvements to the Desired State Configuration utility that helps configure systems into a steady state and brings them back if they deviate from that state. There are also improvements to the integrated scripting environment user interface. This area is absolutely still under active development and it is likely PowerShell 5.0 will release before the final version of Windows Server 10 is declared.
Web Application Proxy (WAP) becomes more useful. The demise of Forefront Unified Application Gateway has at least benefited this version of Windows Server, as the WAP role becomes even more full-featured. It will now pre-authenticate users using HTTP Basic authentication. You can publish RemoteApp programs through the Remote Desktop Gateway service, redirect users from HTTP to HTTPS sessions, use wildcards in external URLs of the applications you are protecting and more.
The new Start menu in Windows 10 — or maybe it is better to call it the Start menu we’ve had since Windows 95 — has made its way over to Windows Server 10 and is used by default.
On balance, right now there is not a huge Big Bang feature that will sell you on moving to Windows Server 10. But that was not the point of releasing the technical preview now anyway. Rather, these incremental improvements continue to tear down objections and obstacles to using some really cool new capabilities Microsoft introduced in Windows Server 2012 — and makes them simpler and more accessible.
As you might expect, while there is a lot to like about this preview, there are also some changes that, at least for now, are bound not to sit well with some constituencies. These include:
Network access protection (NAP) is gone. The rumors were true; the technology that allowed you to restrict the ability of untrusted or mistrusted hosts on your network to actually talk over the wire — without remediating whatever problem they had that was causing them to be mistrusted — has been yanked out of this build.
We knew a few months ago that Microsoft had decided to deprecate this feature, and indeed many large organizations still use this technology provided by their own network hardware and not Windows Server. But some medium-sized organizations and small businesses use NAP and will now have to figure out what their story will be. There is no word on how Windows Server 2008 R2, Windows Server 2012, Windows Server 2012 R2 and Windows Server 10 will interact from a NAP standpoint, whether there will be incompatibilities or problems introduced if you are running them all in the same network, and so on. More to come on this piece, but NAP users should consider this a heads up.
The rapid update cadence is slated for future versions of Windows Server, too. One of the big promises about Windows 10 was that it would herald a new model of delivering Windows updates — indeed, the whole operating system itself would update automatically from a branch of code hosted at Microsoft. Gone would be the patches and roughshod updates; instead, you would get what amounted to a new OS during each update cycle.
Consumers cheer this sort of outcome; they value simplicity and want Windows mainly to get out of their way and let them use the Web and their apps.
Corporate customers, on the other hand, scream in anger and rejection (of Windows 8, for one) at this sort of outcome. They need time to test, to make sure their legacy applications still work, to make sure their infrastructure can handle changing features, to make sure no new security problems are introduced with updates.
Despite this, Microsoft says the new update cadence is coming to Windows Server 10, too. There are no details about exactly how this will happen, how customizable it will be and if it will be possible to opt out. This means it is too soon to come to a conclusion about this service and its impact on your operations.
But the bottom line is that in a couple of decades of working with enterprises and institutions, I have never heard one clamor for more updates of a bulkier, more significant nature delivered and applied automatically without any ability to customize how those updates are deployed. This is an area to watch and an area in which Microsoft needs to tread oh so carefully.
You can now cut and paste from the command prompt window — here, I copied the text in Notepad and used CTRL+V to paste it into the command session.
Again, it is early days yet in the Windows Server 10 development cycle, so these drawbacks may well not apply to the final release, or they may evolve into something different. But they are still points to be aware of as we head into playing with this technical preview.