RE: ADMT v2.0 Database corruption question

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: Bob Qin [MSFT] (bobqin_at_online.microsoft.com)
Date: 08/20/04

  • Next message: Feng Mao: "RE: Domain List could not point to new domain automatically" 
    Date: Fri, 20 Aug 2004 07:43:40 GMT

    Hi Pere,

    What is the database you renamed? Do you mean Protar.mdb file?

    Please retore the original database. Now create a new group (named
    newgroup) with a new user (Newuser) in the source domain, then migrate the
    group and user as test. If the problem still persists, please attach the
    latest two migration logs in your post. You can find the logs in \Active
    Directory Migration Tool\Logs folder.

    Thank you,

    Regards,
    Bob Qin
    Microsoft Online Partner Support

    Get Secure! - www.microsoft.com/security

    ====================================================
    When responding to posts, please "Reply to Group" via your newsreader so
    that others may learn and benefit from your issue.
    ====================================================
    This posting is provided "AS IS" with no warranties, and confers no rights.

    --------------------
          From: "=?Utf-8?B?UGVyZQ==?=" <Pere@discussions.microsoft.com>
          Subject: RE: ADMT v2.0 Database corruption question
          Date: Thu, 19 Aug 2004 02:05:02 -0700
          Newsgroups: microsoft.public.windows.server.migration
          
          bit more background..
          
          The person before me on the project migrated groups from a NT4 and
    W2K
          domain, and the groups had exactly the same name !! Therefore two
    groups are
          showing with the same RID in the database.
          
          When I migrated groups I now pre-fix them with the old source name so
    we
          don't have the same issue.
          
          Also, they tried to merge SID by migrating the W2K account..then
    renaming it
          to the NT4 account name..and migarting the NT4 account over the
    top..they
          seemed to think this would work..but I have my doubts.
          
          As I posted..I have tried all this with fresh groups..still didn't
    work.
          This is why I'm wondering if the database has somehow become confused
    due to
          the duplicate names. The question is how to fix it, without
    impacting the
          already migrated user accounts.
          
          
          "Pere" wrote:
          
    > Thanks for the reply, I will elaborate..
    >
    > We have migrated pilot users for 3 Domains..1 W2K, and 2 NT4.
    >
    > All the groups for the domains have been migrated first, and we are
    > migrating the users in either batches or individually.
    >
    > The problem is with W2K Domain..
    >
    > User A is a member of group A in Source Domain
    > Group A has been migrated across to the Target Domain
    > User A is migrated(with fix group selected) but does not
    re-establish his
    > membership of the migrated group A.
    >
    > *Testing*
    >
    > -A-
    > I created a new source group and added a new source user account to
    it.
    > I migrated the group.
    > I migrated the account - membership of the group was not
    established in the
    > target domain
    >
    > -B-
    > I removed the test account and group
    > I renamed the database so it would start a fresh one.
    > I did the same as -A-, this time membership was established.
    >
    > We had this problem soon after the start of the migrations..but it
    suddenly
    > started working..now it doesn't work again.
    >
    > The logs show nothing..the process shows adding group
    membeships..but
    > doesn't pick them up.
    >
    > I'm looking at the database in Access..but nothing to show me yet
    why it is
    > failing for this Domain.
    >
    > "Bob Qin [MSFT]" wrote:
    >
    > > Hi Pere,
    > >
    > > Thanks for your posting here.
    > >
    > > I am not very clear about the symptom you mentioned that "it
    doesn't pick
    > > up any group memberships". Would you please provided some screen
    captures
    > > to describe the scenario detailedly?
    > >
    > > In addition, is there any error in the migration log?
    > >
    > > Best regards,
    > > Bob Qin
    > > Microsoft Online Partner Support
    > >
    > > Get Secure! - www.microsoft.com/security
    > >
    > > ====================================================
    > > When responding to posts, please "Reply to Group" via your
    newsreader so
    > > that others may learn and benefit from your issue.
    > > ====================================================
    > > This posting is provided "AS IS" with no warranties, and confers
    no rights.
    > >
    > > --------------------
    > > From: "=?Utf-8?B?UGVyZQ==?="
    <Pere@discussions.microsoft.com>
    > > Subject: ADMT v2.0 Database corruption question
    > > Date: Wed, 18 Aug 2004 10:07:04 -0700
    > > Newsgroups: microsoft.public.windows.server.migration
    > >
    > > We appear to have a corrupt ADMT v2.0 database file.
    > >
    > > The problem is that when we now migrate Windows2000 user
    accounts for
    > > one
    > > domain, it doesn't pick up any group memberships(groups
    already
    > > migrated).
    > >
    > > The others (NT4 domains) are working fine still.
    > >
    > > We have tested this with a new database, and works fine, so
    were
    > > wondering
    > > if anyone knows a way to correct the corruption without
    impacting the
    > > already
    > > migrated groups for the other domains.
    > >
    > >
    > >
          

  • Next message: Feng Mao: "RE: Domain List could not point to new domain automatically"

    Relevant Pages

    • RE: MIgration Question
      ... The source domain must trust the target domain ... The user account that is running ADMTv2 had Administrator rights in the ... If the target domain is a Windows Server 2003 domain, ... Active Directory Migration Tool Overview ...
      (microsoft.public.windows.server.migration)
    • RE: MIgration Question
      ... migrate a global group with SID history, migrated one user account. ... starting user/group migration. ... The source domain must trust the target domain ... If the target domain is a Windows Server 2003 domain, ...
      (microsoft.public.windows.server.migration)
    • Re: ADMT and log on scripts
      ... That is not true if you migrated SID History, it can still use it's old SID ... > the source account during the migration, so the only way the migrated ... >> still has read rights to the NETLOGON share in the source domain, ...
      (microsoft.public.win2000.active_directory)
    • RE: ADMT v2.0 Database corruption question
      ... >> latest two migration logs in your post. ... >> showing with the same RID in the database. ... > account to ... >> no rights. ...
      (microsoft.public.windows.server.migration)
    • Re: Computer account is not disabled in source domain using ADMT
      ... Does the user account that is migrating the computers have the permissions in the source domain to disable the accounts? ... Source Domain: Windows 2000 Server / Sp4/ Native Mode ... Migration tool: ADMT 3.0 on Windows server 2003 R2 ...
      (microsoft.public.windows.server.active_directory)