Runbook Authoring Gareth James Senior Consultant SIM313 Agenda Workflow development and change General Structure Naming Link Logic Global Objects Error handling Advanced Techniques Routing Engine Logging IP ID: 650501
Download Presentation The PPT/PDF document "Best Practices for Orchestrator" is the property of its rightful owner. Permission is granted to download and print the materials on this web site for personal, non-commercial use only, and to display it on your personal computer provided you do not modify the materials and that you retain all copyright notices contained in the materials. By downloading content from our website, you accept the terms of this agreement.
Slide1
Best Practices for Orchestrator Runbook Authoring
Gareth JamesSenior Consultant
SIM313Slide2
Agenda
Workflow development and changeGeneral StructureNamingLink LogicGlobal Objects
Error handling
Advanced Techniques (Routing Engine, Logging IP)
ReferencesSlide3
Runbook Development and Change
Treat Orchestrator Runbooks like codeDev
/Test/Production environments
Check-in/Check-out facility
Versioning
Changes to production
Runbooks
by import ONLY
Change ControlSlide4
demo Gareth James
Senior ConsultantMicrosoft Services
Runbook
AuthoringSlide5
References/Resources
Runbook Authoring best practiseshttp://blogs.technet.com/b/charlesjoy/archive/2011/06/13/ois-6-3-advanced-workflow-amp-best-practice-video-tutorial.aspx
Policy Authoring downloadable examples
http://blogs.technet.com/b/opalis/archive/2010/05/07/workflow-authoring-examples-and-samples.aspx
Oplais
Policy to Orchestrator
Runbook
Migration
http://technet.microsoft.com/en-us/library/hh420350.aspx
Codeplex
External Logging tool
http://orchestrator.codeplex.com/releases/view/76097
Error trapping in
Powershell
http://technet.microsoft.com/en-sg/library/2009.01.windowspowershell.aspxSlide6
© 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the
part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.