Book Image

Microsoft System Center Orchestrator 2012 R2 Essentials

By : Oliveira
Book Image

Microsoft System Center Orchestrator 2012 R2 Essentials

By: Oliveira

Overview of this book

With the increasing complexity of systems in our infrastructure designs, administrating these systems has become more complex and repetitive. This ultimately translates into an inefficient environment and loss of time. System Center Orchestrator 2012 R2 is the tool that can help you regain that time again, by simplifying repetitive tasks (or complex ones) into a simple one that will require minimum intervention from you, or even none. This technology will drive you one step forward towards a more dynamic infrastructure and can also be used to make a customized Private Cloud environment setup. Starting off with the fundamentals of Orchestrator, this book helps you to learn the configuration and deployment of the Orchestrator 2012 R2 in a corporate environment to successfully deploy and mitigate real-life issues that you might encounter. You’ll learn the most used part of Orchestrator, the Runbook Designer, with all its components and mechanisms to help you efficiently design and implement your Runbooks from top to bottom. Additionally, you will also get familiarized with configuring key Integration Packs available for Orchestrator to extend its functionality and enhance the automation solution. Furthermore, you will explore the possibilities of extending and integrating Orchestrator with other parties and learn to set up core infrastructure administrative tasks that can save time and effort when automated with Orchestrator. You finally round off by gaining insights on the maintenance aspects of Orchestrator, while simultaneously covering the troubleshooting, backup, and recovery features.
Table of Contents (8 chapters)

Scalability


This question was set here on purpose due to the fact that many people still get confused about scalability and High Availability, even though both topics are quite different from one another. You'll be using High Availability to keep your service available as much as possible during time, thus improving the user experience and also the availability of your service. You'll however, implement scalability to ensure that the service is responding to the service requests (or demand) and therefore, being provided efficiently and in a timely fashion. Don't forget that scalability is used not only to add resources to a service, but also to reduce the service resources, depending on the need and the scope of that same service.

You'll usually start the Orchestrator architecture with a single server deployment to see how it goes and how you can answer the automation requests you'll find. It will be during the technology lifetime that you'll see the demand for this service increasing, making...