Microsoft Office Tutorials and References
In Depth Information
Applying the runbook concept to Office 365
Figure 7-2 Orchestrator runbook example using the Office 365 DirSync Windows PowerShell
cmdlet as an option.
After the new Office 365 account is created, email will be sent to the Office 365
administrator to notify her that a new account was created successfully.
The runbook shown in Figure 7-2 is the basis for creating business automation in IT. This
simple example of quickly automating a mundane task can be expanded to support almost
any complex process.
Orchestrator includes standard activities, such as monitors, tasks, and other runbook
controls. The standard activities are organized into IPs. The IPs supported by Microsoft are
included with System Center. Orchestrator has been extended to include additional
functionality for third-party products and technologies to support more complex IT automation
in other IPs. Additional IPs to extend into third-party products are created by partners or
created by in-house developers using the System Center 2012 Orchestrator Software
Development Kit (SDK). Many third-party IPs are obtained separately.
INSIDE OUT Licensing System Center Integration Packs
Virtual Server hosts are licensed using System Center 2012 Datacenter licenses and
physical servers are licensed with System Center 2012 Standard. Both of these are
licensed per physical processor (not core). Both licensing models provide all the
System Center components in the suite, including Orchestrator, with all Integration Packs
supported by Microsoft. For more information, see
Search JabSto ::

Custom Search