How to connect up your Windows Server Essentials server up to an Azure Virtual Network.
“Theres lots” of good reasons to do this, step by step, and prove you what it consider this to be. As you know Windows Server Essentials is a great first server operating system. It has a limit of 25 consumers. And Microsoft Azure, is Microsoft’s public cloud. So using the application is integrated 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 velocity, security and snappiness and reliability of that on prem server that you love with limitless expandability and access to a ton of available resources within Azure. So there’s a lot of great grounds to do this. I am going to take you step by step and evidence you what it looks like to set up that website to site VPN connection, applying 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 post, 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 this post. – This video focuses on demonstrating the incorporation of Windows Server 2016 Essentials edition, with Microsoft Azure Virtual Network. With Azure Virtual Network, we have the ability to extend our on propositions 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 repeating file shares via DFS to the cloud, hosting line of business applications, writing remote apps, and more. It can also be your first step toward use Azure as a secondary cataclysm improvement website. For this post, we are running Windows Server 2016 Essentials edition, and a virtual machine moving on a local server.
You likewise have the option of installing Windows 2016 Essentials, natively on a neighbourhood server. For Windows Server Essentials integration with Microsoft Azure Virtual Network, a Microsoft Azure 30 day trial, or full subscription is asked. 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 an example 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 permitted on your server, so that you are allowing remote handling aspects, or your wizard will flunk. You can find this setting, by opening Server Manager so we’ll go down here, and I’ll opening up policy Server Manager. And then we’re going to look at Local Server, here on the left, and then in the privilege pain here under remote control, we see that it is currently disabled.
So we’re going to go ahead and select incapacitated and then we’re going to select the check box saying, enable remote management of this server from other computers, and then moving forward and click okay.
- Now that that’s allowed, our next gradation then is to open up the essential points 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, hand-picked 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 asked 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 account or go ahead and establish 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. I enter my Microsoft account information, and then we’re going to click in, sign in.
- After successfully logging into Azure, the following screen asks us which subscription we are to be able to associate with, the Microsoft Azure Virtual Network (VN) and here you insure I have my pay as I go account. And I’m going to go ahead and click next. In this next setting, be aware that this is only asking you the names of the remote and local networks not to offer an IP scheme. It will figure that out on its own. You can also pick the location this will be decided by which data centre region to use for your virtual network. So here you chose, I’ve already chosen 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 is moving forward and click next.
- This next step is where we have a choice to construct we can either tell the Essentials Server to connect the website to site VPN connection, it will use the remote access RRAS that is integrated into Windows Server, or we can choose to configure the connection from our own on premises firewall and router. For the practical implementation of this demo, I’m going to let the Windows Server be our connection endpoint. So we’ll take the default here and is moving forward and click finish.
- Here we can refresh the configuration and then we’ll go ahead and click close. Notice that it automatically configured and Azure Virtual Network addresses address space. Now we determine a brand-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, tells 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 , we also have our Azure VN one connection and our gateway. Let’s go ahead and click on Azure VN 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 experience we have our Azure VN on gateway down below here.
- Let’s go ahead and click on that and seem 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 group, and we’ll encounter all the components that make up this virtual network. And here we encounter the actual virtual network, Azure VN one, we envision 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 realise, that we started from configuring to connecting, but we also have a lot more information here shared underneath the Azure VNet tab, within the Essentials Dashboard. So we envision the local area network identify, we can see the local public IP addresses, the subscription intelligence, and Azure gateway IP address. So that exactly a little overview of getting started with integrating Azure Virtual Network with the Essentials Dashboard. Thank you . .