Configuring Synchronization using Input / Mapping file?

Inherited a new Domain.  Need to migrate the users from this new domain (Domain A) to our existing domain (Domain B)

We did not use Migration Manager to create the user accounts in Domain B.

We used our own process to set those up.  Then using a mapping file into ADMT we merged attributes across from Domain A to Domain B (including passwords and SIDHistory).

Quest MM is a newly purchased product for us.  The thought was to user Quest MM's Synchronize ability to keep the objects in Domain B up to date.  Specifically when user changes password in Domain A we want it transferred to Domain B.

It would seem to me that the most straightforward way of doing this would be to use a mapping file so we can specifically say to merge this object with that object.  But not seeing how to do that.  Is it possible?

As I mentioned I am new to Quest MM so I apologize if this is a super simple question.

Thanks very much

Parents
  • If all you intend to do is synchronization, then you can take the GUIDs of your source domain objects, translate them to octet (hex) string GUID format and using PoSh, stamp them into extensionattribute15 of their target equivalents (as determined by you).  Configure your domain pairs in QMM and configure your source scope (don't select any target scope!).  Run the dirysync - when it finds these pre-stamped GUIDs, QMM will associate ("match") these object pairs into its AD LDS database.

  • Would it not be easier, to do the following:

    Domain Pair > select only SidHistory,   

    Select your Service attributes you want based on the object class

    On the sync node select your source scope Ous, set filters as needed

    On advanced options select the attributes you want to skip (not overwrite from SRC > TRG)

    Just my two cents

Reply
  • Would it not be easier, to do the following:

    Domain Pair > select only SidHistory,   

    Select your Service attributes you want based on the object class

    On the sync node select your source scope Ous, set filters as needed

    On advanced options select the attributes you want to skip (not overwrite from SRC > TRG)

    Just my two cents

Children