Book Image

Microsoft System Center 2016 Orchestrator Cookbook - Second Edition

By : Michael Seidl, Steve Beaumont, Samuel Erskine (EUR), Andreas Baumgarten

Book Image

Microsoft System Center 2016 Orchestrator Cookbook - Second Edition

By: Michael Seidl, Steve Beaumont, Samuel Erskine (EUR), Andreas Baumgarten

Overview of this book

With Microsoft System Center 2016 Orchestrator Cookbook, you will start by learning how to efficiently install and secure System Center Orchestrator. You will then learn how you can create configuration files for SCO 2016. After initial installation and configuration, you will soon be planning and creating functional and fault-tolerant System Center runbooks to automate daily tasks and routine operations. Next you will delve into runbooks; you will learn how to create powerful and advanced runbooks such as Building your Runbook without a Dead End. You will also learn to create simple and advanced runbooks for your daily tasks. Towards the end of the book, you will learn to use SCO for other interesting tasks and also learn to maintain and perform SCO health checks. By the end of the book, you will be able to automate your administrative tasks successfully with SCO.

Preface

What this book covers

What you need for this book

Who this book is for

Reader feedback

Customer support

Free Chapter

Unpacking System Center 2016 Orchestrator

Unpacking System Center 2016 Orchestrator

Understanding the Orchestrator architecture

Planning the Orchestrator deployment

Installing a single server deployment

Making the Orchestrator environment highly available

Deploying an additional Runbook Server

The Initial Configuration of SCO 2016

The Initial Configuration of SCO 2016

Deploying an additional Runbook Designer

Registering an SCO Integration Pack

Deploying the IP to Designers and Runbook Servers

The initial Integration Pack configuration

Creating and maintaining a security model for Orchestrator

Planning and Creating Runbooks

Planning and Creating Runbooks

Initial steps to consider before creating a Runbook

Making Runbook scenarios automation ready

Documenting Runbook designs

Understanding the Orchestrator scenario building blocks

Runbook Designer standards and primer

Creating a Runbook

Building Advanced Runbooks

Building Advanced Runbooks

Creating a child Runbook

Building a looping Runbook

Implementing logging in your Runbook

Implementing error handling in your Runbooks

Making your Runbooks highly available

Simple Runbooks for Your Daily Tasks

Simple Runbooks for Your Daily Tasks

Active Directory – Deleting inactive computer accounts

SCOM – Activating maintenance mode for a server

SCVMM – Removing an attached ISO from a VM

ConfigMgr – Automating the update Installation process

SCSM – Raising priority, if an affected user is a VIP

Advanced Runbooks for Your Daily Tasks

Advanced Runbooks for Your Daily Tasks

Active Directory – Sending an email to users if their password will expire soon

SCOM – Advanced alerting with SCO

Doing More with Orchestrator

Doing More with Orchestrator

Starting an SCO Runbook using PowerShell

Starting an SCO Runbook with the Orchestration Console

Using SCOOSP to provide self service with SCO

Maintaining and health checking SCO

Customer Reviews

5 star

0

4 star

0

3 star

0

2 star

0

1 star

0

Registering an SCO Integration Pack

Microsoft System Center 2016 Orchestrator (SCO) automation is driven by process automation components.

These process automation components are similar in concept to a physical toolbox. In a toolbox, you typically have different types of tools, which enable you to build what you desire. In the context of SCO, these tools are known as Activities.

Activities fall into two main categories:

Built-in Standard Activities: These are the default activity categories available to you in the Runbook Designer. The standard activities on their own provide you with a set of components to create very powerful Runbooks.
Integration Pack Activities: Integration Pack Activities are provided either by Microsoft, the community, solution integration organizations, or are custom created by using the Orchestrator Integration Pack Toolkit. These activities provide...