Sign in with
Sign up | Sign in
Your question

NT4 Domain and 2003 AD together

Last response: in Windows 2000/NT
Share
May 29, 2005 10:09:31 PM

Archived from groups: microsoft.public.windowsnt.domain (More info?)

Hi,

Our current Windows network is NT4 PDC with 2 BDC. I'll be setting up our
remote office in UK in few weeks and I'd like to know if I can use Server
2003 to set up Active Directory for the office in UK while retain
communications to the existing NT4 domain. Basically, when they browse "My
Network Places", they'll be able to see both domains and access accordingly
based on their permissions.

We use CheckPoint VPN firewall and the UK office will have a CheckPoint
appliance for firewall and routing. The CheckPoint will also provide DHCP.

As far as I know, if I set up AD, the server must run DNS? The UK office
will have a few Linux/Unix computers and we'd like to use Unix for DNS.

Our corporate network consists of about 600 nodes, where the UK is about 10
nodes.

Thanks for your advise,

Simon

More about : nt4 domain 2003

Anonymous
May 30, 2005 2:47:12 PM

Archived from groups: microsoft.public.windowsnt.domain (More info?)

Hi Simon,

Thanks for the posting!

I have read the thread you posted in both microsoft.public.windowsnt.domain
and the microsoft.public.windows.server.active_directory newsgroups, and
understand you plan to configure the remote site win2k3 server.

Since you need to go oversea to configure the remote win2k3 site and this
question may require a bit more in depth attention and may fall under the
umbrella of Advisory Services. You may consider contacting Microsoft
Advisory Services to get more information. For more information on Advisory
Services, please see the following URL:
http://support.microsoft.com/Directory/WORLDWIDE/EN-AU/...

You may also contacting Microsoft phone support engineer about this
question:
To obtain the phone numbers for a specific technology request please take a
look at the web site listed below.
http://support.microsoft.com/default.aspx?scid=fh;EN-US;PHONENUMBERS

If you are outside the US please see
http://support.microsoft.com for regional support phone numbers.

I would like to provide some personal experience about your scenario. It
seems you will set the remote win2k3 in the same domain as NT PDC, I mean
if the NT domain called OldDomain, you plan to add the win2k3 to OldDomain
in the remote site. If this is the case, you need to perform a non-in place
upgrade process in the remote site.

- Install BDC on the new box in the remote site, let us call it
win2k3Machine. Here, please make sure you can ping though between
win2k3Machine and the old NT machine. You need to pay attention to the
firewall to allow the firewall open the port to allow the win2k3Machine can
communicate with old NT PDC.

- Promote a Windows NT 4.0 BDC to the PDC, which demotes the PDC to
a BDC.
- Adding the NT4mulator registry on win2k3 server. This step is
optional but recommend, adding this registry on the win2k3 server will make
the win2k3 server act like a NT server rather than a win2k3 DC. it would be
easier to communicate with NT and the down level clients. You can continue
using Unix DNS in the network as if you are in NT domain.

Configure Protection From Domain Controller Overload
http://www.microsoft.com/technet/prodtechnol/windowsser...
t/4e72dc59-0241-4666-bed9-075b78ba0884.mspx

298713 How to prevent overloading on the first domain controller during
domain
http://support.microsoft.com/?id=298713

- Upgrade the new PDC to Windows Server 2003. If you want to expand
the boot partition, please refer to the following KB:
325857 How To Expand the Boot Partition During a Windows Server 2003 Upgrade
http://support.microsoft.com/?id=325857

- Use the Windows Server 2003 Active Directory wizard to turn on the
Active Directory service. The Active Directory service imports the existing
user accounts, groups, and other settings from the PDC.

IMPORTANT: You can choose the domain function level to use the interim mode
when installing AD on win2k3 server. Your understanding is correct that
interim mode is the correct domain function level when win2k3 and NT
coexists in the network. However, if you add NT4emualtor registry, you can
use the mixed function level since the win2k3 will act like a NT PDC. For
more details about the Interim mode, please refer to the following article,
" Interim Level - Upgrade from a Windows NT 4.0 Domain ":

How to raise domain and forest functional levels in Windows Server 2003
http://support.microsoft.com/kb/322692

- Install WINS on win2k3Machine and make sure it replicates with the
remote old NT DC for name resolution.

- Run your new Windows Server 2003 domain controller with Active Directory
for a test period.

By using the steps above, you have upgraded the NT domain to the win2k3
domain and retained the domain name. However, please note now the primary
domain controller is win2k3 server in the remote site.

