Book Overview & Buying
Table Of Contents
Feedback & Rating

Microsoft System Center 2016 Orchestrator Cookbook

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

5 (1)

Buy this Book

Microsoft System Center 2016 Orchestrator Cookbook

5 (1)

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

Buy this Book

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

Conventions

Reader feedback

Customer support

Free Chapter

Unpacking System Center 2016 Orchestrator

Introduction

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

Introduction

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

Introduction

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

Introduction

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

Introduction

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

Introduction

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

SCOM – Advanced alerting with SCO

Doing More with Orchestrator

Introduction

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 (1)

5 star

100%

4 star

3 star

2 star

1 star

Creating a child Runbook

Creating a child Runbook is one of the most essential tasks in SCO. Technically, there is no difference between normal Runbooks and a child Runbook.

A child Runbook is a Runbook with initialized data and often return data and is mostly used for tasks that are needed by multiple Runbooks.

For example, a Runbook, which is adding a user in the AD Group can be a child Runbook, as this task is often used by different Runbooks.

So, it makes sense to build one Runbook, such as a module PowerShell programming, with all the features you need, instead of building the task in each Runbook separately.

See this chart for a better understanding of how a child Runbooks works: