none
Importing multiple domains within one run profile - keep running import even if domain cannot be reached RRS feed

  • Question

  • All,

    I am facing an issue and spent time on research and discussions with my colleagues. All feedback is more or less the one I was feared of. So - you are my last hope :)

    Current setup:
    -    Run profile “DI” on AD-MA contains 60 steps (screenshot attached)
    -    Each step is related to a single domain within forest
    -   Currently domains are decommissioned step-by-step, as all user are migrated to a single root-domain
    -    We are not always informed that a domain was shut-down
    ==>    RESULT: In case that a domain could not be reached, either caused by a temporary issue or based on being decommissioned run profile is stopped immediately with error “no-start-connection” and all following steps are skipped. Means, in case that in step 2 of the profile domain cannot be reached following 58 domains are not imported.

    Question: I spend some time on checking for a solution on that, not yet successfully. Does anyone of you have an idea how to solve it? My idea, and I assume this is somehow possible, is to define error handling in FIM that enforces him to proceed with next step within run profile instead of skipping all following steps.

    Worst case work-around would be to defined a DI-run profile with a single step for each single domain – means 60 DI-run profiles :(

    NOTE: As the schedule for the migration is not yet finally agreed I would assume a time frame in years - so it is not a short term issue.

    Expecting worst case reply but not yet given up,

    Daniel

    Screenshot:

    Screenshot_Run-Profile_DI

    Thursday, July 3, 2014 9:01 AM

Answers

  • Hello,

    beside the worst case reply i only have one idea.

    You could check domain connection by script, an if domain is not available, manupilate the AgentConfig XML file with a script, that removes the run profile information from it.

    After that you have to find a way to automate GUI work, i know there are some tools around but can't give a example, to initiate the update management agent function.

    Im not quite sure that this will work, just a stupid idea ;)

    Think the better way is to have seperate run profiles for each domain.

    Regards
    Peter


    Peter Stapf - ExpertCircle GmbH - My blog: JustIDM.wordpress.com

    Thursday, July 3, 2014 10:32 AM
  • Since domains are being decomissioned anyway I would stick to per-domain run profile scenario, as you'll need to modify the configuration regularly to remove obsolete information.

    Also, you might be interested to look at IM Sequencer, which simplifies complex run profile scenarios.

    http://www.traxionsolutions.com/imsequencer/

    Tuesday, July 15, 2014 11:20 AM

All replies

  • Hello,

    beside the worst case reply i only have one idea.

    You could check domain connection by script, an if domain is not available, manupilate the AgentConfig XML file with a script, that removes the run profile information from it.

    After that you have to find a way to automate GUI work, i know there are some tools around but can't give a example, to initiate the update management agent function.

    Im not quite sure that this will work, just a stupid idea ;)

    Think the better way is to have seperate run profiles for each domain.

    Regards
    Peter


    Peter Stapf - ExpertCircle GmbH - My blog: JustIDM.wordpress.com

    Thursday, July 3, 2014 10:32 AM
  • Thanks for reply - I will check this solution. and compare it to "run profil per domain".
    Tuesday, July 8, 2014 8:54 AM
  • Since domains are being decomissioned anyway I would stick to per-domain run profile scenario, as you'll need to modify the configuration regularly to remove obsolete information.

    Also, you might be interested to look at IM Sequencer, which simplifies complex run profile scenarios.

    http://www.traxionsolutions.com/imsequencer/

    Tuesday, July 15, 2014 11:20 AM