Windows Server

Glyn Williams · Guest

Hi,
I am planning to take the step and do and in-place upgrade from an NT4
domain to a 2003 Active Directory. Here is my initial plan. I would be
grateful if anyone can have a look, and see where I might go wrong, and
answer a few questions I have.

Any help appreciated.
Glyn

NT4 to 2003 AD Upgrade Plan

Current Domain is 1 Domain with 1 PDC, and 3 BDC's.

All clients are Win2000 pro, XP Pro, and NT4 server SP6a.

My plan is to do an in place upgrade, and have *2 2003 server DC's. and
leave 3 reaming BDC's ready for decommissioning at a later date.

Install process overview.

(All servers have been tested and will run with both Operating systems
without problems)

Install new BDC2 ready to be dropped out before AD upgrade takes place in
case of AD upgrade failure.

Install new BDC1 ready for PDC promotion and AD Upgrade.

Install new 2003 server ready to be made into second DC and secondary DNS
server.

Promote BDC1 to PDC.

Shutdown and remove BDC2 from network.

In-place upgrade the new PDC to Active directory, with DNS incorporated.

Configure our DHCP server to point at new DNS sever.

Manually set our NT4 servers to use DNS, and update DNS server with NT4
server host records.

Run DCPROMO on 2003 server and use as DC2 and secondary DNS server.

Issues I am worried about.

Can I leave my old BDC's running, and decommission them at a later date??

I have Exchange 5.5 sp4 on a member server. This is the only server we have
a dns entry for. I.E mycompany.com.

Now we want to use a different internal domain from our external one, will
this cause problems on the exchange server.

I have MS Proxy server 2 on a BDC, will this have any issues ??

I have various SQL servers on member servers, will these have any issues.

All clients are Win2000 pro, XP Pro, or NT4 server SP6a. Are there any
Issues with these?

Frances [MSFT] · Guest

Hello Glyn,

Your plan to play an in-place upgrade from NT to Windows 2003 seems good.
However, I suggest you install AD-integrated DNS on win2k3 server instead
of making NT host DNS since NT does not fully support DNS.

You can refer to the following articles for more information.
http://www.microsoft.com/technet/community/columns/profwin/pw0302.mspx

In addition, it is better to transfer all Flexible Single-Master Operation
(FSMO) roles to DC2 in the new domain since DC2 is clean installed.

As for you questions, I would like to answer them in sequence.
1. Can I leave my old BDC's running, and decommission them at a later date?
A: Yes. BDCs can be running in the new domain. But they cannot replicate
the whole AD data. It is only in terim.
2. Issues with Exchange 5.5
A: Exchange Server 5.5 is not supported to run in a Windows Server 2003
environment. I suggest you submit exchange related question to newsgroup:
microsoft.public.exchange.setup to get more accurate information about
Exchange.

3. I have MS Proxy server 2 on a BDC and various SQL servers on member
servers, will the se have any issues?

A: No, the upgrade process will not infect them.

4. All clients are Win2000 pro, XP Pro, or NT4 server SP6a. Are there any
Issues with these?
A: No, the upgrade process will not infect them.
As a kind reminder, after the upgrade process, all the Windows 2000/XP
clients may only authenticate with the new Windows Server 2003 DC. Once
win2k3 DC is down, they will not contact BDC for authentication. This issue
is addressed in the KB298713 below. You can consider if you need to add
NT4Emulator registry entry before the upgrade process according to your
real environment since you have 2 windows 2003 DCs.

You can refer to the following articles for more information.
298713 How to prevent overloading on the first domain controller during
domain
http://support.microsoft.com/?id=298713
284937 Windows 2000-based clients connect only to the domain controller that
http://support.microsoft.com/?id=284937

Hope it helps. Any updates, let us get in touch!

Best regards,

Frances He

Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security

=====================================================

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.

=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

Glyn Williams · Guest

Hi,
Thanks for your reply.

A couple of other servers I forgot about is IIS4 on an NT4 sp6a member
server.(Just runs an Intranet) Will this still be ok?
And SMS 2 on a NT4 sp6a BDC. Will this be ok?

I'm guessing these will be ok, as they are just applications on member
servers.

Thanks again,
Glyn

"Frances [MSFT]" <v-franhe@microsoft.com> wrote in message
news:5THAQw88EHA.2944@cpmsftngxa10.phx.gbl...

Frances [MSFT] · Guest

Hello Glyn,

Generally speaking, the upgrade process will not infect the member servers.

Furthermore, there is no known issue about SMS 2 and IIS 4 in a Windows
2003 domain. Just a kind reminder, IIS 4 on NT 4 is no longer supported
after 1/1 2005.

However, it depends on your real environment since you might have developed
any third-party application which relies on IIS, which cannot work in
win2k3 enviornment.

Any updates, let us get in touch!

Best regards,

Frances He

Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security

=====================================================

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.

=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

	Windows Server Forum Index -> Migration	All times are GMT
Page 1 of 1