Parse Orchestrator Export Tool

I have just release a new tool called Parse Orchestrator Export available on the community codeplex site ( There are two files for download, the GUI tool and a general administration .dll it references, you will need both (just put them in the same folder)

What does this tool do?

That’s a great question! It looks at a Orchestrator Export File – point it to one and click ‘Parse’

Now you can see all of the cool things that were included in your export and some additional features are shown

Sanitize Export

This will modify the export file and remove all of the unreferenced global settings and configurations (as you can see above this export has a lot of them)

Now that the clean is done lets re-parse!

Turn On / Off Object Specific Logging

This will turn on or off the Object Specific Logging flag for all runbooks

Turn On / Off Generic Logging

This will turn on or off the Generic Logging flag for all runbooks


Posted in Infrastructure, Workflow
10 comments on “Parse Orchestrator Export Tool
  1. […] from Robert Hearn when he left Microsoft. I blogged earlier about its default functionality ( and will use this post to expand a bit on the new functionality. The project is available at […]

  2. Manuel says:

    Great tool, thank you.
    Some things I noticed, though (with the export tool v1., dll v1.0.0.0, released Apr 11, 2013; exported on SCORCH 2012 SP1).
    – When the program window is resized to more than its initial width (about 800), the vertical scroll bar of the “Folders and Policies” treeview disappears (the whole treeview is basically pulled “below” the “Properties” and “Objects” fields).
    – It would be very helpful if the columns in the “Objects” listview would keep their size when selecting a different runbook; currently, the columns always return to their default column size.
    – When “Alternate Runbook Users” is selected, the “Objects” listview isn’t updated/cleared and will still display the properties of the last object visited.

    Alternate Runbook Users:
    – If the runbook user account is picked from Global Variables or from Published Data, the “raw” names (“\`d.T.~Ed/{}.\`d.T.~Ed/”, “\`d.T.~Vb/{}\`d.T.~Vb/”) are displayed as domain/user names; ideally, variable account names would be resolved to “.” or “” in the treeview, and the “Objects” viewlist would display the respective Names, Types (“Published Data”, “Global Variable”) and GUIDs used in the account settings.

    Global Configurations:
    – If more than one configuration is present for an IP, “Global Configurations” seems to pick up only the first one listed in the export file.
    – It doesn’t pick up Configurations for some of the more common integration packs, for example “System Center Configuration Manager 2007”, “System Center Operations Manager 2007 R2” (and at least one of the more uncommon ones, “Standard Logging” from


  3. Manuel says:

    That was fast, thank you.

    Just noticed that in my earlier post, some information for “Alternate Runbook Users:” I put between “” was swallowed.
    For the sake of completeness, that should have been
    Alternate Runbook Users:
    – When the alternate user account is picked from Global Variables or from Published Data, the “raw” names (“\`d.T.~Ed/{[Activity GUID]}.[PD Name]\`d.T.~Ed/”, “\`d.T.~Vb/{[Variable GUID]}\`d.T.~Vb/”) are displayed as domain/user names; ideally, variable account names would be resolved to “[Activity Name].[PD Name]” or “[Global Variable Name]” in the treeview, and the “Objects” viewlist would display the respective Names, Types (“Published Data”, “Global Variable”) and GUIDs used in the account settings.

    Some feedback to the changes:
    – The vertical scroll bar now remains in place when resizing the window.

    Global Configurations:
    – Multiple configurations for the same IP are now listed.
    – Configurations for SCCM, SCOM, “Standard Logging” are now picked up; the former two as “NativeConfig:{[GUID]}” (can’t be resolved in the export, I know), the latter with its name.


  4. Mark says:

    When I attempt to parse an export file I get an error. Here is the output from the error:
    See the end of this message for details on invoking
    just-in-time (JIT) debugging instead of this dialog box.

    ************** Exception Text **************
    System.NullReferenceException: Object reference not set to an instance of an object.
    at ParseOrchestratorExport.Form1.setupTreeRoots(TreeNode treeRoot, TreeNode& RunbookNode, TreeNode& VariablesTreeNode, TreeNode& SchedulesTreeNode, TreeNode& CountersTreeNode, TreeNode& ComputerGroupsTreeNode, TreeNode& GlobalConfigurationsNode, TreeNode& ASCUsersTreeNode)
    at ParseOrchestratorExport.Form1.reloadTree()
    at ParseOrchestratorExport.Form1.button2_Click(Object sender, EventArgs e)
    at System.Windows.Forms.Control.OnClick(EventArgs e)
    at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
    at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
    at System.Windows.Forms.Control.WndProc(Message& m)
    at System.Windows.Forms.ButtonBase.WndProc(Message& m)
    at System.Windows.Forms.Button.WndProc(Message& m)
    at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
    at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

    ************** Loaded Assemblies **************
    Assembly Version:
    Win32 Version: 2.0.50727.5472 (Win7SP1GDR.050727-5400)
    CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v2.0.50727/mscorlib.dll
    Assembly Version:
    Win32 Version:
    CodeBase: file:///C:/Users/markb/Desktop/Parse%20Orchestrator%20Export/ParseOrchestratorExport.exe
    Assembly Version:
    Win32 Version: 2.0.50727.5468 (Win7SP1GDR.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/
    Assembly Version:
    Win32 Version: 2.0.50727.5467 (Win7SP1GDR.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/
    Assembly Version:
    Win32 Version: 2.0.50727.5467 (Win7SP1GDR.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/
    Assembly Version:
    Win32 Version: 2.0.50727.5476 (Win7SP1GDR.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Xml/

    ************** JIT Debugging **************
    To enable just-in-time (JIT) debugging, the .config file for this
    application or computer (machine.config) must have the
    jitDebugging value set in the section.
    The application must also be compiled with debugging

    For example:

    When JIT debugging is enabled, any unhandled exception
    will be sent to the JIT debugger registered on the computer
    rather than be handled by this dialog box.



  5. Daniel says:

    Hey Ryan,

    Really looking forward to using this tool, but I haven’t been able to get it to work without an error.

    I’ve downloaded the latest version of both the ParseOrchestratorExport.exe and Orchestrator.Administration.dll into the same directory, then launched the ParseOrchestratorExport.exe.

    After browsing to my ois_export file, I parse, then sanitize and get this error msg:
    “Unhandled exception has occurred in your application. If you click Continue, the application will ignore this error and attempt to continue………

    Object reference not set to an instance of an object.”

    This error occurs no matter what folder or runbook I attempt to sanitize.

    I’ve tried this on Windows 7 and Windows 2012 R2, does the tool run only on specific OS/Platform?

    Any help would be greatly appreciated!!


    • randorfer says:


      Did you download the .dll files as well as the tool? Check to see if everything is ‘unblocked’ — go to the properties and see if anything has ‘block’ set because it was downloaded from the internet. The Orchestrator.Administration.dll file needs to be in the same location as the parse tool. Let me know if this doesn’t work.


      • Daniel says:


        Thx for the quick response! I’ll try your suggestions, but was able to get it to work after reading your answer to another commenter with the same question. I rexported my runbooks to include all options (counters, variables, schedules, globals) and it worked.

        Thx again and LOVE the tool. Keep up the great work!

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: