RE: Profile problem during migration

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Karthi (Karthi_at_discussions.microsoft.com)
Date: 01/12/05 

Date: Wed, 12 Jan 2005 05:47:06 -0800

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:

> 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.
>
>

Relevant Pages

  • Re: SID Hitory Not Working after ADMT 3 Migration
    ... As you said "Which is located on the user accounts profile tab", ... SID Hitory Not Working after ADMT 3 Migration ... Sid history via groups is working. ...
    (microsoft.public.windows.server.migration)
  • Re: Corruption of ADMT translated profile
    ... translation and that worked. ... the only issue was to have Win XP SP2 firewall turned off before migration. ... Some days after the computer is migrated, is when I do the the profile ... > 6 Please ping each DC in Source Domain and Target domain on the client. ...
    (microsoft.public.windows.server.migration)
  • Re: ADMT Cannot migrate the correct SID to the target domain.
    ... This profile translation automatically switches from replace mode to ... Did you log off the Windows XP before you perform computer migration? ... Try perform security translation once more to see the results. ... ADMT Cannot migrate the correct SID to the target domain. ...
    (microsoft.public.windows.server.migration)
  • Re: ADMT migration, cannot access profiles
    ... profile. ... During user migration, there's a check box for SID history ... What am I missing if I don't select the SID history option? ... SIDHistory allows the newly migrated user account to access the old domain resources without needing to login. ...
    (microsoft.public.windows.server.active_directory)
  • ADMT Cannot migrate the correct SID to the target domain.
    ... We are testing a inter forest migration. ... After finishing to migrate my users to target domain, then I migrate my test computer to the target domain. ... I can't use the old profile of my user on the test PC. ... Then I examined the migrated account's SID History with ADSIedit. ...
    (microsoft.public.windows.server.migration)