windows xp user profile migration using Quest Migration Manager -Resources Migration tool

Sponsored Links

Hi,

We are currently migrating our user from Domian A to Domain B using
the Quest Migration Manager. Apparrently, before we do the migration
which are also changing the UserId of the user from the Domain A. We
let them login first to the newly renamed userid on their workstaion
before we migrate it. When we, try to migrate the user, resource and
computer of the user to Domain B and user logon, a new profile is
being created.

I think the Quest Migration Manager - Resources Migration tool is not
successful on migrating the resource of profile of a user.

Can somebody give us some suggestion on how we can fix it? We will be
migrating around 700+ users.

thanks,

Hello jher0928@yahoo.com,

Basically this should be a question for Quest, shouldn't? But try out USMT:
http://www.microsoft.com/downloads/d...displaylang=en

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm


> Hi,
>
> We are currently migrating our user from Domian A to Domain B using
> the Quest Migration Manager. Apparrently, before we do the migration
> which are also changing the UserId of the user from the Domain A. We
> let them login first to the newly renamed userid on their workstaion
> before we migrate it. When we, try to migrate the user, resource and
> computer of the user to Domain B and user logon, a new profile is
> being created.
>
> I think the Quest Migration Manager - Resources Migration tool is not
> successful on migrating the resource of profile of a user.
>
> Can somebody give us some suggestion on how we can fix it? We will be
> migrating around 700+ users.
>
> thanks,
>

[Migrator1]

There are a couple of issues here.
1. The new userid
2. The blank profile generations

First if you are changing user ID's in the target domain you can do so via an import file during the migration of the user account

the import file should be a flat file with a header row of samaccountname tab samaccountname then for example john.smith tab jsmith.
This will create the account in the target AD with the new user ID and also match the source account with the target acount of the new name.

The matching of accounts in the ADAM database is what will allow the Resource updating Manager to properly process the permissions.

Now another option is to check that the new target account has access to the source user accounts profile and then just update the profile path in the registery of the target account to point to the folder of the source user accounts profile. This is what the tool is doing in the backround anyway.

Hope this helps,

Over 2,000,000 million migrated users www.coherence.us