Are you looking to get grips with automation and scripting?

Join Thomas Maurer, Microsoft Datacenter and Cloud Management MVP, who will use this webinar to show you how to achieve automation in your Hyper-V environments, even if you don’t have SCVMM.

Remember, any task you have to do more than once, should be automated. Bring some sanity to your virtual environment by adding some scripting and automation know-how to your toolbox.

We’re live on Thursday, 10^th December 2015 at 10am EST / 4PM CET (30-45mins + live Q&A!)

The post WEBINAR: Scripting & Automation in Hyper-V without SCVMM appeared first on Tech-Coffee.

• SMA Web Services – This is a REST Endpoint used by the Windows Azure Pack to connect to the SMA service.
• SMA RunBook Workers – This is the process that runs jobs;
• SQL Database – Store runbooks, jobs, and activities.

Architecture

The below schema describes how each components interact. The Windows Azure Pack is connected via HTTP protocol to the Web Service. This last is connected to the SQL database and so can submit requests and return results to the Windows Azure Pack. Regarding Runbook Workers, they run jobs described in the runbooks.

SMA can be deployed highly available as described in the below schema:

Multiple SMA web service can be deployed behind a load balancer as an F5 appliance. The SMA database supports AlwaysOn to ensure the database high availability. To finish multiple Runbook Worker can be deployed.

Requirements

The requirements described below come from this TechNet topic.

Hardware

Software

Security

SMA Installation

Web services installation

The first service to install is the SMA web service. To install the web service, mount the media of Orchestrator. Once you have run the SetupOrchestrator.exe, click on Web Service in the Service Management part:

Next click on install.

Next enter the registration information and the product key.

Then accept the license terms.

If you have not installed all the prerequisites as me, you can run the below PowerShell script:

Install-WindowsFeature Web-Server, Web-Basic-Auth, Web-Windows-Auth, Web-Url-Auth, Web-Asp-Net45, NET-Framework-Core, Net-Framework-45-Core, NET-WCF-HTTP-Activation45

Once all prerequisites are installed, click on next J.

Next specify database information as below:

Then specify the security groups and the credentials for the Application Pool.

Next specify the Web Service port number and the server certificate. I use a certificate generated by my PKI from the certificate template Web Server.

After that, specify the installation folder:

Then configure the CEIP and the Microsoft Update setting.

And to finish, click on install.

Runbook worker installation

Now that the Web Service is installed, we run again the SetupOrchestrator.exe  on the Orchestrator media to install a Runbook Worker.

On the next screen click on Install.

Specify the production registration information and click on next.

Then accept the license terms and click on next.

Once your prerequisites are validated, click on next.

Specify database server information. These information should be the same that you have specified in the web service installation.

Next specify a service account and click on next.

Choose an installation folder and click on next.

Then configure the CEIP and the Microsoft Update setting.

To run the installation, click on install J.

Connect Windows Azure Pack to SMA

Now that all components of SMA are installed, connect to the Windows Azure Pack administration portal and navigate to Automation.

Enter the service URL and the user name. Usually the service URL is the name of the server where you have installed the web service.

When the Windows Azure Pack is connected to the SMA web service, you should have something similar as below screenshot:

Now you can use SMA to automate your Private CloudJ.

The post Windows Azure Pack – SMA installation appeared first on Tech-Coffee.