Please know it is possible that there are some problems when you browse My
Network Places in view the remote site due to many factors, one of the
possibility is to pay attention the firewall configuration. It is also
recommend you visit the remote site via UNC like \\win2k3machine instead of
open My Network Places.

With regards to the question of DNS in win2k3 domain, AD-integrated DNS is
recommended, however, you can use Unix DNS as a temporarily workaround. You
may take a look at the following article:
http://www.avidware.net/Linux/Windows-2003-linux-dns-se...

On other hand, win2k3 DNS can also serve Linux or UNIX client, it would be
better than you install AD-integrated DNS and serve for unix client:

How DNS Works
http://www.microsoft.com/technet/prodtechnol/windowsser...
ef/19a63021-cc53-4ded-a7a3-abaf82e7fb7c.mspx

HTH!

If you have any question, please contact Microsoft Advisory service or the
phone support engineer.

Best regards,

Rebecca Chen

MCSE2000 MCDBA CCNA


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.
May 30, 2005 2:47:13 PM

Archived from groups: microsoft.public.windowsnt.domain (More info?)

Hi Rebecca,

Thanks for your reply, much appreciated. I didn't mean to cross-posting but
I wasn't sure which newsgroup is more appropriate for posting my question.

Just to make sure I understand the whole process, I'll list them below:

a) install NT4 onto new server in remote office as BDC (NT4 Domain), ensure
this server can communicate to existing PDC

b) promote remote office BDC as PDC? (is this a necessary step, can it
remain as BDC)

c) install Windows 2003 Server and run dcpromo to promote as Domain
Controller? (not sure about this step, as I've never done it before. Or
during install of W2K3, it will recognize existing domain structure and
upgrade the domain controller during install)

d) apply registry emulator for NT4 onto W2K3 server

e) at this point, can I demote the W2K3 from PDC back to BDC, and elect
another BDC from the main office as PDC?

Thanks again for your help,

Simon


