Hold the phone - stop the presses!
Microsoft did something praiseworthy. This, if it turns out not to be the dog's breakfast, was the right thing for once. They did some other thing in the late '90s, but it has been so long I forget what it was.
Microsoft has taken wraps off its latest tools for the modern data center, including a new application container tech for Windows and a micro-sized version of Windows Server that's tailored for cloud deployments. We first heard rumors of Microsoft's so-called Nano Server in March, when a leaked slide deck suggested that …
This post has been deleted by its author
This post has been deleted by its author
From what I've read on the source it's actually Windows with:
- No GUI, same as server core
- Managed via PowerShell, and WMI like current Windows
- Has it's Side-by-Side (SxS) store removed, something you can already do
- Same API's as current Windows
Sure, there's other differences, but most of what is mentioned is similar to what a good admin can already do to a 2012 R2 box.
*BSD is awesome, but it won't play anwhere near as nice with AD, GPO's, my existing management tools and scripts as Server 2012 R2 - plus a large chunk of apps / roles should also work fine.
Containerisation is new (although App-V doesn't seem off the mark), bit the rest is similar to what a competent admin can already do.
Just a heads up that App-V for Server is actualy removed from upcoming version of System Center. This was announced about the same time Microsoft started talking Docker, so my guess at that time was that Microsoft would go all-in on that technology. The document is fairly old, so there is no mention of container but points to templates as a replacement technology.
Regarding the removal of App-V for servers see: https://technet.microsoft.com/en-us/library/dn806370.aspx
Now with Hyper-V containers it seems that Microsoft if trying to use existing Windows technology to fill remainding possible use-case with containers as the reason for Hyper-V containers doesn't seem to be a large market for private cloud. My guess is that the largest use-case for Hyper-V containers will be Azure itself, ie for Cloud-services where a single deployment can take 20-30 minutes which our developers find very frustrating or WebServices (now called App) for more efficient use of resources.