Windows Server 2016 – Introduction to Windows Server 2016

Windows Server 2016 – Introduction to Windows Server 2016


All right, so let’s get started with Module
One. Corey Hynes, Ward Ralston.
What’s New in Windows Server 2016. Take a quick look at what is new in Windows
Server 2016. What are the major new things, the major new
categories? Just at a high level of what’s been introduced
in this version of Windows Server.
So, our agenda for this module, take a look at what customers came back and
told Microsoft. So, based on what feedback, what scenarios,
what challenges are all these new features based on.
And then we’ll look at some built-in security capabilities,
how Azure has inspired the infrastructure and coming
down from Azure to Windows Sever for on-prem deployment.
Look at some hosted, sorry, hybrid application models for
the platform and how we’re deploying applications now.
And then finally what’s the next step of recommendations for
you to go on and go ahead and learn more. So we’ll begin with what Microsoft heard from
customers. This can be broadly categorized into three
areas. Security, the Software-defined Data center
and then Application Platform.
So in terms of security, things became very prevalent as Microsoft
collected feedback. One of them, there’s an increasing number
of breaches or security incidents that are happening all
the time. And a lot of those incidents are based on
targeting identity.>>Yeah, it’s a really interesting point.
I was just looking up in preparation for this, the Identity Theft Research Center last year,
2015, 781 identified data breaches last year.
Which was the highest number since 2005 when they started
recording. And it’s not starting to be a business anymore,
like huge data bridges across medical, like blue cross,
blue shield, as well as financial sectors as well.
A lot of identity or breaches, they go unreported. Take that big issue we had,
and think about maybe the 40% that weren’t even reported.
Security which hasn’t been on the front burner for a lot of IT
pros in the past, is now becoming a hot and heavy topic.
And, as we’re gonna see Windows server 2016 really has some
innovated features that are being introduced to target these exact scenarios.
One of the other pieces of feedback was that securing
virtual environments is increasingly becoming more
and more complex. Especially as we have multi-tenant
virtual environments, where there’s this separation between
what’s often referred to as the fabric administrator, and
the service with the application administrator. And so these are two terms that you’re going
to here quite a bit, fabric administration and service administration.
Fabric administration being, you’re the guy that’s responsible for
the physical layer that everything ultimately runs o,
storage, networking and computer. And the service administrator being, you know,
you’re the guy that deploys the applications on top of that
fabric. And so securing one from the other, so
the application administrator cannot manage the fabric,
and the fabric administrator, now that he has, and this is
kind of the key one, access to the physical data center?
How do you protect the resources in that data center from the guy
that has physical access to it? We then move into the software defined data
center which is, in a lot of cases, the way that this is solved.
You know customers came back and said, well there’s a lack of integration between
all my different components.
I have many different types of hardware, many different type of vendors.
They don’t all talk together, they don’t all work together very well.
And as a result it’s hard to point operate. And in many cases, when I’m deploying your
server roles, and the server for due date.
Give me a smaller version of Windows. Give me a lighter version of Windows.
Give me a purpose built version of Windows. which is ultimately where
the new nano-server technology came from. And then finally on the application side,
we want quick integration between developers and operation.
This term devops. And that integration is kinda lacking today
and it’s making it difficult to plan for eventual migration to
public cloud. So ultimately these are the big things that
customers came back and said.
So we will take a look at the way that windows server now
begins to address those. And so with security, with infrastructure
and with the hybrid application platform, there
is many different technologies that windows server 2016 has
introduced to address these very specific customer needs.
We will take a second and kinda talk about What these different technologies
are. First off, on the security side.
A couple of major things that have happened. Number one, jumping ahead, and
look at identity with credentials. With credentials
we have the notion of something called credential guard.
Credential guard was introduced with Windows 10 And
uses a virtualization-based technology. Essentially, kind of a specialized VM to be
able to protect credentials that are stored on
the system. Ordinarily, credentials are stored in memory
on the system. If we introduce the boundary of a virtual
machine, a kind of special virtual machine It makes
it much harder for malware, malicious software,
malicious administrators to now go in and steal credentials.
Another common problem, just enough administration, just in time administration.
You know, how often have, in the past for example,
you take an administrator and they come in and
they need to perform a task so you make them safe domain admin
and then you forget to remove them.>>or you accidentally delete that OU or-
>>Right.>>don’t>>Yeah.
>>I mean like they become an administrator and
they’re an administrator for ever.>>That’s right.
>>I know you’ve done a on security audits on companies.
>>Yep.>>And you go in and you look and you see well there’s 40 people in
the main admins group. And you find out well it was because three
years ago they had to do something that required it and we just
forgot to.>>And they’re walking around the entire network
with that token all day.>>Yeah.>>Yeah.
>>So with Windows server 2016, there’s two new security technologies that have been
introduced, that allow you to take the capability of an administrator
and reduce it from all they need to do, you know
all privileges all the time->>Right.>>to just what they need for
a limited period of time>>Right. So you become an admin for
the next three hours to accomplish your task and
after that your credentials automatically lose that right.
So, very key for long term protection. To take away the notion of I forgot to
remove it from the security group. I forgot to take away those permissions.
They all become time based>>Then, what, in addition to that.
Protecting the OS regardless of where it is. Whether it’s in a private cloud or a public
cloud. And taking some of the knowledge that has
been learned on Azure and bringing that down to Windows Server 2016.
But you may be surprised to learn but people attack Azure.
I’m sure it’s under constant attack.>>They attack Azure all the time, and so
Microsoft developed some very special technology to basically
model what they consider effective or correct behavior of
operating systems. And if you find something that doesn’t match
correct behavior, take an action to block it.
And the result are things like Control flow guard.
And enhancements to Windows Defender. And then advance code integrity policies.
>>Yeah.>>To make sure that, for example,
a machine boots, it boots using the right kernel code.
>>Right. [CROSSTALK]>>You use the term
rootkit a lot.>>Yep.>>There has been a rootkit
applied that modifies the kernel somehow to get
below the hyper visor at that very, very low level.
And these were all things developed, tested, tried, and
proven in Azure. And now have been brought down to Windows
server.>>And I would add a quick note on this Windows
defender for those of you who are gonna download technical
preview five. As Cory mentioned this is about as close you
get to the release before the actual release comes
out. Being feature complete this is an excellent
time to download and start kicking the tires.
On the Windows Defender side and technical preview five,
this is enabled by default Defender and you actually have to install through the add
remove features, the actual console to actually turn it on
and off if you want. Just heads up, installed not by default.
>>So great tip, thanks. So then we move on to what there is for virtual
machines. Well now we introduce
this notion of what is called a shielded VM. In previous versions we had the notion of
a Bitlocker encrypted VM.
So I could take my VM and I could use Bitlocker technology and
I could fully encrypt that VM. The idea is that if you get physical access
to the machine And you steal the VHD, you can now, it’s as
if you walked into the data center and pulled the hard drive.
You have physical access, you own it. Well, we wanna change that, right?
If you have physical access maybe you don’t own it.
Maybe you can’t go in and crack the database and
get the passwords. So bit locker protected VMs.
Use bit locker encryption to make sure that VHD files
are encrypted to the same level bit locker you can’t go in,
steal the HD crack it open, get the passwords.>>What we’re doing here with the technology.
I think you’re gonna see this theme a lot in Server 2016.
Virtualizing network. Virtualizing storage.
We’ve been virtualizing hardware for years now.
And the technology that really makes the shielded VM happen
is actually virtualizing that Trusted Platform Module chip
that’s normally associated on the hardware. We can now bring that into the VM and
hence leverage BitLocker to encrypt it.>>So you may ask the question, well,
how do I deploy BitLocker across an entire enterprise?
How do I take that to mass scale? And the answer is, there’s a new component
within Windows Server called the Host Guardian Service.
It’s a complete infrastructure that you deploy. You actually deploy a separate forest to hold
your keys. You create a cross to that forest and
you create what’s known as a protective fabric so
that every Hyper-V host can get it’s BitLocker keys from
a central location, deploy what are called shielded VMs which
are encrypted VMs. They can move from host to host to host with
the same flexibility, As a normal virtual machine on
a normal fabric, but while maintaining that same level of encryption,
okay? And then finally we have generation 2 VMs.
A generation 2 VMs are not necessarily a new thing But
it’s a Generation 2 VM that enables things like
BitLocker encryption, TPMs, and this Host Guardian Service to work properly.
>>This is an important thing, though. Again, when I think about that Windows Server
08 administrator. And when I think about any data center, I
can’t imagine them all being 2012 R2 without a little bit
of ’08 in there. So for you ’08 administrators out there, for
you guys with ’08 in your data center, pay attention to the Gen
2 VMs as you look to upgrade to the next version. Cuz there’s a lot of capabilities that get
unlocked when you switch to, what is it UEFI?
>>UEFI.>>UEFI, so->>Instead of a PC based BIOS-
>>That’s right.>>Or an SMBM, the old American megatran that
was on->>Phoenix Bios?
>>Yeah, it’s that one.>>[LAUGH]>>Every CRT
monitor ever turned on. It’s a UEFI BIOS.
>>That’s right.>>It’s a much more intelligent BIOS.
So take a look at this slide real quick. We see that we’ve kinda moved the bar a little
bit to where if you were a server administrator
and the servers were locked in a physical building
you didn’t have access to, you could have managed the
server but not manage any of the fabric and the platform.
As we move to VMs, which is kind of where we are today, if you’re
the server administrator, you can now manage the storage,
the network, the backups, everything, right? Because it’s all files, it’s not physical.
It’s files. With Shielded, we can now be a VM administrator,
so I can manage the fabric but not have access
to the sever, the storage, the network, or the backup.
So we’re kind of moving that bar to make sure that
you as an administrator have access to only what you need
only when you need it. And then, there’s a lot of additional built-in
security features.
We kind of have sort of a plethora here of what
all these different sort of features are. You see things like Secure Boot.
You see things like Nano Server. You see things like Containers.
Code integrity checks. There’s a lot of work being done to make sure
that the knowledge and the security from running Azure has been
brought down, rolled into Windows server 2016 so you have
all that same knowledge, intelligence and capability,
just the smaller package you can deploy on your own.
>>Yeah. If I was looking, again, I’m looking at it through that ’08 lens, I
would definitely, personally, be paying attention to the shielded
virtual machines as well as the HyperV containers.
I mean, to me, those are gonna be a couple features that really
make moving off of ’08 into 2016 very compelling.>>So, our next sorta theme as we talk about
what’s called Azure-inspired infrastructure, as Microsoft
is deploying Azure, Azure is, I think you made a comment to me
a couple days ago, the world’s largest supercomputer.
>>Let me jump on my little soap box here about Azure, because I
get personally a little excited when I talk about it or
when I tell people about it. Azure is commodity hardware,
literally just deployed across the planet. We have over 100 data centers offer Azure
services in over 140 countries, and we run 200 of our own services
on there. Think of XBox, Office, Outlook, Hotmail, Office
365. I mean, and in these data centers, we have
over a million servers around the world that we have gotten
excellent at managing ever since we opened our first data
center in 1989. And since then, have spent over $15 billion
in investing in data center and how to highly automate the
compute network and storage across these million computers.
So when we say we’re taking some of our learnings that we have
brought from these 200 plus services that Microsoft
runs highly reliably down into the data center, while at
the same time we have 20 years of momentum that we are putting
behind all the technologies into Windows Server. We really have, in my opinion,
Windows Server 2016 is the best of both worlds. Not only do best of breed on premises, but
also start dipping your toe in the Cloud if you
haven’t already. These Azure inspired features, or infrastructure
as they like to call it, is gonna more increasingly
allow you to seamlessly bring your On-Premises up into Azure.
Okay, I’m off my soapbox.>>So as we think about that, the biggest
thing, when you start moving to hyperscale’s obviously
downtime. You have to find ways to prevent downtime,
to mitigate downtime, to eliminate downtime.
And what Microsoft has done with Windows Sever 2016 is
given you the ability to virtualize virtually anything.
No pun intended. And eliminate all those needs for downtime
that come from the not so obvious scenarios such as patches
and reboots, such as cluster upgrades, right?
Which was a big pain point going from 2008 to 2012 R2, especially
for those that haven’t invested in heavily virtualization.
Because you had to incur downtime to that. And then things like, I need more networks,
I need more disk, I need more storage, I need more memory.
Yes, we have dynamic memory, but now we have things like add and
remove hard drives, disks, and memory. And we’ll take a look at some of that as we
move into the module.>>And not just Microsoft technology.
I think that’s an important point.>>Yes.>>We are, we offer that same
type of potential for Linux operating systems, too.
>>Absolutely.>>[CROSSTALK] add, move.>>There’s a, many, a number of years ago
there was kind of a trend towards Linux, and it kind of, I don’t
want to say died down, but it kind of got quiet
for a while. And now there’s a big,
Linux is kind of in the forefront of everybody’s mind
again to the point that Windows 10 has a bash shell on it now.
>>Microsoft is truly embracing the Linux world and
the Linux community, making it a first-class citizen both in Azure,
also on Windows Server, and embracing technologies that
traditionally come from a Linux world, like containers, the docker engine, for example.
So, for example, as we mentioned, rolling cluster upgrades, Linux hardware.
And then, in terms of placing your workloads, there’s some new network technology we’ll
talk about. The network controller, which is a new component
of Windows Server 2016 that was inspired directly
from Azure, to centrally manage all elements of your physical
networks, which is routers, top of rack switches, load
balancers. And then, also virtualized component,
like virtual switches. And then, introducing the notion of distributed
firewall. The distributed firewall’s a term that it’s
a little, it’s a little vague.
We’ll explain it more when we talk about the networking.
But it’s this idea that if you have an application, and
that application requires a certain port to be open, and
that application runs in a virtual machine, as that virtual machine moves around the data
center, as you move it from host to host or from data
center to data center, the rules that ensure it has connectivity,
such as open firewalls, open ports, follow the workload.
And if that means we’ve gotta reconfigure switches, we’ve
gotta reconfigure routers, we need to create firewall rules.
All that happens automatically as that workload moves around.
And you as the administrator don’t need to remember that,
hey, if we put the sales app in data center two, someone’s
got to remember to open up the firewall or it’s not gonna work.
That all now happens automatically as part of the network controller.
>>Would you say it’s fair to say that with network controller
you really are creating a network fabric within your organization?
>>I would, but I wouldn’t put it that way. With the network controller, you’re now, via
software and policy, you’re able to fully manage that network
fabric.>>Okay, that’s a better way to look at it
>>You don’t have to understand how to configure the CISCO switch versus the
Dell switch versus the HP switch.
>>Right.>>You can simply, say, have a policy, and the network controller
can now go into all those different switches if,
assuming they support industry standard configuration protocols-
>>Right.>>And make those configuration changes for
you.>>Cool.
>>So then we take a look at storage.>>[INAUDIBLE]>>Honestly, it truly is.
I come from a storage background, I love storage.>>I love the way you light up when you talk
about it.>>I know, it gets like->>It’s like watching
paint dry for most people, but->>For me,
it’s like watching bits move on a disc. So most IT pros in the Windows ecosystem
is familiar with storage spaces. It’s Windows, I say this very, very loosely.
It’s Window’s built-in version of RAID. So, everyone knows what RAID is.
RAID 5, RAID 10, etc. And then with Windows they had software RAID
and Windows NT, and Windows 2000 and so on.
>>Yeah.>>And then with Windows Server 2008, or was it R2?
One of them, they introduced storage spaces, which was sort of an upgraded version.
Now we have distributed storage spaces. And this is kind of fun one.
It enables you to have multiple commodity servers with no shared
storage configured as a single storage pool. So it’s a RAID array that spans physical servers.
So think, with RAID you have five discs, and your parity’s on one disc.
With storage space direct, you have five servers. You parity someone’s server.
Now, in reality, it’s not that. But conceptually, its kinda like that.
And we’ll see an example of how to build a hyper-converged
cluster, which is a cluster that runs VMs with
full shared storage and parity, but without any networking, without any shared
storage [INAUDIBLE] I just said it uses shared storage,
and I’m saying it doesn’t use shared storage.>>Yeah, I don’t wanna->>You’ll get the
point when you see it.
>>I don’t wanna get too ahead of ourselves, cuz I know we have
other modules we’re gonna go a lot deeper on this.
But for those people maybe just picking up one module here,
I think you mentioned to me the other day there is this
transformation going on, even with the IT professional, right?
The IT professional used to have a SAN administrator, used to have a security administrator,
used to have a domain administrator. And in a weird way, not to overuse a term,
but they’re also being hyper-converged into one person now.
>>Yes.>>Because the capabilities and the product make it so easy, you don’t need
a a guy with a degree from MIT to set up a fiber channel, right?
You just get a box with a bunch of discs, commodity hardware which, by the way, which
is what Azure uses. Right off the shelf, x86 infrastructure.
And now, with the promise of the technology to do these complex
tasks for you The role the IT administrator is becoming
more complex with a lot more responsibility.>>I use the term of fabric administrator
and the workload administrator.
The fabric administrator does networking, virtualization and
storage. In the past if you were doing storage, you
typically, let’s say you deploy a very high storage rate.
You bought it from one of these big companies, EMC,
Dell, any one of those big companies. You had to learn how to use it, it was complex,
there was a lot of work to it, and it’s very specialized
because essentially a SAN has its own little operating system.
You gotta know how to configure it. Well, you can now take all that knowledge
and that work and Windows does it for you.
So the skills you use to create a file share are now the skills
you use to deploy a san. And so those kinds of tasks are becoming accessible
to the mainstream Windows administrator.
The result is, it’s simpler and easier, and we’ll see that as we’re going through.
So a lot of these capabilities that come from what we refer to
as Azure-inspired infrastructure. And you can see a pretty long list here.
The things that Microsoft does in Azure, we wanna enable those to run On-Prim and make
the transition from Azure to On-Prim and from On-Prim to
Azure. Simple simple, seamless and easy.
>>Yeah and again, I always like to look at these lists again
from that if I were an 08 or other type of previous
version of Windows, I would say for me, network controller
stands out as a feature to really pay attention to.
>>And I always have to give a shout out to PowerShell.
As you think about the new role of the IT pro or
the IT administrator, there’s less and less you’re gonna be able to do without PowerShell.
And I think a good example to see is if you wanna put group
policy doesn’t work on Nano server. If you want to do any type of policy, you
need to use desire stick configuration through PowerShell.
Just become the tool that you need to know more and
more about as we get into more versions of Windows.
>>Absolutely. So take a look hybrid application platforms
and what that means.
There’s two major things we’ll talk about in here.
Nano Server as a deployment option. So the idea would be that if you want to deploy
a workload, you deploy the minimum amount of windows as
possible, and the minimum amount of application infrastructure
as possible so that your application is as light
and portable as possible.
And so Nano Server was developed for that reason.
Nano Server is a version of Windows that is below sever
core. It’s a less than server core.
>>20 times less. [LAUGH]>>It’s very, very lightweight.
You deploy the entire thing in a couple hundred meg.
You can’t really modify it once it’s been deployed.
>>Right.>>You kinda pick the roles and features you
want. You build it and you set it up.
And it boots in seconds, uses very little memory.
And it’s just enough to run applications. And one of the applications it’s very good
at running at is the container technology.
Which is container technology’s an application deployment model
that’s less than a virtual machine but more than running,
say, multiple web apps on a single machine. So it gives you a level of isolation and
a level of portability that’s been fairly common.
It’s very common in cloud providers that are out there and
existing today, and so a lot of developers are looking to use
container technology to circumvent some of the problems
you have when you go from a developer workstation to
a testing staging server to a deployment production server and
all the configuration changes that can happen. I deploy the application but we’re missing
a file, we need to deploy the file.
Containers solve, if used properly, solve many, many,
many of those issues. And so we have containers, which are traditional,
which are kind of the new minimal workload. We have traditional VM workloads that can
run on Server Core. And then we have full applications that require
the GUI that can run on RDS. So you have all these different tiers that
can, you can choose from as an application developer,
and how you want to deploy it.
Windows has traditionally been the big one, virtual machine
server core introduced the one in the middle, and now we have Nano Server and containers,
which is the smallest, simplest, most light weight version.
>>I mean, a little nerd point here. Jeffrey Snover’s blog,
just the other day was talking about how Nano Server doesn’t
use the MSI-installer technology anymore. It uses the same technology to install that
APPX, I believe?>>Yeah.
>>It’s the same technology that’s used to install things
from the Microsoft Store. So really, kinda flip it on its head how we
even look at the install of Windows Server.
>>Yeah, everything is looked at very differently. So we mentioned containers, right?
What is a container? A container is a boundary within the system
that is less overhead than a virtual machine, and
provides essentially a read only view of the operating system
within a mechanism to capture changes as well. But a read only view of the operating system
where you can actually run an application.
So I can run multiple copies of the same application in multiple
containers on the same host with minimal overhead. If you compare this to virtual machines because
for most IT administrators, they get confused
between virtual machines and containers and they hear the
term Hyper-V Container and Windows Server Container,
virtual machine and what really is the difference between them.
A Hyper-V container and a Windows Server container are both containers they’re just different
deployment models. A Hyper-V container will use the hypervisor
to create additional isolation whereas a Windows Server container
will not use the hypervisor for the additional level of
isolation. On both cases it’s still just a container,
and a container is a boundary in which you can run an application.
A good analogy for if you’re an existing IT pro administrator,
a good analogy is AppV or Server AppV. When you spin up an application in AppV,
it creates a little virtual bubble the application runs in,
where it doesn’t conflict with anything else. And it’s got its own view of the files and
the operating system, and it can contain its own configuration.
But you start the application, it’s in a virtualized bubble,
when you’re done with the application, the bubble goes away.
A container works in a similar conceptual manner.
You start a container, it’s isolated, you stop a container it goes away.
You don’t back up containers you, don’t live migrate containers, you don’t save
containers. A container is an instantiated version of
a container image, much like an AppV application is an instantiated
version of AppV.>>I’ve tried to explain containers to a few
people and until you explain the way that AppV acts as
similarly the same way as a container.
So it’s when their kinda, that was like my aha moment.
You know it’s like okay I get it now.>>And then you say, well,
how does it relate to a virtual machine? A virtual machine has the entire operating
system, its own copy of the operating system.
>>Yeah.>>A container doesn’t.
A container uses the host’s copy of the operating system for
operating system functions. And so we got a whole module and
we talk about the application platform that deal with
containers a little bit later on. And so you can see there’s a lot of things
that represent this new sort of hybrid application platform.
Containers, full integration with Docker.>>Mm-hm.
>>Docker is sort of an industry standard container engine and
container set of commands for manipulating and
managing containers.>>Yeah.
>>And Microsoft has full docker support on Windows Server
20 staff writer. You can create containers with docker commands
or with the PowerShell provider.
PowShell desired stake configuration rather than
scripting the flow of making configuration changes,
you merely describe the desired end state. And the system figures out how to make those
changes for you. If you wanna surface start with PowerShell
DSC, you say make the surface start and PowerShell takes care
of the work for you. You don’t have to query the state of the service.
>>Right. It’s a push pull.
>>If stop start, if not ignore.>>One of the interesting things about the
desire state configuration>>And
it was also in Jeffrey Snover’s blog that, you know,
increasingly Microsoft is going to start to move away from
group policy, especially when it relates to servers.
I mean, it’s great for fine configuration. There’s a bunch of new group policy management
tools put in just for Windows 10.
But as we’re seeing with Nano Server, it needs to be managed through desired state
configuration with PowerShell and as the server world evolves,
that’s gonna be increasingly become the case.>>Well, ultimately if you think a group policy,
a group policy requires that you be in a domain on the land.
>>Yeah. [CROSSTALK]>>Ultimately.
>>That’s right.>>The fundamental environment or
climate for group policy is I’ve got a domain.>>Yep.
>>I’ve got a local area network, and I’ve got that,
I’m inside the firewall on the land type connectivity.>>Yeah.
>>Increasingly, that’s not the case for how companies are deploying workloads.
>>Right.>>For example, if you’re a company today,
and you’re starting up right now,
you’re probably putting your application on the cloud.
You’re probably embracing bring your own device. So rather than domain-joined machines,
you have personal machines. If they’re not domain-joined, you can’t use
group policy. So moving away from this traditional notion
of domain managed, group policy managed machines into
servers that are managed through declarative technology
like PowerShell, and then policy based access to resources as opposed
to policy-based configuration systems.>>Yeah, so again if I were looking at this
through the 08 lens, I would say PowerShell, desired state
configuration and, of course, containers and
Nano are definitely the ones to keep an eye on.
>>PowerShell’s always gonna be the theme. Nano Server certainly is the big one.
So just kinda recap where we are with Windows Server 2016.
A lot of built in security capabilities. A lot focused on identity.
Taking the infrastructure that’s been powering Azure bringing
that down to Windows Server 2016, building out the software defined data center,
and making those capabilities richer and richer.
So as you build your data center, infrastructure or
deploying workloads, you need less and less specialized skill to manage it.
You can define policies and let the system worry about
the differences between the actual hardware. And then moving towards a hybrid application
model with support for containers, support from nanoserver, DSC,
and many other things.
So, with that, that’s kind of our first look at Windows server
2016 and what’s new. We encourage you to go ahead and download
the technical preview, technical preview five as of today which is,
when we’re recording this, it’s just become available.
Check out the Windows server blog. There’s a really good video series on the
blog that was published not too long ago which is the top
ten new features in Windows Server 2016.
So Matt McSpirit, one of the technical evangelists here at
Microsoft sat down with a number of folks in the product groups
and kinda look at what are the top ten best features?
A lot of them we would’ve talked about right in here.
You can see some interviews. They talked about in little more
depth of what these features are and why they’re good.
So with that, that’s our quick look at Windows Server 2016 and
we’ll see you in the next module.>>Stay tuned for the next modules.

About the author

Comments

Leave a Reply

Your email address will not be published. Required fields are marked *