This is with the assumption you will be installing SCOM 2016 on a Windows 2016 Server along with SQL Server 2016.
- MICROSOFT ® REPORT VIEWER 2015 RUNTIME
- Microsoft System CLR Types for SQL Server 2016
- Microsoft System CLR Types for SQL Server 2014
I am proud and happy to announce, Microsoft has awarded me their Most Valuable Professional award this October, for my contributions within the Cloud and Datacenter Management technical communities.
“Microsoft Most Valuable Professionals, or MVPs, are community leaders who’ve demonstrated an exemplary commitment to helping others get the most out of their experience with Microsoft technologies. They share their exceptional passion, real-world knowledge, and technical expertise with the community and with Microsoft.”
For more information, please visit the LINK.
To begin, I am setting up a Site-to-Site VPN (Virtual Private Network) between my home-lab and Azure. The same concept(s) can be applied to an On-Premises/Data-Center environment and enterprise grade firewalls/routers.
For starters you will need to know the IP of your home network, my IP is dynamic, so it is continuously changing. If you don’t know your public IP, go HERE to get that now. Also, I will be using the Azure Resource Manager portal, and not the classic portal, and lastly working with IPv4, not IPv6. Lastly, I am going to assume you already know a few things about Azure, Windows Server 2012R2 RRAS (Routing and Remote Access Service) and the basics of Networking.
This setup consists of 2 steps — Step 1, setting up and configuring Azure, and Step 2, setting up and configuring your Windows RRAS server. Let’s begin:
Step 1: Create a Resource Group
Step 2: Create a Virtual Network
Now we need to create a Virtual Network. This virtual network will provide IPs to machines assigned within this resource group. The IP spacing can be whatever you choose, however it is best to choose an address space different from your home-network. I have chosen a 22.214.171.124/24; my home network is a 10.10.10.0/24.The resource group will always the one you created back in Step 1.
Next I will add two subnets, one for the back-end and one for the gateway of my servers. Within your Virtual Network, select Subnets, and add as many subnets as needed.
Step 3: Create a Virtual Network Gateway
Next we will create the Virtual Network Gateway. The virtual network gateway will be responsible for sending and receiving data. Essentially the bridge between (gateway) Azure and your RRAS server/home-network.
I have kept the defaults, VPN as the Gateway type, and Route based for the VPN type. The resource group will always the one you created back in Step 1.
Depending on your environment and requirements, you will need to decide which VPN type is best for you.
Once you have entered all the properties successfully, it will take about an hour for Azure to create the Virtual Network Gateway. (Good time for lunch/a break)
Step 4: Create a Local Network Gateway
Now we need to create the local network gateway, this gateway will be configured with all of your on-premises network.
Keep in mind, the address space here MUST NOT overlap with the address space in Azure (this is why my Azure Local Network was provided a 126.96.36.199/24 address space to differentiate)
The resource group will always the one you created back in Step 1.
Step 5: Create the VPN connection
Now that all the fun stuff is done, now we need to create the VPN connection. Within the Local Network Gateway we just created (Step 4) go within the Connections, and configure a VPN connection.
Great Step 1 – Azure done! After configuring the RRAS server, we will need to come back to Azure, and connect/confirm the VPN traffic is flowing.
Step 1: Install the RRAS Windows Role
Microsoft explains this pretty well and it is pretty straight-forward, so I won’t bother, see HERE.
Step 2: Configure and Enable Routing and Remote Access
Right click on the Network Interface, and select a New Demand-dial Interface
Call it something meaningful…
Continue through the wizard, choose VPN.
Use IKEv2 Encryption here for the VPN Type (as we chose back in Step 5 within the VPN Connection configuration for Azure; they must match…duh)
Here you need to specify the Azure Public IP:
If you don’t know your Azure Public IP, go to your Virtual LAN Gateway, and see within the Essentials properties:
Leave Route IP packets on this interface enabled….
Since we are providing a PSK, credentials here don’t matter.. I just entered, Azure and left the rest blank…
Now add the Static Route for your local network, as mentioned, my network is a 10.10.10.0/24; 255.255.255.0.
Once complete, right-click on the interface we just created, and go to the Security settings. By default “Use machine certificates” will be enabled, select the preshared key for authentication option, and now enter that PSK we used in Step 5 of Azure….
Hit OK, and now let’s try to connect…..
Step 3: Test Connection on Server
Give this a few minutes, I gave it about 5 minutes, and it finally connected to Azure.
Step 4: Establish/Test Connection on Azure VPN
Go back to Azure, and within your VPN connection, hit Connect. For me, this took some time. Initially it connects, then fails, and repeats for a few minutes. I’d say after 5 minutes or so, it finally connected and stayed connected! YAY!
After all that, we now have a VPN connection established between Azure and my home network. This is evident as we can see traffic going in and out via Azure’s Gateway! Sweet!!!
After using Windows 10 on my work PCs for the last year and so, I decided it was time to upgrade my home PC. Overall Windows 10 seems great, I am able to use all my applications as I did before, and no issues with the drivers/hardware.
However, I after a few hours I really started to get annoyed with the Lock Screen activating every time I leave my desk for a few minutes. Rather than increasing that threshold, I rather disable the lock screen completely.
Here are the steps I took to disable the Windows 10 Lock Screen.
And that is it! No reboot for me was required. If you are finding the lock screen still kicking in, try a reboot.