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.
Table of Contents (8 chapters)

Conventions

In this book, you will find a number of text styles that distinguish between different kinds of information. Here are some examples of these styles and an explanation of their meaning. Code words in text, database table names, folder names, filenames, file extensions, path names, dummy URLs, user input, and Twitter handles are shown as follows: "Create a subfolder called 1.3.1-Delete inactive Computer Accounts." A block of code is set as follows:

 $POSTBody = @"
<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<entry xmlns:d="http://schemas.microsoft.com/ado/2007/
08/dataservices"
xmlns:m="http://schemas.microsoft.com/ado/2007/
08/dataservices/metadata" xmlns="http://www.w3.org/2005/Atom">
<content type="application/xml">
<m:properties>
<d:RunbookId type="Edm.Guid">{$($RunbookID)}</d:RunbookId>

When we wish to draw your attention to a particular part of a code block, the relevant lines or items are set in bold:

 $POSTBody = @"
<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<entry xmlns:d="http://schemas.microsoft.com/ado/2007/
08/dataservices"
xmlns:m="http://schemas.microsoft.com/ado/2007/
08/dataservices/metadata" xmlns="http://www.w3.org/2005/Atom">
<content type="application/xml">
<m:properties>
<d:RunbookId type="Edm.Guid">{$($RunbookID)}</d:RunbookId>

Any command-line input or output is written as follows:

 $RetreivedGUID = GetSCOProperty $XML 
$RunbookInputProperty "In" "Id"

New terms and important words are shown in bold. Words that you see on the screen, for example, in menus or dialog boxes, appear in the text like this: "Right click on Runbook Designers, and select Deploy new Runbook Designer"

Warnings or important notes appear like this.
Tips and tricks appear like this.