| Author |
Message |
Karthi
Guest
|
 Posted:
Wed Jan 12, 2005 6:45 am Post subject:
Profile problem during migration |
|
|
We are migrating from Windows NT 4.0 domain to Windows 2003 native domain
with the help of
ADMT v2 tool using the SID histroy migration.
We migrated the users and groups to Windows 2003 native domain using SID
history. We logged in
using few user account to the target domain and we verified that we can
access the resources located
in the source domain. We ran computer migration wizard in the ADMT tool and
migrated few workstations
to the target domain by selecting all the options (including user profiles)
and selected "ADD" options
It successfully migrated few workstationsto the target domain. We asked few
users to login to the new target domain
from the migrated workstations. It recrates the new user profile when they
log in to the new target domain
first time after their workstation successfully migrated to the target domain.
Users were loosing their old local computer profile settings on their
workstations.
We logged in to that workstation as an administrator and verified user
profiles under my computer properties.
It renamed the sourcedomain\username to targetdomain\username during the
computer migration.
When the user login to the target domain and it recreates the new profile
and it is not taking the existing profile.
Are we doing anything wrong in this procedure? We have only local user
profiles in the workstation for all the users.
We don't use the roaming profiles. Do you have any good documentation on ADMT?
Any help would be greatly appreciated.
Thanks |
|
| Back to top |
|
 |
Rebecca Chen [MSFT]
Guest
|
| Posted:
Wed Jan 12, 2005 11:52 am Post subject:
RE: Profile problem during migration |
|
|
Hi Karthi,
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. Any application that is packaged
with Windows Installer version 2.0 (which is used on workstations running
Windows 2000 SP3 or later, Windows XP SP1 or later, or many common software
packages) might not function after the profile is translated. When the ADMT
Security Translation Wizard is translating local profiles in replace mode,
it reverts to add mode if a profile is locked. This might result in a
successful profile translation; however, application installations might
not function after the profile is translated.
Before you start the local user profile translation, allow enough time for
the workstations to restart after you move them to the target domain. Allow
for the ADMT time delay factor (one minute) plus the time required for a
restart cycle for your workstations.
Please more details, 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
HTH!
Best regards,
Rebecca Chen
MCSE2000 MCDBA CCNA
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. |
|
| Back to top |
|
|
Karthi
Guest
|
| Posted:
Wed Jan 12, 2005 7:47 pm Post subject:
RE: Profile problem during migration |
|
|
Hi,
I checked your article in the Microsoft web site and this article applies to
the migration using without SID history. We are migrating with SID History.
Can we use the same article for our migration?
"Rebecca Chen [MSFT]" wrote:
| Quote: | Hi Karthi,
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. Any application that is packaged
with Windows Installer version 2.0 (which is used on workstations running
Windows 2000 SP3 or later, Windows XP SP1 or later, or many common software
packages) might not function after the profile is translated. When the ADMT
Security Translation Wizard is translating local profiles in replace mode,
it reverts to add mode if a profile is locked. This might result in a
successful profile translation; however, application installations might
not function after the profile is translated.
Before you start the local user profile translation, allow enough time for
the workstations to restart after you move them to the target domain. Allow
for the ADMT time delay factor (one minute) plus the time required for a
restart cycle for your workstations.
Please more details, 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
HTH!
Best regards,
Rebecca Chen
MCSE2000 MCDBA CCNA
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.
|
|
|
| Back to top |
|
|
Karthi
Guest
|
| Posted:
Thu Jan 13, 2005 6:01 am Post subject:
RE: Profile problem during migration |
|
|
I gone through the Windows 2003 deployment guide in your link. We have all
workstations located in resource domain. All the user accounts were located
in account domain. Users log in to the account domain from their workstation
which is attached to resource domain.
When I migrate the local user profile in replace mode using security
translation wizard, which domain I have to select in the source domain? Is it
resource domain or account domain? The Target domain always the Windows 2003
domain.
When I migrate the workstation using Computer migration, I can select the
source domain as resource domain and target domain as the Windows 2003 domain
since the workstation is attached to the resource domain.
Thanks
"Rebecca Chen [MSFT]" wrote:
| Quote: | Hi Karthi,
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. Any application that is packaged
with Windows Installer version 2.0 (which is used on workstations running
Windows 2000 SP3 or later, Windows XP SP1 or later, or many common software
packages) might not function after the profile is translated. When the ADMT
Security Translation Wizard is translating local profiles in replace mode,
it reverts to add mode if a profile is locked. This might result in a
successful profile translation; however, application installations might
not function after the profile is translated.
Before you start the local user profile translation, allow enough time for
the workstations to restart after you move them to the target domain. Allow
for the ADMT time delay factor (one minute) plus the time required for a
restart cycle for your workstations.
Please more details, 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
HTH!
Best regards,
Rebecca Chen
MCSE2000 MCDBA CCNA
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.
|
|
|
| Back to top |
|
|
Karthi
Guest
|
| Posted:
Sat Jan 15, 2005 2:27 am Post subject:
RE: Profile problem during migration |
|
|
As per your previous reply, profile migration should be run under "remove"
mode.
"Rebecca Chen [MSFT]" wrote:
| Quote: | Hi Karthi,
I have not used security translation wizard to migrate user profile,
actually during computer account migration you have choose to migrate the
user profile. It works perfectly on my side. The steps are as follows:
NOTE: The user account is v-rebc, the client XP is called RebcXP. The NT
domain called Domain, destination is Win2k3Dom.
Use v-rebc to logon to NT domain, you will find the profile is located to
c:\documents and settings\v-rebc.domain
1. Logon to the win2k3dom DC and run ADMT to migrate user account v-rebc
2. Migrate computer account RebcXP. During the migration, tick User profile
on Translate objects screen. Please refer to the screen shot.
3.Choose Add mode.
4.Follow the wizard to migrate the computer account.
5.Go to XP client, log on to the win2k3dom. You will find the user profile
is still using c:\documents and settings\v-rebc.domain.
HTH!
Best regards,
Rebecca Chen
MCSE2000 MCDBA CCNA
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 |
|
|
| Back to top |
|
|
Rebecca Chen [MSFT]
Guest
|
| Posted:
Mon Jan 17, 2005 3:09 pm Post subject:
RE: Profile problem during migration |
|
|
Oh, sorry for my topo.
ADD mode will cause the potential issue when you use GPO to deploy software
installation. Please use the Replace mode.
Please use the steps as I have tested and migrate the user profile in
Replace Mode.
Further qeustions, let us get in touch!
Best regards,
Rebecca Chen
MCSE2000 MCDBA CCNA
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. |
|
| Back to top |
|
|
|
|
|
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in