- Hi everyone, welcome to another episode of OEM TV.
I'm Eric Mills, with Microsoft.
I do Windows Server marketing here.
And, in this video Ken is going to show you
what it looks like to connect up your
Windows Server Essentials server up to
an Azure Virtual Network.
There are a lot of good reasons
to do this, that Paul covered in the previous videos.
But, Ken's actually going to take you
step by step, and show you what it looks like.
As you know Windows Server Essentials
is a great first server operating system.
It has a limit of 25 users.
And Microsoft Azure, is Microsoft's public cloud.
So using the software built into
Windows Server Essentials and Azure
you can connect the two together.
And that gives you really the best of both worlds.
You get all the speed, security and snappiness
and reliability of that on prem server that you love
with unlimited expandability and access
to a ton of resources within Azure.
So there's a lot of great reasons to do this.
Ken's going to take you step by step
and show you what it looks like
to set up that site to site VPN connection,
using Windows Server Essentials
and just go through and make sure everything
is connected properly, so you know it's going to work well.
So it's a short video, there's a lot in it,
but I hope you get a lot out of this,
and are able to connect up that Windows Server Essentials
hardware server up to Azure,
and get the best of both worlds.
Hope you enjoy the video, we'll see you next time on OEM TV.
- [Ken] This video focuses on demonstrating
the integration of Windows Server 2016
Essentials edition, with Microsoft Azure Virtual Network.
With Azure Virtual Network, we have the ability to
extend our on premises server and domain
infrastructure, into the Microsoft Azure Cloud,
and run additional virtual machines there
without buying any new hardware.
Azure Virtual Networks are perfect for running
backup virtual domain controllers
replicating file shares via DFS to the cloud,
hosting line of business applications,
publishing remote apps, and more.
It can also be your first step
toward using Azure as a secondary disaster recovery site.
For this demonstration, we are running
Windows Server 2016 Essentials edition,
and a virtual machine running on a local server.
You also have the option of running
Windows 2016 Essentials, natively on a local server.
For Windows Server Essentials integration with
Microsoft Azure Virtual Network,
a Microsoft Azure 30 day trial,
or full subscription is required.
Integrating Microsoft Azure Virtual Network,
with Windows Server Essentials
starts in the same manner as configuring
other Azure services, via wizard in the
Windows Server Essentials Dashboard.
The Windows Server Essentials Dashboard
is part of Windows Server 2016 Essentials edition,
and it automatically installed as part of the
Windows installation and accessible via
the shortcut on the desktop.
So let's get started.
First step is to verify remote management is
enabled on your server, so that you are allowing
remote management features, or your wizard will fail.
You can find this setting, by opening Server Manager
so we'll go down here, and I'll open up Server Manager.
And then we're going to look at Local Server,
here on the left, and then in the right pain here
under remote management,
we see that it is currently disabled.
So we're going to go ahead and select disabled
and then we're going to select the check box
saying, enable remote management of this
server from other computers,
and then go ahead and click okay.
Now that that's enabled, our next step then
is to open up the essentials dashboard.
So we'll come down here, and I already have it here.
And what we're going to there then
is come over here on the left side, select services
and then we're going to select Azure Virtual Network
here in the middle, and then click on
integrate with Azure Virtual Network.
Now we're prompted to sign into our
Azure subscription, if we don't have one
we can click on one of the links at the bottom here
to either sign up for a free trial
or go ahead and create one,
for a new full Azure subscription.
I already set up my Azure subscription prior to this
so I'm just going ahead and click on sign in.
Go ahead and enter my Microsoft account information,
and then we're going to click in, sign in.
After successfully logging into Azure,
the next screen asks us which subscription
we want to associate with,
the Microsoft Azure Virtual Network
and here you see I have my pay as I go.
And I'm going to go ahead and click next.
In this next step, be aware that this
is only asking you the name of the remote and local networks
not to provide an IP scheme.
It will figure that out on its own.
You can also pick the location
this will determine which data center region
to use for your virtual network.
So here you see, I've already entered
Azure VN one for my Azure Virtual Network
and for my local network its Local N one
and I'm just going to come over here
and I'm going to select east US
and then we'll go ahead and click next.
This next step is where we have a choice to make
we can either let the Essentials Server handle
the site to site VPN connection
it will use the remote access RRAS feature
built into Windows Server, or we can choose
to configure the connection from our own
on premises firewall and router.
For the purposes of this demo,
I'm going to let the Windows Server
be our connection endpoint.
So we'll take the default here
and go ahead and click finish.
Here we can review the configuration
and then we'll go ahead and click close.
Notice that it automatically configured
and Azure Virtual Network addresses space
outside of the detected on premises address space.
Now we see a new plugin has been activated
for Azure VNet, as you can see
the virtual network still has a status of configuring.
While it's configuring, lets go check out
the Azure portal.
We're now logged into the Azure portal,
and we see that our virtual network has been added.
As you can see here, Azure VN one,
we also have our Azure VN one connection and our gateway.
Let's go ahead and click on Azure VN one
and we'll see more details.
Here we can see the details up at the top here,
with all the information about our subscription,
the DNS servers, address space, we also see
we have our Azure VN one gateway down below here.
Let's go ahead and click on that
and look a little bit more behind that.
Here you can see additional information
on the virtual network, public IP address, and so forth.
Now let's click on the Azure VN one group,
and we'll see all the components
that make up this virtual network.
And here we see the actual virtual network,
Azure VN one, we see the connection,
Azure VN one connection, the virtual network group gateway,
as well as the public IP address,
and the local network gateway.
So we can see that we're completely
configured up here in the Azure.
Now let's just go back and
check on our dashboard, Essentials Dashboard,
and see if the status had changed there.
So we'll switch back over to here.
And we now see, that we went from
configuring to connecting, but we also
have a lot more information here
distributed underneath the Azure VNet tab,
within the Essentials Dashboard.
So we see the local network name,
we can see the local public IP addresses,
the subscription information, and Azure gateway IP address.
So that just a little overview of
getting started with integrating
Azure Virtual Network with the Essentials Dashboard.
Thank you.