1. Orchestrator 2012 Overview Markus Erlacher Technical Specialist Microsoft Switzerland Markus Erlacher Technical Specialist Microsoft Switzerland

2. Orchestrator Investments Areas Operator Trigger, Monitor &Troubleshoot Developer Application integration IT Business Manager Report & Analyze IT Pro Authoring, Debugging & Scripting

3. Activities Intelligent tasks that perform defined actions Activities Intelligent tasks that perform defined actions Orchestrator Concepts  Integration Packs –The way Opalis integrates to and executes activities against other systems and solutions  Integration Packs –The way Opalis integrates to and executes activities against other systems and solutions  Databus –The mechanism Opalis uses to publish and consume information between activities as the Runbook executes  Databus –The mechanism Opalis uses to publish and consume information between activities as the Runbook executes  Runbooks –System level workflows that execute a series of linked activities to complete a defined set of actions  Runbooks –System level workflows that execute a series of linked activities to complete a defined set of actions

5. Orchestrator System Requirements Supporting the latest platforms  Compute Resources –Min 1GB, recommended 2GB RAM –Minimum 200MB disk space –Dual Core CPU recommended  Compute Resources –Min 1GB, recommended 2GB RAM –Minimum 200MB disk space –Dual Core CPU recommended  Datastore –Local or Remote Instance –Windows or SQL authentication  Datastore –Local or Remote Instance –Windows or SQL authentication

6. Opalis to Orchestrator Migration Considerations  Rules –Export/Import from Opalis 6.3 to Orchestrator 2012 Beta –Some Opalis 6.3 activities are no longer available  Results –Most Opalis 6.3 Pipeline Mode Runbooks will work without authoring –Non-Pipeline Mode runbooks may require authoring –Opalis 6.3 non-Pipeline Mode runbooks will import as “checked out” and may required authoring to work in SCO 2012 Beta –Deprecated activities will import as unknown and require authoring –(Required only for Beta) Opalis 6.3 encrypted strings such as passwords will need to be reset after import  Resource: System Center Orchestrator 2012 Runbook Migration Guide (Beta) available on TechNet.

7. Integration Pack compatibility for RC  What works with Orchestrator 2012 RC/RTM? –All System Center IPs (updated for RC) –All 3rd-party IPs updated and released with beta  When are IPs Coming for System Center 2012? – Shortly after Orchestrator RTM – Virtual Machine Manager 2012 – Service Manager 2012 – Data Protection Manager 2012 – Configuration Manager 2012 – Operations Manager 2012

8. Migrating from Opalis 6.3 – Deprecated Activities Legacy File/FolderLegacy / No-Pipeline SupportInfrequently used / Outdated Manage Text File Create Folder Delete Folder Copy File Delete File Move File Rename File Get File Status Monitor File Monitor Folder Filter email Process email Read email Filter Exchange email Process Exchange Email Read Exchange email Wait Send Page Purge Event Log Send Pop-Up Monitor Event Log Capacity Monitor Performance Send Popup Disconnect dial-up Get dial-up status Items in Purple replaced in Foundation Activities New Foundation Activities for Text File Management and email in Orchestrator

9. The Orchestration Console  Java/JBOSS console is deprecated  New Silverlight web application  Operate Runbooks –Monitor –Initiate –Troubleshoot

10. The New Web Service  Exposes Orchestrator runtime functionality and data –Runbook definitions –Runtime data (instances, status) –Environment data (runbook servers)  Reporting and Analytics  External interface to System Center  Standards Based –RESTful web interface –Uses OData (Open Data Protocol)

11. Frequently Asked Questions  Localization / Globalization –We are globalizing for Orchestrator (run on non EN_US OS) –Localization (languages other than EN_US) will follow in a future release  Operations Manager Management Pack –YES! –Released with Orchestrator  Operations Manager Management Pack –YES! –Released with Orchestrator