""Rebecca Chen [MSFT]"" <v-rebc@online.microsoft.com> wrote in message
news:zibwxTQZFHA.388@TK2MSFTNGXA01.phx.gbl...
> Hi Simon,
>
> Thanks for the posting!
>
> I have read the thread you posted in both
> microsoft.public.windowsnt.domain
> and the microsoft.public.windows.server.active_directory newsgroups, and
> understand you plan to configure the remote site win2k3 server.
>
> Since you need to go oversea to configure the remote win2k3 site and this
> question may require a bit more in depth attention and may fall under the
> umbrella of Advisory Services. You may consider contacting Microsoft
> Advisory Services to get more information. For more information on
> Advisory
> Services, please see the following URL:
> http://support.microsoft.com/Directory/WORLDWIDE/EN-AU/...
>
> You may also contacting Microsoft phone support engineer about this
> question:
> To obtain the phone numbers for a specific technology request please take
> a
> look at the web site listed below.
> http://support.microsoft.com/default.aspx?scid=fh;EN-US;PHONENUMBERS
>
> If you are outside the US please see
> http://support.microsoft.com for regional support phone numbers.
>
> I would like to provide some personal experience about your scenario. It
> seems you will set the remote win2k3 in the same domain as NT PDC, I mean
> if the NT domain called OldDomain, you plan to add the win2k3 to OldDomain
> in the remote site. If this is the case, you need to perform a non-in
> place
> upgrade process in the remote site.
>
> - Install BDC on the new box in the remote site, let us call it
> win2k3Machine. Here, please make sure you can ping though between
> win2k3Machine and the old NT machine. You need to pay attention to the
> firewall to allow the firewall open the port to allow the win2k3Machine
> can
> communicate with old NT PDC.
>
> - Promote a Windows NT 4.0 BDC to the PDC, which demotes the PDC to
> a BDC.
> - Adding the NT4mulator registry on win2k3 server. This step is
> optional but recommend, adding this registry on the win2k3 server will
> make
> the win2k3 server act like a NT server rather than a win2k3 DC. it would
> be
> easier to communicate with NT and the down level clients. You can continue
> using Unix DNS in the network as if you are in NT domain.
>
> Configure Protection From Domain Controller Overload
> http://www.microsoft.com/technet/prodtechnol/windowsser...
> t/4e72dc59-0241-4666-bed9-075b78ba0884.mspx
>
> 298713 How to prevent overloading on the first domain controller during
> domain
> http://support.microsoft.com/?id=298713
>
> - Upgrade the new PDC to Windows Server 2003. If you want to expand
> the boot partition, please refer to the following KB:
> 325857 How To Expand the Boot Partition During a Windows Server 2003
> Upgrade
> http://support.microsoft.com/?id=325857
>
> - Use the Windows Server 2003 Active Directory wizard to turn on
> the
> Active Directory service. The Active Directory service imports the
> existing
> user accounts, groups, and other settings from the PDC.
>
> IMPORTANT: You can choose the domain function level to use the interim
> mode
> when installing AD on win2k3 server. Your understanding is correct that
> interim mode is the correct domain function level when win2k3 and NT
> coexists in the network. However, if you add NT4emualtor registry, you can
> use the mixed function level since the win2k3 will act like a NT PDC. For
> more details about the Interim mode, please refer to the following
> article,
> " Interim Level - Upgrade from a Windows NT 4.0 Domain ":
>
> How to raise domain and forest functional levels in Windows Server 2003
> http://support.microsoft.com/kb/322692
>
> - Install WINS on win2k3Machine and make sure it replicates with
> the
> remote old NT DC for name resolution.
>
> - Run your new Windows Server 2003 domain controller with Active Directory
> for a test period.
>
> By using the steps above, you have upgraded the NT domain to the win2k3
> domain and retained the domain name. However, please note now the primary
> domain controller is win2k3 server in the remote site.
>
> Please know it is possible that there are some problems when you browse My
> Network Places in view the remote site due to many factors, one of the
> possibility is to pay attention the firewall configuration. It is also
> recommend you visit the remote site via UNC like \\win2k3machine instead
> of
> open My Network Places.
>
> With regards to the question of DNS in win2k3 domain, AD-integrated DNS is
> recommended, however, you can use Unix DNS as a temporarily workaround.
> You
> may take a look at the following article:
> http://www.avidware.net/Linux/Windows-2003-linux-dns-se...
>
> On other hand, win2k3 DNS can also serve Linux or UNIX client, it would be
> better than you install AD-integrated DNS and serve for unix client:
>
> How DNS Works
> http://www.microsoft.com/technet/prodtechnol/windowsser...
> ef/19a63021-cc53-4ded-a7a3-abaf82e7fb7c.mspx
>
> HTH!
>
> If you have any question, please contact Microsoft Advisory service or the
> phone support engineer.
>
> Best regards,
>
> Rebecca Chen
>
> MCSE2000 MCDBA CCNA
>
>
> 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.
>
Related resources
Anonymous
May 30, 2005 2:53:03 PM

Archived from groups: microsoft.public.windowsnt.domain (More info?)

Here are some good readings:
Why Upgrade from Windows NT 4.0 to Windows Server 2003
http://www.microsoft.com/windowsserver2003/evaluation/w...
et.mspx


Upgrading from Windows NT Server 4.0 to Windows Server 2003
http://www.microsoft.com/windowsserver2003/evaluation/w...
03-2.mspx

Windows NT Server - Upgrade/Migrate
<http://www.microsoft.com/technet/prodtechnol/winntas/de...
fault.mspx>

Please also take a look at the thread in
microsoft.public.windows.server.active_directory newsgroup, Jimmy has also
replied in your thread.

Good luck!

Best regards,

Rebecca Chen

MCSE2000 MCDBA CCNA


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.
Anonymous
May 31, 2005 7:47:47 AM

Archived from groups: microsoft.public.windowsnt.domain (More info?)

Hi Simon,

Your plan seems good post in
microsoft.public.windows.server.active_directory
seems good.

For your conveneince, I would like to including the reply in that thread
====================================
However, I still recommend you contact Microsoft phone support or Advisor
as I have suggested last time to get a concert plan.

Personally, I am glad to hear you plan upgrade your corporate office to
Windows 2003 running interim mode, it is better and the process will go
smoothly.

With regards to if you can make win2k3 as a BDC, there is not BDC concept
in win2k3 environment. You can make the remote win2k3 server as the
additional server during the promote process, something like BDC, in the
remote side. Another point is to set the domain function level to interim
mode or mixed mode to allow win2k3 works with NT server.

About the DNS, I have a same opinion with Al, you can migrate Unix DNS to
win2k3 DNS. That would be better.

There are many steps you need to perform, that is the reason I suggest
contact Microsoft phone support to get more detailed information.
========================

HTH!


Best regards,

Rebecca Chen

MCSE2000 MCDBA CCNA


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.
!