Microsoft Azure Automation - Creating Azure Automation Modules

This video shows how to make Azure Automation Modules that can be used to extend the standard capabilities in Microsoft Azure Automation.

Tags:

Microsoft Azure Automation Start and Stop Virtual Machines using Runbooks

This short guide will show you how to use Microsoft Azure Automation for managing the start and stop of your Microsoft Azure Virtual Machines.

This guide provides to PowerShell Automation script for Azure Automation:

  • Workflow: Start_My_Azure_VMs - Start_My_Azure_VMs.ps1 (5.26 kb) - Script for starting domain controllers first and than all the rest of the virtual machines on your Azure Subscription
  • Workflow: StopMyAzureVMs - StopMyAzureVMs.ps1 (4.97 kb) - Script for shutting down all virtual machines on your Azure Subscription

See the functionality of the scripts here:

Implementation of the scripts

Here are the steps needed to get everything up and running.

  1. Sign into the Windows Azure Portal (https://manage.windowsazure.com)
  2. Subscribe to Azure Automation Preview
  3. Create an Automation Acount (For more information: http://azure.microsoft.com/en-us/documentation/articles/automation-create-runbook-from-samples/?WT.mc_id=Blog_SC_Automation_Azure)
  4. Create the "Asset" for the Runbooks
  5. Upload the previously downloaded Automation Runbooks to the Automation Account
  6. Change the names in the Runbooks to reflect the assets and the Domain controllers

 Sign into the Windows Azure Portal and subscribe to Automation Preview 

Sign in to the Azure Portal and navigate to Automation.

 

 Create the Automation Assets

 Create a Certifcate Asset (It must be a Management Certificate) and a connection asset.

 

Connection Asset:

Certificate Asset:

 

Download the Runbooks and upload them to the Automation Account:

Download the files

Start_My_Azure_VMs.ps1 (5.26 kb)

StopMyAzureVMs.ps1 (4.97 kb)

Upload the files to the accounts

 

Change Asset names and information with the Runbooks

 

/Peter 

 

Tags:

Microsoft Windows DirectAccess Client Troubleshooting Tool

I'm pleased to announce that Microsoft have just released an awesome troubleshooting tool for DirectAccess clients called "Microsoft Windows DirectAccess Client Troubleshooting Tool".

 

Get the tool here: http://www.microsoft.com/en-us/download/details.aspx?id=41938

 

 

Tags:

Web Application Proxy - HTTP to HTTPS redirect

This article explains how to perform HTTP to HTTPS redirect for deployments of Microsoft Web Application Proxy v1.

The guidance within this article is only for companies that doesn't use a layer 7 application firewall (with the ability to perform HTTP to HTTPS redirect). Most often these firewalls will be Citrix NetScaler, F5, Palo Alto Networks, Barracuda, Fortinet, etc. If your existing firewall support HTTP to HTTP redirect always use the firewall for the redirection.

Requirements:

  • Microsoft Internet Information Service
  • URL Rewrite

Configuring HTTP to HTTPS redirect

Install "Microsoft Internet Information Service" on the "Web Application Proxy" server. It may already be installed depend on the roles that have been added. Open "IIS Manager".

Select the "Web server" and click the "Get New Web Web Application Platform".

Click "Free Download" on the right.

Find the "URL Rewrite" module, click "Add" and then click "Install".

Click "I Accept".

Click "Finish".

Close the "IIS Manager" and re-open the "IIS Manager". Click "URL Rewrite".

Click "Add Rule (s)..."

Click "Blank Rule".

Type "HTTP to HTTPS" in the "Name" textbox and in the "Pattern" textbox type "(.*)".

Navigate down to "Condition" and click "Add".

In the "Condition input" textbox type "{HTTPS}" and under "Patterns" type "^OFF$". Click "OK".

Navigate down to "Action".

Type "https://{HTTP_HOST}/{R:1}" and click "Apply".

Testing the "HTTP to HTTPS" redirect functionality:

Try accessing your site using HTTP. You should see that the page will be automatically redirected to the HTTPS site. See the network trace below for more details. 

 

Microsoft Windows 2012 R2 - Web Application Proxy support for HTTP

WAP doesn't allow for applications to be published on port 80/HTTP. It will ONLY allow external connections to HTTPS. It will be possible to use the WAP in bridge mode from HTTPS to HTTP, if your internal applications isn't configured for HTTPS internally.

IIS Application Request Routing

If you would like support for HTTP on your Web Application Proxy server you should consider using IIS Application Request Routing (ARR):

http://www.iis.net/learn/extensions/url-rewrite-module/reverse-proxy-with-url-rewrite-v2-and-application-request-routing

 

You can download the IIS add-on here:

http://www.iis.net/downloads/microsoft/application-request-routing

For more information about the Web Application Proxy. See the TechNet overview page: http://technet.microsoft.com/en-us/library/dn280944.aspx

 

 

Tags:

Microsoft Forefront Unified Access Gateway 2010 is discontinued... What now?

Microsoft Forefront Unified Access Gateway 2010 is discontinued!

The product will be removed from pricelists on the first of July 2014 and the Mainstream support will continue through April 14, 2015.

More information:

http://blogs.technet.com/b/server-cloud/archive/2013/12/17/important-changes-to-the-forefront-product-line.aspx

 What NOW?

Microsoft will continue the develope the Web Application Proxy (WAP) role within Microsoft Windows 2012 R2. Keep come and wait for great things to come.....

 

 

Tags: