Long list of updates answer criticisms and throw punches at virtualization, cloud foes
In Windows Server 2012 R2 and Windows 8.1, Microsoft has released a combination of operating system updates that we find very compelling. Microsoft has joined much of the rest of the industry in annual release roll-ups with feature additions, and this time, they listened to the critics. More interesting are the one-upmanship features targeted directly at its virtualization and cloud competition. Some were stunning, despite a few strange and perhaps anecdotal basic problems that we found.
Windows 8.1 is the answer to loud and vociferous complaints regarding radical changes to the user interface found in Windows 8, and is currently a free upgrade for 8.0 users. What's apparent in 8.1 is that Microsoft is committing strong changes to the tablet and touch user interface in its Surface devices first, in order to compete with Apple and Android. If 8.0 didn't convince you, then 8.1 is a shot across the bows of those believing that desktops and notebooks rule IT.
[ALSO: The hidden fangs of Windows 8.1]
[LOVEFEST: 10 things we love about Windows Server 2012]
Microsoft has targeted Windows 2012 R2 directly at data center and service provider use, along with baseline connectivity to Azure Cloud services and third party Azure services providers. Microsoft's other targets are Oracle and VMware.
Microsoft offers a free add-in for Windows 2012 R2 of its Azure Pack to connect cloudlike constructs, and anchors it with various free and paid appliance services that battle competing IaaS/SaaS providers and other MSP/cloud competitors. Through gritted teeth, Microsoft is also supporting specific instances of commonly used Linux distros as manageable guests within the Hyper-V and Azure infrastructure.
By contrast to the heavy work done in 2012 R2, Windows 8.1 is a far lighter weight set of changes, and largely addresses criticisms of Windows 8.0.
Authentication and access enabling technologies are important in a BYOD universe. Many Windows users find Apple's iTunes to be difficult to use as an authentication system under Windows, with frequent unthreaded new releases. Microsoft has responded with a unified identity method enhancement of its Windows Intune ecosystem and Active Directory-poised authentication methods.
The Good News
What we liked about Windows 2012 R2 is that it's generally easier to use than Windows 2012 -- fewer sharp edges -- and 2012 R2 contains stronger networking, storage, and hypervisor skills, we found in testing. Microsoft has also made it almost fiendishly consistent and easy to join Windows 2012 R2 to Azure Clouds -- and it's practical if organizations have fast Internet pipes.
Both new Windows releases are highly targeting enterprise customers, although a Windows 2012 R2 Server Essentials Edition (traditionally limited to 25 or fewer users) is available, and not reviewed here. The Essentials Edition must live within three total VMs, which limits possible users, unless something unforeseen and magical happens in hardware.
If organizations want a control plane, Microsoft attaches System Center 2012 R2 releases of Ops Manager, Virtual Machine Manager, and Configuration Manager that are deeply intertwined into the depths of Server 2012 R2 and Hyper-V.
During briefings with Microsoft, we had to constantly disambiguate what was a Server or Azure or System Center feature as Microsoft blends them together. In doing so, Microsoft wants its value proposition to be considered as a mixture of the three, but this review focuses on only the Server, Windows 8.1, and the free connection to Azure Pack.
For its part, Windows 8.1 solves the silliness of bringing back the familiar Desktop, along with ways to access applications in ancient and hallowed ways. While the Windows Start menu is gone (available from third parties if desired), there's a method to show apps selections onscreen easily. Windows 8.1 is also faster than 8.0 — this additional speed makes the most impact when it comes to video drivers and the Server Message Block (SMB3) communications transport protocol.
SMB3 speed isn't proprietary to Windows as SAMBA 4.1 -- the open source SMB emulator that can be used by Mac OS, Linux, BSD, and other non-Windows operating systems, is now compatible with SMB3. However, SAN and NAS devices may not support SMB3 until vendors can get caught up.
Much attention in Windows 8.1 surrounds features that will be found in tablets, like Microsoft's own Surface Pro. Multi-touch object manipulation and attention towards touch and tethered keyboard combinations abounds. We tested 8.1 and found an enormous variety of keyboard manipulations and touch motions that produced interesting effects.
2012 R2 and Hyper-V
Windows 2012 R2 contains a number of storage options poised towards Hyper-V, but we found that R2 can probably be booted from a wristwatch and store data on our sneakers -- if we format them NTFS. We successfully booted local hardware (you may need BIOS updates), iSCSI, and virtual network storage. Many will be booting VMs, and Microsoft has made this especially simple under Hyper-V V3.
Hyper-V V3 has received much work, and Microsoft considers it a “Generation 2” hypervisor VM-hosting platform that delivers a higher degree of para-virtualization and cuts away much hardware layer specific driver emulation, although other OS versions/distros of hosted VMs can still find connection points.
Hyper-V V3 and its Windows 2012 VMs also boot UEFI, rather than traditional memory-location-specific BIOS. This gave us a few fits, but works. There is the capacity to move virtual machines from host to host using compression, and where compatible hardware is available to support it, very fast transports -- 10Gigabit Ethernet, Infiniband, and other faster-than-10G Ethernet connections. The high-speed connections are crucial to VM movements among hosts in hypervisor fabrics.
We tested Microsoft's virtual network switching component, and found it easy to manipulate, although we disconnected several remote hosts by making inept choices. The instructions weren't clear to us, and we were able to crater the communications of two of our test servers with ease. The drive to our network operations center is a long one.
The SDNs inside Hyper-V V3 are more easily manipulated by System Center 2012. Microsoft includes IP Address Management/IPAM in Hyper-V, and as VMware has found, is heaven-sent for those with genuine desires to form virtualization platforms where VMs can be easily transported from host to host for either performance or isolation within a defined fabric/VM farm.
Hyper-V V3 resources can be aggregated into clusters, and through the use of new VHDX sharable disk stores, can create islands internally -- or for cloud-hosted purposes, external clouds whose resources should be opaque to other cloud components. We were not able to successfully find constructs to test the opaque nature of what should be isolated clouds, but rudimentary tests seemed to prove isolation. The VHDX format can also be dynamically re-sized as the need arises; we found that the process is fast, although during that period, disk and CPU resources can peak until the modification is over. Heavy CPU/disk-imposed limitations thwart resizing by slowing it.
We also tested Hyper-V and 2012R2 IPAM and Microsoft's SDN successfully under IPv4 (other limitations prevented heavy IPv6 testing). Software defined networks (SDN) cross a turf that is divided in many organizations: virtualization and network management teams. Network management staff have traditionally used IPS, routing, switching and infrastructure controls to balance traffic, hosts, even NOC hardware placement. SDN use means that what were once separate disciplines are now forced to work together to make things work inside the host server's hypervisor, where the demarcation was once where the RJ-45 connector meets the server chassis.
IPAM allowed us to define a base allocation of routeable and/or non-routeable addresses, then allocate them to VMs hosted on Hyper-V hosts or other hosts/VMs/devices on our test network. We could in turn, allocate virtual switches, public private or internal, connected with static/blocked and sticky DHCP. Inter-fabric VM movements still require a bit of homework, we found. Using one IPAM is recommended.
[ALSO: Windows 8.1 cheat sheet]
What we like is that the SDN primitives and IPAM can work well together, with well-implemented planning steps. We could create clouds easily, and keep track of address relationships. A Microsoft representative mused over the spreadsheets that carry IP relationship management information in many organizations, calling it crazy. We would agree, and believe that hypervisor or host-based IPAM is a great idea. If only DNS were mixed in more thoroughly -- and it's not -- we'd be complete converts to the concept. We found it very convenient nonetheless, although errors were more difficult to find when they occurred, such as address pool depletions. Uniting networking and virtualization/host management disciplines isn't going to be easy.
The Bad News
We found head-scratchers and limitations. We found several initial foibles installing the operating system on bare metal to what should be generic hardware. We were able to overcome them, but warn installers that they'll need to consider that Windows 2012 and especially R2 might require updated server BIOS firmware to UEFI-compatible, as happened with our Lenovo ThinkServer and HP DL 380 Gen8 servers. When Windows 2012 R2 can't install (R2 or Hyper-V V3-R2), we received an inarticulate flash of an error message. We actually took a video of it to capture that there was a problem with ACPI -- and not UEFI. The turf between platform providers and OS/hypervisor makers is still real and strong, but Microsoft isn't alone, as we've incurred driver/platform mysticism with VMware and Oracle, too.
We found the Hyper-V role cannot be re-instantiated. This means that no hypervisor on top of a hypervisor. Microsoft claims that there has been no customer demand for this, but it also imposes a limitation. Although running a hypervisor atop a hypervisor seems silly, there are cases where it's useful. One role often cited is in production test labs, and another where Microsoft's SDN is used -- Hyper-V V3 must always be the base layer talking to the metal and silicon of a server, precluding other schemes direct access to the metal and therefore impeding other SDN schemes.
The Azure Pack uses the same Hyper-V infrastructure as Windows Server 2012 R2. Microsoft offers a sample of what other third party providers may offer in the form of services and ready-to-deploy pre-built appliances. We were reminded of what TurnKeyLinux started several years ago, in terms of usable appliances built from Linux substrates. There isn't a huge variety of appliance samples available, but what we tested, worked -- full WordPress websites that were ready for skins and customizations.
A Service Bus, actually message bus, connects components in the clouds serviced by the Azure Pack and Hyper-V. The Service Bus connects Microsoft-specific API sets, after a framework “namespace” is created. Communications can be subscribed and published to the framework and its members in the namespace talk via REST, Advanced Message Queueing Protocol/AMQP, and Windows instrumentation APIs. The Service Bus reminds us of products like Puppet, Chef, and others in the Linux world, communicating in a stack-like framework for rapid deployment and ease of VM and infrastructure fleet management.
Where Windows 8.1 is upgraded on Windows 7 or Windows 8 platforms, the upgrade was fast and made no mistakes. Windows XP can be run atop Hyper-V or in a Type 2 hypervisor application, but we didn't test this, as we've retired Windows XP completely and we hope that readers have, too. Like Windows 8.0, 8.1 can use the latest version of Hyper-V V3 as a foundation, so that other OS versions can be used on the same host hardware, with resource limitations to guests or 8.1, SDN, IPAM, and other Hyper-V features.
The Windows 8.1 UI is initially identical to Windows 8.0, but with the addition of a desktop icon that can be touched/chosen to be optionally or subsequently a resident resource more familiar to XP and Windows 7 users. We found it's also possible to boot directly to an Apps screen that allows apps to be easily chosen, although not with the same vendor topical drop-boxes that Win XP and Windows 7 might be used to. If there are many applications, the screen must be scrolled. Windows XP/7 users who have accumulated many dozens of applications might be scrolling frequently as long lists of applications can fill many screens.
We found more UI customization choices, and discovered we could make very busy combinations of Live Tiles. It's possible to insert RSS feeds into tiles where supported, allowing what we feel is an addicting amount of information available within just a handful of tiles, and the appeal of moving tiles combinations on tablets to suit differing use situations. Apps that use “traditional” windows are easier to manage, and users can now move multiple windows adjacent to each other (especially handy on multiple monitors) without having snap behavior crater their placement choices, as occurred in 8.0 and even Windows 7 editions.
By wresting control of Windows 10 mobile updates away the carriers, Microsoft continues to show that...
After Ubuntu's Mark Shuttleworth discussed publicly how important it is for the open source community...
How far does Swift soar over Objective-C? Let us count the ways
Sponsored by HP
Sponsored by Broadview Networks
Microsoft has extended the Windows 10 carrot. Later it will brandish the stick
A look ahead to next week’s Big Google Thing in San Francisco.
What can containers do for you? Here are 10 frequently asked questions about application container...
The IoT and mobile devices present special challenges that innovative vendors are trying to resolve. ...