Re: NT->W2K3 User Migration Question
From: Keith Caravelli (keith_at_caravelli.com)
Date: 03/25/05
- Next message: Paul Bergson: "Re: GPO question"
- Previous message: Clayton Sutton: "GPO question"
- In reply to: Jason Tan: "Re: NT->W2K3 User Migration Question"
- Messages sorted by: [ date ] [ thread ]
Date: 25 Mar 2005 11:12:18 -0800
I am unable to reach you with the above address
v-jas...@microsoft.com.
I have run the dianostic report and I am ready to send it.
Here are the rest of the answers.
Please help me know how you DCpromo the new OEM Windows 2003 DC.
Server A: Old Win NT4 BDC -> Raised to PDC.
Then I followed the book on doing a "migration" and using ADMT. I made
the trust to server B:
Server B: This is a new OEM 2003 server dcpromod with the domain name
"Askomain.corp" because I couldn't use the original NetBIOS name of the
old domain which is "Asko".
I had problems with a test migration using ADMT tool on a single user
pc. I just did not go well and I also lost the users desktop in the
process.
To save time I went back and studied to do an in-place upgrade using a
BDC from the old "Asko" domain.
Before starting the upgrade on server A (NT4 PDC) I demoted the
Askomain.corp domain by running dcpromo.
I then put in the NT4Emulator key in the server A (old PDC) and
upgraded it to 2003.
This seemed to work fine. All user accounts came over and everyone has
logged in fine. Not many errors at all on this server A (old PDC)
I then proceeded to upgrade server B ( new OEM 2003) which was now just
member server. I was not able to connect to the server B (upgraded PDC)
now 2003 DC with AD installed. I read about "neutralizeNT4Emulator".
This allowed me to join up with the Asko domain and install AD.
I don't' think I can only login to either server using "asko" as
domain not "askomain.corp".
Where did you specific the "askomain.corp"?
If I understand you correctly. I think I stated this name as the Active
directory name for DNS. My whole intention was to keep the old NetBIOS
name intact so that I would not have to touch every pc like I would
with the ADMT. The ADMT was saving the individual user profiles on the
test machine so this made a mess.
Trusts:
OEM 2003 Server B: trusts showing on this server are incoming and
outgoing to Askomain. No trusts to Asko
Server A (upgraded PDC): trusts are same as B.
Current Progress:
Since my email to the newsgroup I have turned on user account auditing
in AD on Server B (OEM DC with AD). I have noticed that there are users
who show as NTLM other users who show as Kerboros. I have not manually
moved anyone and only rejoined two XP PCs to the new domain so users
are getting logged in to AD it seems. That was one of my questions to
the newsgroup. How do I know if someone is logging into NT or AD. It
seems this is the answer?
More:
I also tried (stupid I know) adding the "NTEmulator" key after the fact
two days ago to the oem server B new DC. This caused all XP and 2K PCs
to be unable to log in. I got a call from several users. I took out the
"NT4Emulator" key from the new OEM Server B and all was well.
So it seems that I am somewhat ahead of myself and everything may
actually be fine. I might be worried for nothing.
Since Both DC are replicating fine for AD and DNS I may be in better
shape that I think.
My next step is to wait for your response and then begin planning to
deal with our Win98 clients. If I just delete the NT4Emulator from the
the upgraded NT PDC now a 2003 DC with AD, I will cause mass panic in
getting the few Win98 PCs migrated.
I am also somewhat skeptical about my DNS configuration. I am not sure
its right, but that was because of the 5719 error which I would guess
your correct on.,
Anyway. long winded complex stuff. Thank you in advance for your help.
Keith Caravelli
.
- Next message: Paul Bergson: "Re: GPO question"
- Previous message: Clayton Sutton: "GPO question"
- In reply to: Jason Tan: "Re: NT->W2K3 User Migration Question"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
