Re: ADMT 2.0 Profile Issue

SWalters wrote:

We have successfully migrated all user accounts from the old domain to
the new domain. I also disabled SID Filtering which gave us successful
mapping of new domain accounts accessing the old domain resources
without issue.

We migrated a couple test workstations in order to see what happens to
the old profiles.

Here is what we are left with.

The old profiles were changed (security wise) to the new domain. So if I
were looking at the Profiles under the properties of My Computer I would
now see NEWDOMAIN\USERACCOUNT insetad of OLDDOMAIN\USERACCOUNT.

I also checked the file securities on the old "Docuements and Settings
\Profile" and the new Domain account has the appropriate rights. Which
makes sense because of the previou paragraph's findings.

Here is where the problem comes into play. When the user logs on as the
new domain account it creates yet another profile giving it a .NEWDOMAIN
at the end of the folder under "Documents and Settings". I was able to
go into the registry and change which folder the new profile was
pointing to and it worked but we are hoping to have all users login and
have their old profile be the first accessed so we do not have to edit
the registry on each user.

Please let me know if someone needs addtional information for
clarification.

Thanks in advance!

Update: I did find an old post regarding this and it seems that you need
to run Translation Wizard. If this is correct I wanted to confirm the
order and settings to make this work properly.

The user migration is already done for all users. So after doing the
workstation migration I then run the Translation Wizard in ADMT and set
the following options:

-Previously migrated objects
-Source domain: = old domain
-Target domain: = new domain
-Computer Selection: Select the workstation that was migrated from the old
domain to the new domain from the list of computers in the new domain
-Additional trusting domain: Do nothing with this...
-Translate Objects: Only select "User profiles" or do I select everything?
-Security Translation Options: = "Add"

With the above settings this should occur right after the Computer
Migration in ADMT but prior to the user logging into the New domain
account. If this occurs then the user logging into the New domain should
be using the profile from the Old domain?


--
-=SW=-
-MCSE CCEA CCNA-
.

Relevant Pages

  • Re: ADMT 2.0 Profile Issue
    ... I also checked the file securities on the old "Docuements and Settings ... new domain account it creates yet another profile giving it a .NEWDOMAIN ... The user migration is already done for all users. ...
    (microsoft.public.windows.server.migration)
  • Re: It must be simple, but...
    ... Copy the contents of the old profile into the new profile. ... I tried to run the connectcomputer wizzard on the client again, ... > don;t have any of the user settings. ... >> Transferring the settings of the local account to the domain account is ...
    (microsoft.public.windows.server.sbs)
  • Re: ADMTv2 computer migration wizard/local profiles issue
    ... >> computer migration, ... >> the migrated computer has their old profile and all is good. ... their old icons and settings, but not all the GPOs for the profile are there. ... > Which users accounts in what domain are used to log on which computers ...
    (microsoft.public.win2000.active_directory)
  • Re: user migration
    ... If it doesn't succeed, try removing the computer from the domain, delete the directories for _SBS_netsetup_ under 'Documents and Settings' and try to add the Administrator account without transferring the profile. ... If it succeeds, then you know that the migration problem is in the user's profile. ...
    (microsoft.public.windows.server.sbs)
  • Re: Re: ADMTv2 computer migration wizard/local profiles issue
    ... >> So you migrated a computer and also re-acl the local profile ... > documents and settings, so it is using their old settings. ... Migration tool\ on the PC that you ran your user and group migration ...
    (microsoft.public.win2000.active_directory)