Re: NT4 - ADMT - 2003 & XP Agents

From: Sven (s_selleslagh_at_hotmail.com)
Date: 03/24/05


Date: Thu, 24 Mar 2005 14:32:30 +0100

Jason,

About your remark on the 1st question "You may have to ensure that all
Workstations point to
the 2003 DNS Server prior to their migration."

Isn't it possible to create a MS KB article for this issue ? Today this is
not documented at all and apparently more people are experiencing problems
with workstation migrations (see also my posting of 16 March ADMT computer
migration and name resolution (DNS))

Regards,
Sven

"Jason Tan (MSFT)" <v-jasont@online.microsoft.com> wrote in message
news:kIkdMuDMFHA.2632@TK2MSFTNGXA03.phx.gbl...
> 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: ADMT Problem Migrating Workstations
    ... I have choosen the Add option so I believe the profile is added, ... I am using ADMT to migrate objects from a W2K3 forest to a new W2K3 ... I have migrated some workstations successfully but when the user log on ... Did you opt to use the Security translator during the migration? ...
    (microsoft.public.windows.server.active_directory)
  • Re: Please help!! 5 user - simple migration
    ... After migration they can move there outlook data back to the inbox and have ... and you have to copy the profile content to the new created local ... profiles are local on the workstations. ... Is the 2000 server also SBS version? ...
    (microsoft.public.windows.server.migration)
  • Re: Please help!! 5 user - simple migration
    ... After migration they can move there outlook data back to the inbox and have it on the new exchange server or just let it on the .pst file. ... and you have to copy the profile content to the new created local ... profiles are local on the workstations. ... Is the 2000 server also SBS version? ...
    (microsoft.public.windows.server.migration)
  • RE: Active Directory migration - Prep work??
    ... migration that has been sinking. ... resources to get the whole thing done. ... Proof of Concept (Create a test OU and workstations to be migrated) ... DNS forwarding works in this scenario, ...
    (microsoft.public.windows.server.active_directory)
  • RE: Active Directory migration - Prep work??
    ... migration that has been sinking. ... resources to get the whole thing done. ... Proof of Concept (Create a test OU and workstations to be migrated) ... DNS forwarding works in this scenario, ...
    (microsoft.public.windows.server.active_directory)

Loading