Weird Migration

[Nuflo]

Hello group:

I'm having this problem: I had an old NTdomain and now they bought a new
server so I created a new 2Kdomain with a name more like the company's new
name.

I migrated all users with their own passwords using ADMT (Including SID)
but when I change any workstation (win 2k pro or XP pro) to new domain and
the user logon in the workstation a new profile is created (user.2Kdomain)
under documents and settings folder.

The old school solution is to copy all the content of the user profile to
the new profile folder but I could do that if I had 5 o 10 users but I have
nearly 100 users and can't even think on doing this manually. And we will
not speak about some fantastic P-II machines that we still have.

Does anyone know any simple way to migrate users to another domain without
having to copy all the profiles again but using the old profile in the
workstations?

Thanks in advance

 

[Scott Harding - MS MVP]

This is by design and is to be expected. You should upgraded your domain and
not used ADMT to avoid this exact issue. That way the domain profiles would
be in tact. But it sounds like you wanted to change your domain name and the
only way to do that is to either rename your NT4 domain or install a new
domain and use ADMT. The only choices I see is to either start over and do
an in place upgrade of your domain or touch every box with your current
setup.

 

[Army of Juan]

I've done a migration from NT to 2000 and I'm about to do a another 200
to 2003 domain move. The NT move we created to AD and each use
accounts and workstations manually (we couldn't put in a full trus
between the domains so no ADMT). We had to touch each PC (about 700 a
the time) to force the user's profiles to use the old domain profil
(add the new account full rights to the old profile, editing the reg t
point to the old profile, mostly scripted) This time we'll have a ful
trust so we are going to try ADMT to clone the accounts (to keep th
old SIDs) and I found a trick to keep the profiles intact also.

http://tinyurl.com/2nwff

The link is old but the concept still works so I recreated the batc
files as VBScripts (so I don't need the files from the Resource kit
and we have WinXP clients anyway) and modified them pretty heavily bu
it seems to work as advertised. We are hoping to be able to move th
PCs and user accounts over to the new domain using only login script
(and maybe a little SMS 2.0) and not touch any of the PCs. I'm hopefu
but you never know what'll go wrong or not work


-
Army of Jua