RE: NT4 - ADMT - 2003 & XP Agents

From: Jason Tan (v-jasont_at_online.microsoft.com)
Date: 03/24/05 

Date: Thu, 24 Mar 2005 06:34:34 GMT

Hi JS,

Thanks for posting!

Based on the description, I would like to provide you with the following
information for your reference:

The first question:
=============================
A: It looks like the Workstations in the NT Domain could not successfully
resolve the DNS Domain name for the Windows 2003 Domain successfully.
Please point the Workstation to the DNS Server in the 2003 Domain and test
the migration again. You may have to ensure that all Workstations point to
the 2003 DNS Server prior to their migration.

The second question:
=============================
A: Since it occurred randomly sometimes, please help me collect the
information when it reproduces again.

1. Please save the event logs as .evt files and then send them to me at
v-jasont@microsoft.com.

2. Please send the full ADMT log files to me at v-jasont@microsoft.com.

If we only quote out of context from the log, we may not be able to
completely understand the problem and get it resolved as efficiently as
possible. ADMT creates several log files in the Logs folder under the ADMT
folder on the computer on which the tool is installed. User and group
migration progress is recorded in *Migration.log*; dispatcher progress is
recorded in *Dispatcher.log*; and the progress of the Trust Migration
Wizard is recorded in *Trust.log*. Additionally, the progress of each agent
is recorded in log files named for the computer to which the agents are
dispatched. These log files are located in the Agents folder under the
previously mentioned Logs folder. Each agent also records information a
*Dctlog.txt* file which is created in the folder specified by the %TEMP%
variable on each computer to which an agent is dispatched. Please send all
these files to me.

The third question:
================================
A: The cause could be that you use Add mode when migrating computer
account.

The example of Migration:

Use user1 to logon to NT domain, you will find the profile is located to
c:\documents and settings\user1.domain

1. Logon to the windows 2003 domain DC and run ADMT to migrate user account
user1.

2. Migrate computer account Client XP. During the migration, tick User
profile on Translate objects screen.

3. Choose Replace mode.

4. Follow the wizard to migrate the computer account.

5. Go to XP client, log on to the windows 2003 domain. You will find the
user profile is still using c:\documents and settings\user1.Win2k3Dom.

We recommend using Replace mode.

Local profiles are translated in replace mode because if you perform the
profile translation in add mode, software installation by means of software
deployment Group Policies might not work.

User profile migration, please refer to the following link:

Remigrating User Accounts and Workstations in Batches
http://www.microsoft.com/resources/documentation/WindowsServ/2003/all/deploy
guide/en-us/Default.asp?url=/resources/documentation/WindowsServ/2003/all/de
ployguide/en-us/dssbi_reer_zgwe.asp

If there is anything that is unclear, please feel free to let me know.

Thanks & Regards,

Jason Tan

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.

Relevant Pages

  • RE: Migration client issues
    ... You may use logon script to copy profile or my favorites to the new ... In Windows NT 4.0, locally cached profiles are stored as a subfolder of the ... Regardless of whether the user logs on to a local account or an account ... Description of Windows 2000 User Account and Profile Migration ...
    (microsoft.public.windows.server.migration)
  • ADMT v3.0 ERR3: 7438 no NTUser.DAT file for "user" was found
    ... I am doing an interforest migration and trying to migrate a user from ... domain a --> domain b (target domain). ... The roaming profile cannot be migrated" ... Do not expire source account ...
    (microsoft.public.windows.server.migration)
  • Re: AD Migration Feedback
    ... enterprise-wide domain migration is not something you want to get "creative" ... > exactly as if it were one of the NT4 account domains. ... I guess the script ... > guessing that the user profile is somehow migrated by a 3rd party tool. ...
    (microsoft.public.win2000.active_directory)
  • Profile Manager Copy To not available
    ... >the migration was performed, a new user was created with ... >the same username but for the new domain. ... >I have tried to use the Copy To function on the Profile ... >regardless of which account I am using. ...
    (microsoft.public.windowsxp.security_admin)
  • (Trying to debug) Laptop Latency issues off of domain network
    ... screen, login, and gneral while running application latencies. ... UserEnvDebugLevel log files are generated and the records sorted as per ... The GetProfileType function retrieves the type of profile loaded for the ... WMI includes an object repository, which is the database of object ...
    (microsoft.public.windowsxp.setup_deployment)