At MMS keynote on Tuesday, Brad Anderson announced that System Center Orchestrator is the official name for what we have been referring to previously as Opalis vNext.
Orchestrator which will be part of the System Center 2012 releases will provide a number of new features, functions and capabilities in addition to being rebranded and the codebase being moved into the Microsoft organization.
Here’s a summary level list:
- IT Pro – Authoring, Debugging & Scripting
- The Opalis product will be rebranded to System Center Orchestrator. We’e working very hard to ensure that your existing investments in Opalis are maintained
- A new PowerShell provider to allow Orchestrator to be integrated into scripts and provide a mechanism for remote execution of runbooks
- Operator – Trigger, Monitor &Troubleshoot
- A new silverlight based dynamic web console to provide an easy way to start, monitor and investigate runbooks
- Developer – Application integration
- A new rich OData based web service that exposes Orchestrator functionality and information in a standards based way
- IT Business Manager – Report & Analyze
- A new mechanism for connecting your existing reporting investments to Orchestrator to extract, report and analyze what’s happening inside Orchestrator.
In addition to the above investment areas, we’re also completing a number of ‘housekeeping’ functions:
- A new Installer experience
- An Orchestrator Management Pack for Operations Manager
- Globalization of the Orchestrator release (Localization will follow in a future release)
- Updated versions of the Integration Packs, both for System Center as well as a number of the 3rd Party IP’s