Hello all- I’m starting a new migration project and am currently in the assessment phase. I have more questions than answers right now but wanted to run this scenario to the forum. 3 AD forests into one target AD forest Exchange 2010 and 2013 in the source, Exchange 2016 will be deployed in the target Exchange 2013 is a RESOURCE forest to one of the source AD forests QMM 8.13 is deployed already and is used to copy source accounts and sync passwords. This has been in place for quite some time and appears to work (although I understand the tool was not designed to do this long term.) Source/Target users have been copied/matched with their target objects This is what I’m thinking: Stand up 2 new QMM consoles with a shared ADLDS instance. This will allow myself and another consultant to work both the RUM and DSA concurrently. Matching will be done with available attributes and will obviously be different than what the other DSA instance uses Match source/target AD objects but exclude the password copy. Let the other QMM instance continue to perform this function Does this make sense? Am I missing anything? I would rather not disturb the first QMM install as it keeps critical applications from breaking. I’ll need to dig in deeper on a Resource Forest Exchange migration but any feedback is appreciated. Thanks in advance, Eric

So right now, the first QMM deployment is using, let's say EA14 and EA15 on the target objects to store its data right? EA15 contains the corresponding source object GUID. In your new QMM deployment, you are going to use EA12 and EA13 for your service attributes - EA13 being the matching attribute. What I am proposing is that you use PoSh to copy the contents of EA15 to EA13 so when you run your migration sessions and/or dirsynch, QMM will immediately find the corresponding object in the target for each source object. In fact, with this in place, you can turn off all of your existing matching rules in your new deployment. Does that make sense?

This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

QMMAD already deployed to sync passwords, need to perform QMMAD/EX migrations

eric_bergstrom over 5 years ago

Hello all-

I’m starting a new migration project and am currently in the assessment phase. I have more questions than answers right now but wanted to run this scenario to the forum.

3 AD forests into one target AD forest
Exchange 2010 and 2013 in the source, Exchange 2016 will be deployed in the target
Exchange 2013 is a RESOURCE forest to one of the source AD forests
QMM 8.13 is deployed already and is used to copy source accounts and sync passwords. This has been in place for quite some time and appears to work (although I understand the tool was not designed to do this long term.) Source/Target users have been copied/matched with their target objects

This is what I’m thinking:

Stand up 2 new QMM consoles with a shared ADLDS instance. This will allow myself and another consultant to work both the RUM and DSA concurrently. Matching will be done with available attributes and will obviously be different than what the other DSA instance uses
Match source/target AD objects but exclude the password copy. Let the other QMM instance continue to perform this function

Does this make sense? Am I missing anything? I would rather not disturb the first QMM install as it keeps critical applications from breaking.

I’ll need to dig in deeper on a Resource Forest Exchange migration but any feedback is appreciated.

Thanks in advance,

Eric

Top Replies

JohnnyQuest over 5 years ago in reply to eric_bergstrom +1 suggested

So right now, the first QMM deployment is using, let's say EA14 and EA15 on the target objects to store its data right?

EA15 contains the corresponding source object GUID.

In your new QMM deployment…