• State Not Answered
  • Replies 3 replies
  • Subscribers 22 subscribers
  • Views 587 views
  • Users 0 members are here
Options
Related

Switch from QMMAD to ODMAD or BT AD Pro?

vinodhkumar s
6 months ago

Hello Team,

We require your assistance and suggestions for the following migration scenario.

In Phase I of our plan, we successfully migrated a few AD resources to the Target Forest Domain using the Quest Migration Manager for AD tool.

For Phase II of the migration plan, which covers the rest of the AD resources, we are considering switching to either On Demand Migration for AD (ODMAD) or BT AD Pro. Please note that there are dependencies on the Groups Mapping due to ADLDS Database for both Phase I and II migrations.

We would appreciate your suggestions on whether it's feasible to switch from QMMAD to ODMAD or BT AD Pro in the middle of the migrations.

Thank you.

  • 0 5 months ago

    Yes, it is feasible to switch from QMMAD to ODMAD or BT AD Pro in the middle of your migration. However, there are a few things you need to keep in mind:

    • Group Mapping: You mentioned that there are dependencies on Group Mapping due to ADLDS Database for both Phase I and II migrations. You will need to make sure that the Group Mapping is compatible between the two tools you are switching to.
    • Data Integrity: It is important to verify that the data migrated in Phase I is still consistent after switching to a new tool. You can do this by comparing the data in the Source and Target Forest Domains.
    • Downtime: There will be some downtime associated with switching from one tool to another. You will need to plan for this downtime and communicate it to your users.

    Here are some specific steps you can take to switch from QMMAD to ODMAD or BT AD Pro in the middle of your migration:

    1. Export the data from QMMAD. This will include the user accounts, groups, and other objects that you have migrated so far.
    2. Import the data into ODMAD or BT AD Pro.
    3. Verify that the data is consistent. You can do this by comparing the data in the Source and Target Forest Domains.
    4. Update the Group Mapping. Make sure that the Group Mapping is compatible between the two tools you are switching to.
    5. Cut over to ODMAD or BT AD Pro. This will involve changing the DNS records for your domain to point to the new Active Directory servers.

    If you are not comfortable switching from one tool to another in the middle of your migration, you may want to consider using a migration service provider. A migration service provider can help you plan and execute your migration, and they can also help you troubleshoot any problems that you encounter.

  • 0 5 months ago

     makes some good points.

    Not mentioned is the the over-arching concern of process re-engineering, re-validation and documentation updates.

    Depending on how much time you have already invested (and time remaining if there is a completion deadline), you need to ask yourself and / or the project stakeholders can you afford to go through the above steps with a new toolset?

  • 0 5 months ago

    Switching from QMMAD to ODMAD or BT AD Pro in the middle of your migration is feasible, but it requires careful planning and execution to ensure a smooth transition. Here are some factors to consider:

    Group Mapping Dependencies: Since both ODMAD and BT AD Pro rely on the ADLDS database for group mapping, you'll need to ensure compatibility between the two tools. This may involve exporting the group mapping data from QMMAD and importing it into the new tool.

    Data Synchronization: You'll need to synchronize the existing migrated data between the QMMAD environment and the new tool. This may involve exporting the migrated objects from QMMAD and importing them into ODMAD or BT AD Pro.

    User Cutover: Once the data synchronization is complete, you'll need to plan a user cutover to switch over to the new tool. This involves updating user profiles and group memberships to reflect the new environment.

    Testing and Validation: Thorough testing and validation are crucial throughout the migration process. This includes verifying that all objects have been migrated correctly, that group memberships are accurate, and that users can access their resources without any issues.

    Technical Expertise: Switching tools mid-migration requires a good understanding of both QMMAD and the new tool you choose. Consider engaging experienced IT professionals or consultants to assist with the transition.

    Documentation: Maintain clear and comprehensive documentation throughout the migration process. This will aid in troubleshooting and future reference.

    In summary, switching from QMMAD to ODMAD or BT AD Pro in the middle koows of your echat migration book is possible, but it requires careful planning, data synchronization, user cutover, testing, and technical expertise. Proper documentation will also be crucial for a successful transition.