Problem with profiles using ADMT

Dear Alvin,

Thank you for your post.

Please ensure that the user account used to run ADMT must have
administrative privileges on the client computers to be migrated.
Otherwise, the agent cannot be dispatched to the client and we will get an
"Access is denied" error.

If the problem still persists after adding the account to the client
machine's local Administrators group, I would like to know the following:

1. During the last step of migrating the computer account, a window titled
"Active Directory Migration Tool Agent Monitor" appears. What is shown in
the "Status" column?

2. Please click the "View Dispatch Log" button, and then post the content
of the dispatch.log file.

3. In the same time, is a "System Shutdown" window displayed on the screen
of the client computers to be migrated?

Thank you and have a nice day!

Regards,
Joe Wu
Product Support Services
Microsoft Corporation

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: "Alvin" <alvin_g.TakeThisOut@sbcglobal.net>
|References: <O$6FiDZbDHA.1872@TK2MSFTNGP12.phx.gbl>
|Subject: Re: Problem with profiles using ADMT
|Date: Thu, 28 Aug 2003 15:05:57 -0700
|Lines: 37
|X-Priority: 3
|X-MSMail-Priority: Normal
|X-Newsreader: Microsoft Outlook Express 6.00.2800.1158
|X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
|Message-ID: <#kD0SCbbDHA.2580@TK2MSFTNGP12.phx.gbl>
|Newsgroups: microsoft.public.windows.server.migration
|NNTP-Posting-Host: user8x175.lacoe.edu 156.3.8.175
|Path: cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP12.phx.gbl
|Xref: cpmsftngxa06.phx.gbl microsoft.public.windows.server.migration:3035
|X-Tomcat-NG: microsoft.public.windows.server.migration
|
|This is what I came up with, not sure if it is meant to be or something is
|still wrong, but it works. I haven't read anything regarding any sequence
|when running the migration.
|
|When I migrate the user account first, then the computer account, the users
|will get their same profile whether logged into the source or target
domain.
|If it's ran vise-versa, the user get a new profile when logged into the
|source domain.
|
|Alvin
|
|
|
|"Alvin" <alvin_g.TakeThisOut@sbcglobal.net> wrote in message
|news:O$6FiDZbDHA.1872@TK2MSFTNGP12.phx.gbl...
|> Hello,
|>
|> As I just posted, I am in the process of migrating W2K computer and users
|> from an NT4 domain to a W2K domain. Both the user and computer accounts
|> migrate and complete with no errors. Everything looks good until the user
|> logs onto the W2K domain; the users original profile is not associated
|with
|> the W2K domain. In other words, it is giving the user a new profile on
the
|> workstation. I choose that the profiles were to be translated, so I would
|> thnik they would have the same profile just in a new domain. This worked
|on
|> my test bench migrating computers to W2K3 srv. Is there any order of
|> migration that needs to be followed? It keeps giving my users new
|profiles.
|>
|> Appreciate the help.
|>
|> Alvin
|>
|>
|
|
|
 >> Stay informed about: Problem with profiles using ADMT 

hi,
that's the expected behavior.
when you migrate a user account a mapping is created between a source and
target account in the admt database, so the two accounts will be associated.
When profile translation is performed, this mapping is used to translate
profiles to the correct account. If the profile translation occur prior to
the user migration, this mapping will not exist and since the source user
has not associated target account, the profile will not be translated.
thanks


"Alvin" <alvin_g DeleteThis @sbcglobal.net> wrote in message
news:#kD0SCbbDHA.2580@TK2MSFTNGP12.phx.gbl...
> This is what I came up with, not sure if it is meant to be or something is
> still wrong, but it works. I haven't read anything regarding any sequence
> when running the migration.
>
> When I migrate the user account first, then the computer account, the
users
> will get their same profile whether logged into the source or target
domain.
> If it's ran vise-versa, the user get a new profile when logged into the
> source domain.
>
> Alvin
>
>
>
> "Alvin" <alvin_g DeleteThis @sbcglobal.net> wrote in message
> news:O$6FiDZbDHA.1872@TK2MSFTNGP12.phx.gbl...
> > Hello,
> >
> > As I just posted, I am in the process of migrating W2K computer and
users
> > from an NT4 domain to a W2K domain. Both the user and computer accounts
> > migrate and complete with no errors. Everything looks good until the
user
> > logs onto the W2K domain; the users original profile is not associated
> with
> > the W2K domain. In other words, it is giving the user a new profile on
the
> > workstation. I choose that the profiles were to be translated, so I
would
> > thnik they would have the same profile just in a new domain. This worked
> on
> > my test bench migrating computers to W2K3 srv. Is there any order of
> > migration that needs to be followed? It keeps giving my users new
> profiles.
> >
> > Appreciate the help.
> >
> > Alvin
> >
> >
>
>
 >> Stay informed about: Problem with profiles using ADMT