Basically you need to do the following:
1. Power down your NT4 PDC
2. dcpromo your Win2K Server that you want to make a DC
- it will take the PDC role
- the SAM will move into this new PDC just fine (did for our domain
anyway - 7000 users)
3. Leave the NT4 PDC powered down.
4. Bring more Win2K DCs online as you need/like (pay attention to FSMO
roles as you do this)
5. When you feel you have enough Win2K DCs, take the rest of the NT4 BDCs
offline
6. When you are confident that the domain is working correctly, move to
native mode.
There's a white-paper from MS on this that's pretty clear... but I don't
remember the Q number off hand.... also you need to be considering how your
DNS is setup for your domain... you really should read that Q article...very
helpful.
jeff e.
-----Original Message-----
From: Jasmine [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, October 24, 2001 3:31 PM
To: NT 2000 Discussions
Subject: Ramifications to SAM when Joining a W2K Server to an NT 4 Domain
We are gradually migrating and introducing Windows 2000 Servers into our NT4
Domain.
I have been informed if I make the W2K Server a Domain Controller it will
automatically become the PDC. What happens to the current SAM.
Will my existing User Manager Database go over smoothly. Do I have to
recreate the database. How will effect the current client workstations when
they log on the next day.
I have left the W2K server as a standalone for now till I am confident that
I will not have a lot of failed logins from my client machines.
Can anyone give me help??
Thanks..
Jasmine.
------
You are subscribed as [EMAIL PROTECTED]
Archives: http://www.swynk.com/sitesearch/search.asp
To unsubscribe send a blank email to [EMAIL PROTECTED]
------
You are subscribed as [email protected]
Archives: http://www.swynk.com/sitesearch/search.asp
To unsubscribe send a blank email to [EMAIL PROTECTED]
