Want to run powershell script for the users I migrate via quest

Hi,

After I migrate User from Source to Target domain I want to run a powershell script by making use of the workflow.Will powershell take action only on the users Quest migrates? is their any parameter or functionality in Quest for the same. Also, same while migrating devices.In old QMM , there was option to run powershell script from RUM on devices.

  • Did you figure this out yet? I want / need to do the same. Can't seem to find any details or example scripts? In QMM days, it was easy as the scripts ran from the QMM server already on Prem. My initial thinking was that the script would be pushed down to the Agent server in either the source or target AD and run from there, but does not seem to be the case; at least I didn't see anything on the Agent server.

  •  and  In ODM Directory Sync, you have the ability to run PowerShell scripts as part of the workflow. This scripts will run against the ODM "Environment" in which they are associated in the "Scripts" settings. The script will run as the service account configured in the ODMAD Directory Sync agent installation, so that account will need the rights to perform any actions in the script. 

    Important Note: The PowerShell script ran from within a ODM DirSync workflow has no concept of what objects are "in-scope" of the workflow, so the user scope will need to be set independently within any PowerShell script to ensure only intended users are actioned.

    Steps:

    • The first step is to go to the ODM DirSync portal
    • Click on the hamburger menu
    • Select Scripts
    • Add a script, associate with the Environment
    • Navigate to Workflow s
    • Select Workflow
    • Click Settings
    • Click Sync Workflow
    • Find Run PowerShell Scripts in the available Workflow Steps
    • Drag and drop the Run PowerShell Scripts block to the desired location in the workflow steps on the right
    • Click Save

    Regards,

    Trevor Taegder
    Migration Center Engineer

    Quest | Migration Assurance Center

  • I know how / where to add scripts. I'm just trying to understand where the scripts run from and an example script. If for example, I need to get pretty granular on where objects will be created based on the Source domain OU they are in. Target OUs will not be recreated based on Source OU structure so objects would be created under the default target OUs specified. I have a script (using hash table for OU mapping) to do this locally but need to understand how to run this from within Quest. Just looking for a basic example of a script connecting back to either Source or Target domain (Local - Local sync) as there's got to be a line of sight to the DCs for this to work in my opinion.

    Or is there a better way to do this custom OU Mapping?