ADMT2 and roaming profiles...

  • Thread starter Thread starter Joe Cotter
  • Start date Start date
J

Joe Cotter

I am working for a company mid-way through a migration. They are
collapsing several(2) NT4 domains and one 2000 AD domain into one new
Windows 2003 domain. We have all trusts and everything functioning
perfectly. We are now trying to get the Windows 2000 users (there are
only a few) migrated to the new domain, and we're having a problem.
They use roaming profiles. And we're using ADMT2 to make the move from
the old domain to the new one.

We run ADMT2 and it runs without an error (yes, checked the log files)
and it tells us that it made the changes to the roaming profile
without incident. However, when we attempt to login on a machine with
that profile on the new 2003 domain it simply creates a new local
account on the machine and doesn't use the roaming profile. We've
verified that the account profile is pointing to the correct location
(on the server where all profiles are stored), but it just won't load
it.

Any ideas on what we are doing wrong? Why won't the roaming profile
load?
 
Hi Joe-

Did you choose the TranslateRoamingProfile option during the migration?
 
Hi Tim, YES - that option was checked during the migration. But when
we try to login to the new domain with the profile - the machine just
creates a local profile.
 
Hi Joe-

If you didn't see any overt errors during the migration with that option
selected, I'd think we need to see what is happening as the profile tries to
load, just to verify what we are seeing.

The idea is enable USERENV logging on the client machine, log on and off a
few times, reproducing the issue, then look at the USERENV.LOG for any
problems reaching it or processing it.

221833 How to Enable User Environment Debug Logging in Retail Builds of
Windows
http://support.microsoft.com/?id=221833

The idea is to see if starts to pull it down at all, which could indicate
that ADMT worked on the SID aspect, but there is poerhaps another issue at
hand.

A portion that will be applicable will look like this:
USERENV(93c.918) 02:22:40:489
=========================================================
USERENV(93c.918) 02:22:40:505 LoadUserProfile: Entering, hToken = <0x158>,
lpProfileInfo = 0x6f64c
USERENV(93c.918) 02:22:40:505 LoadUserProfile: Entering, hToken = <0x158>,
lpProfileInfo = 0x6f64c
USERENV(93c.918) 02:22:40:505 LoadUserProfile: lpProfileInfo->dwFlags =
<0x0>
USERENV(93c.918) 02:22:40:505 LoadUserProfile: lpProfileInfo->lpUserName =
<USER1>
USERENV(93c.918) 02:22:40:521 LoadUserProfile: lpProfileInfo->lpProfilePath
= <\\SERVER1\SHARE1$\USER1\Profile>
USERENV(93c.918) 02:22:40:521 LoadUserProfile: lpProfileInfo->lpDefaultPath
= <\\SERVER1\netlogon\Default User>
USERENV(93c.918) 02:22:40:521 LoadUserProfile: NULL server name
USERENV(93c.918) 02:22:40:521 LoadUserProfile: Created mutex. Waiting...
USERENV(93c.918) 02:22:40:536 LoadUserProfile: Wait succeeded. Mutex
currently held.
USERENV(93c.918) 02:22:40:692 GetOldSidString: Failed to open profile
profile guid key with error 2
USERENV(93c.918) 02:22:40:692 GetProfileSid: No Guid -> Sid Mapping
available
USERENV(93c.918) 02:22:40:692 GetOldSidString: Failed to open profile
profile guid key with error 2
USERENV(93c.918) 02:22:40:708 GetProfileSid: No Guid -> Sid Mapping
available
USERENV(93c.918) 02:22:40:708 ParseProfilePath: Entering, lpProfilePath =
<\\SERVER1\SHARE1$\USER1\Profile>
USERENV(93c.918) 02:22:40:755 LoadUserProfile: ParseProfilePath returned a
directory of <\\SERVER1\SHARE1$\USER1\Profile>
USERENV(93c.918) 02:22:40:755 RestoreUserProfile: Entering
USERENV(93c.918) 02:22:40:755 IsCentralProfileReachable: Entering
USERENV(93c.918) 02:22:40:771 RestoreUserProfile: Central Profile is
reachable
USERENV(93c.918) 02:22:40:771 RestoreUserProfile: Central Profile is
roaming
 
Back
Top