Sergey Nivens - Fotolia
Administrators looking for new System Center 2016 features in Orchestrator and Service Management Automation are in luck.
Orchestrator provides workflow management in the data center. Service Management Automation (SMA) automates the resource provisioning process via System Center. Both support the creation, test, refinement and use of runbook-based process management and automation. Windows Server 2016 offers several enhancements in those areas, mostly related to PowerShell.
In System Center 2016, both Orchestrator and SMA use the Windows Management Framework to create runbooks with PowerShell scripts. This native scripting feature helps reduce the preprocessing often needed to run scripts in earlier versions of Orchestrator or SMA.
System Center Orchestrator 2016 and SMA can use the PowerShell Integrated Scripting Environment (ISE) plug-in to help create and test runbooks. For example, ISE offers helpful coding features such as syntax highlighting and allows administrators to select portions of a script to test during the development process.
Administrators can install various System Center Orchestrator 2016 components, including its management server, runbook server, web service and runbook designer, and enable network discovery to automatically recognize systems in the environment. IT can install these components on one machine or distribute them across multiple servers.
To try out the streamlined scripting in Service Management Automation and Orchestrator, download System Center 2016 for a 180-day evaluation.
When to consider a Windows Server 2016 upgrade
PowerShell users get upgrade with WMF 5.1
Admins should know these PowerShell scripts
Dig Deeper on Windows administration tools
Related Q&A from Stephen J. Bigelow
Understand and work around one of the more common Docker for Windows errors -- permissions for shared volumes -- to read, write and execute to the ... Continue Reading
IT administrators should familiarize themselves with the benefits and limitations of using nested virtualization to run containers in VMs before ... Continue Reading
Many issues cause VMs to become unresponsive, including invoking particular tasks, such as snapshots or migrations, resource configuration and ... Continue Reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.