Re: NT Domain to AD migration
- From: Charles Woolever <info@xxxxxxxxxxxxxxxxxxxx>
- Date: Sat, 06 Oct 2007 16:57:31 -0400
No real reason other than wanting to make sure everything works. With
having an Exchange 5.5 SP4 machine (on W2K Server SP4) and a MS SQL 6.5
machine on NT4.0, we knew W2K would work with everything. All the
servers are W2K SP4 right now except the PDC (also runs SQL 6.5) and 3
BDCs. Two of the BDCs are new created and were created specifically
because they are upgradable to W2K. The PDC and original BDC are not
upgradable.
I had heard about 2003 (may be unjustified?) not playing well with NT
domains and earlier versions of software.
Although the current scheme actually works completely fine for us, we
need to get rid of the PCD and BDC due to age.
Once the "new" BDCs are upgraded to W2K and are domain controllers, I'd
like to move that function over to two other PowerEdge 1800 and 2900
servers running W2K and then make them the domain controllers. Then the
two previous domain controllers can be retired also.
So my main concerns are:
1) Get rid of NT PDC and BDC
2) Still support Exchange 5.5 SP4 until that too can be upgraded.
3) Still support SQL 6.5 until that can be tossed or upgraded. It
supports a financial package that will be going (hopefully) in the next
6 months anyway.
4) All other functions (DNS, DHCP, file serving, anti-virus, intranet
(IIS) are all on W2K already.
Thanks,
Charles
In article <60FCA506-9047-450C-9CAA-200C497FAE5D@xxxxxxxxxxxxx>,
Richard Crandall <Richard Crandall@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
Charles, if your W2K machine that is running DHCP is a domain member then one.
other thing that you are going to want to remember to accomplish after the
upgrade in place is to authorize this DHCP server.
Also, after you upgrade your DCs to W2K, assuming this is during off hours,
I would recommend that you reboot the clients. The reason is that the
clients will pick up the new DNS domain as their primary suffix. I do
recommend that you wait until all of the DCs are up to W2K though otherwise
what you will see are some clients (servers included) will not update this
information.
I do a lot of migrations and I am just curious, what was the reason that you
decided not to go straight to W2K3?
Thanks Charles.
/rich
"Charles Woolever" wrote:
Yes, I knew that. The first step is to 2000 and then to 2003. Thanks.
Charles
In article <u5ncjv7$HHA.4476@xxxxxxxxxxxxxxxxxxxx>,
"Jorge Silva" <jorgesilva_pt@xxxxxxxxxxx> wrote:
Windows 2000? Remember that 2000 is under MS extended support, and soon
will
be no support for 2000.
The steps are basically the same.
--
I hope that the information above helps you.
Have a Nice day.
Jorge Silva
MCSE, MVP Directory Services
- Prev by Date: Re: Audit dept request
- Next by Date: Re: Get user password in Active Directory
- Previous by thread: certmagic.com exams ?
- Next by thread: DSListRoles Call Failed, Error 6 Could not reach DS at home server
- Index(es):
Relevant Pages
|
