RE: ADMT 2.0 win2k >> win2003 forest computer accounts issue

From: Feng Mao (fengmao_at_online.microsoft.com)
Date: 08/31/04


Date: Tue, 31 Aug 2004 11:09:00 GMT

Hi Dan,

Thank you for posting!

As I know, ADMT agent can help to move the computer accounts from the
source domain to the target domain. It can help to change the clients from
the source domain to the target domain. However, it did not change the
cached logon domain. That is the say, after the migration, when the user
logon the computer, it will see the logon domain still be the original one.
But the logon domain name will be changed after you logon and restart it.

For detailed information about how to use ADMT for migration, you may visit
the below articles in Microsoft Knowledge base:

326480 How to Use Active Directory Migration Tool Version 2 to Migrate from
http://support.microsoft.com/?id=326480

325851 How To Set Up ADMT for a Windows NT 4.0-to-Windows Server 2003
Migration
http://support.microsoft.com/?id=325851

832221 How to configure the Active Directory Migration Tool to migrate user
http://support.microsoft.com/?id=832221

Have a nice day!

Thanks & Regards,

Feng Mao [MSFT], MCSE
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: pearsondan99@hotmail.com (Dan Pearson)
| Newsgroups: microsoft.public.windows.server.migration
| Subject: ADMT 2.0 win2k >> win2003 forest computer accounts issue
| Date: 30 Aug 2004 16:51:50 -0700
| Organization: http://groups.google.com
| Lines: 24
| Message-ID: <4c3faf5c.0408301551.44b005ae@posting.google.com>
| NNTP-Posting-Host: 61.9.213.159
| Content-Type: text/plain; charset=ISO-8859-1
| Content-Transfer-Encoding: 8bit
| X-Trace: posting.google.com 1093909910 28254 127.0.0.1 (30 Aug 2004
23:51:50 GMT)
| X-Complaints-To: groups-abuse@google.com
| NNTP-Posting-Date: Mon, 30 Aug 2004 23:51:50 +0000 (UTC)
| Path:
cpmsftngxa10.phx.gbl!TK2MSFTNGXA03.phx.gbl!TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP0
8.phx.gbl!news-out.cwix.com!newsfeed.cwix.com!news.maxwell.syr.edu!postnews2
google.com!not-for-mail
| Xref: cpmsftngxa10.phx.gbl microsoft.public.windows.server.migration:13433
| X-Tomcat-NG: microsoft.public.windows.server.migration
|
| Ok scenario:
|
| Win2k forest >> win2003 forest migration
|
| all admt prerequisits setup, users migrated sucessfully, computers....
|
| two problems:
|
| Computers aren't rebooting after agent completes..
|
| computer accounts in the target domain must be corrupt or incomplete
| as when a migrated user [whos profile has migrated sucessfully] logs
| on login script fails to run and the computer gets access denied when
| connecting to any shares
|
| As a test I removed the migrated computer from the new target domain
| and rejoined manually and it works fine so there must be something in
| the process thats failing, any ideas would be gratefully received or
| an alternatvie for migrating computers from one domain to another and
| retaining user proflies
|
| Thanks in advance
|
| Dan
|



Relevant Pages

  • RE: ADMT local user profile migration
    ... After a long try with ADMT 2, ... in target domain, and kept it enabled in source domain. ... using the group migration wizard, ... My file server and ...
    (microsoft.public.windows.server.migration)
  • RE: SidHistory and password migration with ADMT
    ... on the target domain. ... |Subject: RE: SidHistory and password migration with ADMT ... I let ADMT create it. ... |In target domain there are deafult user rights in registry ...
    (microsoft.public.windows.server.migration)
  • RE: ADMT local user profile migration
    ... ADMT V2 did not let me transfer local profile. ... Yes, with version 3, I was able to migrate user, computer, local profile. ... > migration you found these account still disabled. ... >>>in target domain, and kept it enabled in source domain. ...
    (microsoft.public.windows.server.migration)
  • RE: Domain List could not point to new domain automatically
    ... Please understand that ADMT only works on the Domain Controller to migrate ... Microsoft Online Partner Support ... The migration ... |>|>agent will help to change the logon domain. ...
    (microsoft.public.windows.server.migration)
  • RE: Domain List could not point to new domain automatically
    ... I tried to use another computer to reboot the ... >installation of ADMT. ... The migration ... >|>agent will help to change the logon domain. ...
    (microsoft.public.windows.server.migration)