ADMT V3

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

Hi,

Migrating groups with ADMT V3 between 2 forests.
In source domain, global groups A and B exists.
Group A is a member of group B.

When both groups are migrated in target domain with ADMT, group A is not
automatically added as member of group B!

Any solutions!

Thanks




.

Relevant Pages

  • RE: Interforest Migration
    ... migration with ADMT v3. ... we don't have to create a global group before we perform the ADMT ... change to the source domain re: ... we need to use a member of the Built-in\Administrators ...
    (microsoft.public.windows.server.migration)
  • RE: ADMT ver 3: ERR2:7816
    ... I was originally logging into the target server (with ADMT on it) using the ... source domain admin account, and this user account was a member of the local ... Although this source domain admin had ...
    (microsoft.public.windows.server.migration)
  • RE: ADMT Security Translation Requirements
    ... you can use ADMT with security translation for changing the ... You want to know if you can use sid mapping file to remove the sids from ... >Thread-Topic: ADMT Security Translation Requirements ... >> before you can run ADMT security translation without source domain no ...
    (microsoft.public.windows.server.migration)
  • Re: Questions about ADMT
    ... The lingering effects of ADMT are miniscual. ... In your source domain, you have ... the Domain Admin account, the Local Domain Group named yourdomain$$$, and ... > domain's admin account from the administrator group on the existing ...
    (microsoft.public.win2000.active_directory)
  • Re: problem migrating security settings via ADMT
    ... After migrating a single computer that's a member server of the ... > source domain and shutting the source domain controller down, ... > Does anybody know if this is the way ADMT works or is it a bug? ... adding them to the builtin groups on a member server, ...
    (microsoft.public.win2000.active_directory)