Hello,
I'm working on a Proof of Concept for an AD Migration. During the migration we have to start multiple times a AD Migration session, based on an 'dynamic' importfile.
We would like to schedule the AD Migration Session (commandline or Powershell), or Create/start/manage a Migration session by powershell
We use Quest AD Migration 8.14
Is this possible ?
Thanks in advance,
Sander
You might want to replan your migrations process. Normally I migration all in scope objects in the first weeks of the projects. Once I have all inscope object migrated or merged, I allow the directory sync to keep the current. So there is really not a reason to run session on demand.
The anwser is it can be done via Quest professional services. Please contact your sales rep.
Hi Jeff,
The migration will run for at least one year. New users in the source domain have to be renamed to another name (name,cn,samaccountname and UPN) in the target domain.
This is not possible by a synchronization of the paired domains, and a new Migration session is required, see https://support.quest.com/migration-manager-for-ad/kb/69882/error-0xe1000010-attribute-175a3f38-a46c-496c-943d-9ddeac7726cc-_objectrdn-not-found-in-object-
Therefor I would like to start/schedule this Migration task automatically.
From a process point of view though, as Jeff suggested you can perform your initial "mass" (all users) migration session and adjust the accounts as you say and then, perform daily / weekly (whatever makes sense) sessions to "pick-up" any net-new users. The dirsync (when properly configured with attribute skips) will keep all of the other attributes (passwords, group memberships etc.) up to date for you.
Hi John,
Therefore my question: Is it possible to start the AD migration session (daily/weekly) automatically, by a commandline/Powershell/others.. ?
The required importfile for the rename action is created by a scheduled Powershell script.
Hi John,
Therefore my question: Is it possible to start the AD migration session (daily/weekly) automatically, by a commandline/Powershell/others.. ?
The required importfile for the rename action is created by a scheduled Powershell script.
Fair enough. A supported automation interface like you describe does not exist. However, another option would be to have the dirsynch (DSA) create the objects for you. You would need to configure it allow object creates. This would also require a custom XML Add-In to support the transformations (rename etc.) that you require. You need to get a quote from Quest Professional Services (Custom Dev) for that.
