Previous Post in Series: Part 1: Azure Stack Deployment Guide (Updated)
Welcome back folks. So…with all the work we’ve done thus far, we’re now in a position to deploy the MSSQL RP. This will allow you to provide SQL databases as a service, so PaaS!
Here’s a list of what we’re going to do in this section of the guide:
Continue reading “Part 2: Deploy MSSQL Resource Provider into ASDK”
Previous Post in Series: Part 1: Deploy Azure Stack Single Node POC
19/07/2017: UPDATED for the Azure Stack Dev Kit
Welcome back folks. In the last guide we deployed a single node Azure Stack POC and uploaded a Server 2016 Image to the gallery. In part 2 we’re going to deploy both the MSSQL and MySQL resource providers. Microsoft have done a great job of making this a fairly straightforward endeavour so I don’t expect this to be too meaty a post
Here’s a high level list of what we’ll be going over:
Continue reading “Part 2: Deploy MSSQL and MySQL as PaaS on Azure Stack”
Hello again folks, I just recently put up a guide on deploying WAP and SPF and thought this little addition would be useful.
The first thing I wanted to do when I spun up my first WAP server was to have the admin and tenant sites respond over port 443 and change the URLs to something more friendly. I was very happy to find out that this is something that can be done without “too” much effort
The first thing you’ll want to do is decide on the URLs for each of the sites listed in the table below. Once that decision has been made, you’ll want to add them into DNS, for the purposes of this guide I’m doing this all internally but the theory is the same for making these sites available to the internet. Continue reading “Set Custom URLs for WAP Admin and Tenant Sites”
Hello again folks, if you’ve been following this blog since it launched, you’ll be aware that I’ve been writing a series I’m calling the Server 2016 Features Series. Part of this series is exposing the Shielded VM capability to the Windows Azure Pack portal. I’m working on the assumption that some people may never have deployed WAP before, and so decided to put a guide together for it. As this guide isn’t technically part of the above series, I’ll also be including the components required for a successful minimal viable deployment of WAP Express (single server). Here is a high level of the tasks covered:
- Deploy and configure a SQL Server 2016 VM
- Deploy and configure a Service Provider Foundation Server
- Deploy and configure a Windows Azure Pack Server
Continue reading “Deploy Windows Azure Pack (Express) Step-by-Step”
As I was about to start deploying a SQL server for use by VMM, I was reminded about how SQL is licensed when it’s for the purpose of hosting System Center databases. If you’re licensing your Hyper-V hosts with Cloud Platform Datacentre licenses, any SQL licences required for your System Center DBs are already covered.
With that in mind, I decided that if this was actually a production build, I’d build out a 2 node SQL AlwaysON cluster that uses Availability Groups for hosting all System Center databases.
The only database we will place here (during the guide) is the VMM database. For reasons I’ll explain a little further on, I had to go with the Enterprise edition of SQL, be aware though that only SQL Standard licensing is covered when using the Cloud Platform Datacentre licensing model for System Center. Continue reading “Part 1: Deploy SQL Server 2016 Availability Groups”