Create local user to bypass password policy

Problem: You are trying to create an IIS account for basic authentication, however the domain password policy does not allow you to create such an insecure password. When trying to edit the local group policy setting of "Password must meet complexity requirements" you run into the issue where the setting is greyed out.

Solution: The solution is to perform the following commands from an elevated command prompt. secedit /export /cfg C:\new.cfg Edit new.cfg and change line “PasswordComplexity = 1″ to “PasswordComplexity = 0″ and if needed any of the other complexity settings such as  "MinimumPasswordLength = 0" secedit /configure /db %windir%\security\new.sdb /cfg C:\new.cfg /areas SECURITYPOLICY Perform the user setup as normal.

Use GPUpdate /force to have the original group policy take effect again.

Experience Azure Operations Management Suite (OMS)

Microsoft has setup a nice little lab where you can use a HTML 5 emulator or guide to view specific functions in OMS including:

Insight and AnalyticsGuided HTML5 labSecurity and ComplianceGuided HTML5 labAutomation and ControlGuided overview PowerpointProtection and RecoveryGuided overview Powerpoint
Check it out here

VSTS error - PackageDeploymentFailed - using WebDeploy

VSTS reports the following error when trying to use WebDeploy on a release.

2017-06-12T15:00:29.1546658Z [command]C:\vstsagent\A5\_work\_tasks\IISWebAppDeploymentOnMachineGroup_1b46XXXX-6725-4b6d-accd-886174c09bba\0.0.18\MSDeploy3.6\msdeploy.exe -verb:sync -source:package='C:\vstsagent\A5\_work\r1\a\XXXWebsite Redesign-ASP.NET (PREVIEW)-CI\drop\' -dest:auto -setParam:name='IIS Web Application Name',value='dev/dev' -enableRule:DoNotDeleteRule
2017-06-12T15:00:29.2151195Z ##[warning]Can\'t find loc string for key: PackageDeploymentFailed
2017-06-12T15:00:29.2151195Z ##[error]PackageDeploymentFailed
2017-06-12T15:00:29.2151195Z ##[error]Error: C:\vstsagent\A5\_work\_tasks\IISWebAppDeploymentOnMachineGroup_1b467810-6725-4b6d-accd-886174c09bba\0.0.18\MSDeploy3.6\msdeploy.exe failed with return code: 2148734720
2017-06-12T15:00:29.2284444Z ##[section]Finishing: IIS Web App Deploy (Preview)
When running the command specified in the logs directly …

Software Management with PowerShell DSC and Chocolatey

Here is an extremely helpful slidedeck on an introduction to Chocolatey and an overview for how it integrates with Powershell Desired State Config (DSC).
Software Management with PowerShell DSC and Chocolatey
This is from the Powershell Summit 2017, held in Bellevue, Washington. Credit goes to Rob Reynolds - Founder at Chocolatey Software.

Microsoft Azure Storage Explorer - Cannot find blob storage

Microsoft Azure Storage Explorer is a great utility for navigating all of the storage available in Azure. You can easily leverage the tool to upload, download or manage snapshots for storage resources across all of your subscriptions.

You can download the tool here:

I ran into an issue when looking for a set of SQLBackups. I tried to use the option on the sidebar to search by prefix but I was still unable to find the SQLBackups:

Taking a second look and actually reading, I noticed, that unlike everything else in the Windows world, this search was case sensitive. By changing the "search by prefix" I entered to match the case sensitivity, I was able to find the SQL backup that I needed.

Visual Studio Team Services - Powershell Azure Build errors

Visual studio team service builds error out with the following error:
The term 'Remove-AzureStorageContainer' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.

This error is caused by the deployment agent having an old version of the Azure powershell module installed.

The solution was to update the module using the powershell one-get module and to install the current version from the powershell gallery. Use the command "install-module azure -force" if an existing version is installed.

Once that is completed, as the helpful build error below points out:
Neither the Azure module nor the AzureRM module was found. If the module was recently installed, retry after restarting the VSTS task agent. You must restart the services named VSO Agent (your agent name here).