301-sql-alwayson-md-ilb-zones DSC fails

--------------------MESSAGE FROM ADMIN, DELETE BEFORE SUBMITTING----------------------

Sorry to hear you had a bad experience with one of the templates :worried: But, in case you're just asking a question, we're happy to help. You can also check if the question might already have been asked here https://github.com/Azure/azure-quickstart-templates/issues?utf8=%E2%9C%93&q=is%3Aissue

We've created an outline of recommended sections to fill out that will help make this Pull Request awesome!

--------------------MESSAGE FROM ADMIN, DELETE BEFORE SUBMITTING----------------------

[301-sql-alwayson-md-ilb-zones](https://github.com/Azure/azure-quickstart-templates/tree/master/301-sql-alwayson-md-ilb-zones)

### Issue Details
The DSC scripts fail to execute correctly. They both fail when attempting to install the Nuget package provider during the "set-script" variable creation.

### Repro steps (*if necessary, delete otherwise*)
1. Both zip files (config-sqlao.ps1.zip and prep-sqlao.ps1.zip) in DSC fail at point during install-package for Nuget
2. Current Line: SetScript = Install-PackageProvider -Name NuGet -Force;
3. Both require modifications to the .PS1 in the zip to add the following prior to the install-packageprovider step: SetScript = '[System.Net.ServicePointManager]::SecurityProtocol = [System.Net.SecurityProtocolType]::Tls12;

The template is 301-sql-alwayson-md-ilb-zones; inspect config-sqlao.ps1.zip and prep-sqlao.ps1.zip, especially the SetScript assignment that installs NuGet. Validate both DSC scripts after the TLS 1.2 setting is included before Install-PackageProvider succeeds.

Written by the indexing model from the issue text.