Deploying Windows Service Management Automation (PART 1)

Deploying Windows Service Management Automation (PART 2)

Integrating Windows Service Management Automation (PART 3)

Introduction

What is Windows Service Management Automation (SMA)? 

Before describing « SMA », you need to know what is Windows Azure Pack (WAP). The goal of Windows Azure Pack is to create your private cloud in your own Datacenter using Hyper-V and Virtual Machine Manager (VMM). Users, DevOps or Syadmins can use a similar web portal as Azure to deploy VMs on Demand. If you don’t want (or you can’t) to push your datas in Microsoft Azure, use the WAP!

Below is one of my favorite schema about WAP architecture:

azurepack

WAP use the Service Provider Framework (SPF) for interfacing the Service Management API to VMM.
WAP includes:

  • 1 admin portal
  • 1 self-service portal
  • Active Directory Authentication with ADFS

Below is a screenshot from the self-service portal:

azurepack2

What is Service Management Automation?

SMA is integrated into Admin Azure Pack Portal and allows you to automate some tasks such as: Deploying VMs, Creating Checkpoint, Monitoring your deployments, … SMA use runbooks based on PowerShell Workflow.

Below is a SMA screenshot from admin portal:

sm3

More informations about SMA and WAP: https://technet.microsoft.com/en-us/library/dn469260(v=sc.12).aspx

Be careful: Azure Pack is not Azure Stack! Another article will be published about Azure Stack.

Deployment Part1

In brief:

  • SMA is an Orchestrator component. (So you must have the orchestrator ISO)
  • SMA is integrated into the WAP Admin portal
  • PowerShell can be used to manage SMA

In this blog post, we will install SMA. Assuming you have the following installed & configured components:

  • Orchestrator 2012 R2
  • Windows Azure Pack

Let’s start!

First, run the orchestrator setup and select « Web Services ». The Service Management Automation web service is a REST based service that exposes Service Management resources and relationships through Open Data Protocol (OData). You can access the Web Services using Windows PowerShell.

2016-09-28-15_22_56-sor01-connexion-bureau-a-distance

Click « Install »

2016-09-27-16_20_52-sor01-connexion-bureau-a-distance

Enter your Name, Organization Name and the Product Key:

sma-3

Read & Accept the license

sma-4

You will probably get the following errors. So go to the next step:

sma-5

Go to Server Manager and install « Basic Authentication » and « URL Authorization »:

sma6

Re-run the prerequisites:

sma-7

Specify your database server name and the database name:

sma-8

Configure access rights:

sma-10

Choose the port number and use a certificate (drop down the list to select your certificate)

sma-11

Specify the installation folder:

sma-12

Next, next and finish

sma-16

Web services are installed. You can check if the DB is created:

sma-18

Open a web browser and type the following URL: https://yourserver:9090/00000000-0000-0000-0000-000000000000/

sma3

 

Next part will describe how to install Runbook Worker, the PowerShell Module and how to integrate SMA into Admin Azure Portal.

 

Thanks for reading! You can follow me on Twitter @PrigentNico.

About Nicolas 192 Articles
I work as a System Engineer, based in Switzerland with a primary focus on Microsoft technologies. I have 7 years experience in administering Windows Servers. . I am a Microsoft MVP for Cloud & Datacenter Management. I also received the PowerShell Hero 2016 award by PowerShell.0rg. And finally, I am "MCSA: Windows Server 2012" and "Administering & Deploying SCCM" certified.