SCSM & SCO – Management Pack Transfer Tool Beta 3 – Freeware!

New version out! a few bugs have been fixed, and the mappings are now kept properly! (see changelog below)

 

Download from TechNet Gallery

 

Have you ever tried to transfer some Request Offerings that contains runbooks from one environment to the other?
You will notice that is it not possible by default.

Problem is that the links to the runbooks do not work anymore since all the runbooks has been re-imported and have been assigned new IDs.

by using this easy 4 step procedure you can accomplish a successful transfer!

SNAGHTML18d506ed

 

How to (also in ReadMe):

Step 1 – Export Runbooks and Management Pack (Source Environment)

  1. Export Runbooks from SCO
  2. Export Management Pack from SCSM.

Step 2 – Create Runbook Info Pack (Source environment)

  1. Open tool on source (old) environment
  2. Edit Orchestrator Service URL
  3. Click Export Runbook Info (Source)

Step 3 – Import Runbooks (Target Environment)

  1. Open Runbook Designer
  2. Import Runbooks 

Step 4 – Update Management Pack (Target Environment)

  1. Open tool on target (new) environment
  2. Edit Orchestrator Service URL
  3. Click Update Management Pack (Target)
  4. Select location of Runbook Info Pack
  5. Select Management Pack
  6. Import Management Pack to new environment
  7. You are done!

Change Log

Beta 2 -> Beta 3:

Parameter IDs was not replaced properly, which would cause the mapping to be lost when transferring

Beta 1 -> Beta 2:
Error message was not shows properly, fixed.
Utility would fail if any runbooks from Management pack , was not found in SCO. Change behavior to skip these runbooks instead of stopping.


Comments (6):

  1. Gracjan Zawadzki says:

    Hi Jakob,
    after a delay i could finally test your new Version and i can Report, that it works like a charm!

    Many thanks for the bugfix with the Parameters (works now!) and generally the great tool – it really helps to establish a clean release process for SCSM/SCOR Workflows.

    Just a minor Annotation for a future release:
    Occasionally i wanted to update a Management pack with a runbook GUID, which runbook Name was used two times in the target orchestrator. Your tool threw an error, because it finds the runbook on the target orchestrator by runbookname.
    A fix would be – i can imagine – to search for the runbook by runbook PATH, not runbook NAME.

    Thanks again and if i find you at this years Teched in Housten you get a hug 😉

    • Thanks Gracjan! and please say hello if you meet me, I am going to speak about System Center Orchestrator 2012 – Runbook Design 101. :)

      about the fix, yes that could be a fix, but it would also lead to a new requirement of the structure of folders.
      I think i could implement a checkbox for name/path instead.

      I have thought about popping up a window and making the user select it, this is something i am working on for the next version (which also is going to be implemented inside the console). but depending on time, i might just update this stand alone tool too, to get it done.

  2. […] issue isn’t a secret, and there have been blogs discussing it, as well as third party tools designed to help ease the process. Unfortunately, those instructions and tools have been limited to […]

  3. […] issue isn’t a secret, and there have been blogs discussing it, as well as third party tools designed to help ease the process. Unfortunately, those instructions and tools have been limited […]

  4. […] issue isn’t a secret, and there have been blogs discussing it, as well as third party tools designed to help ease the process. Unfortunately, those instructions and tools have been limited […]

  5. Michael Maurer (MSFT) says:

    Worked like a charm and saved my life!
    Thank you.

    MIchael

Leave a Reply