Re: Windows NT 4 domain to AD
- From: "Kurt" <lorentzenkurt@xxxxxxxxxxxxxxxxxx>
- Date: Thu, 23 Mar 2006 19:25:28 -0800
There are pros and cons to each. If your old NT4 DC is "ghostable", I'd do
that first. If not, do backups to the point that you can re-install and
restore if all else fails. Hopefully, this is a DC-only or/DC-fileserver and
not an application or exchange server. If you can, you could also bring up
an NT4 BDC as an off-line backup box. I'll tell you, as most will, that
upgrading the DC as the starting point for your new AD domain is the
easiest. Then, as you say, bring up a new DC from scratch, transfer the
roles and demote the old one. I'd download the 180 day eval from MS for the
upgrade or borrow a CD from someone else to make sure it hasn't been
modofied by Dell. Migration from a live NT4 domain to a new AD is a lot
tougher, and more prone to failure IMHO. But the advantage is that if it
fails, your Old PDC is still around. Anyway, good luck and spend some time
researching all of the pros and cons of each method as they relate to your
particular business needs.
....kurt
"Will Kubly" <wkubly@xxxxxxxxx> wrote in message
news:%23zA0xjpTGHA.1728@xxxxxxxxxxxxxxxxxxxxxxx
Hi
I am starting to look into converting or migrating a Windows NT domain to
a Windows 2003 SP1 AD and had a few questions.
It looks like to preserve our current domain setup I can upgrade the NT
domain controller to Windows 2003 to get our first AD controller on.
However this is a 5 year old box that I have replaced with a new box. I
only want to convert it so I can then bring up another AD from our new
2003 servers and then shut this old box down.
1. Can I use a Windows 2003 CD from one of my new Dell server to upgrade
this box and then once I have transfered the roles etc to another licensed
server drop it? Or will using the software CD from another server cause an
issue?
2. I am not sure what DNS to use on this box. When I deal with new AD
domains the DNS is often company.local. However as this is an NT domain
its Company_bender which does not strick me as a DNS name I can use.
Internally my DNS is company.local.
Or I could migrate the NT domain over to one of the 2003 boxes. The tools
and documentation look good. It about 80 IDs and 60 PCs with about 20 PCs
setup across a Site to Site 786 VPN.
It just seems to me that converting is easier except for the software and
DNS issues that I am unsure about. Or is it easier to migrate?
Thanks
Will
.
- References:
- Windows NT 4 domain to AD
- From: Will Kubly
- Windows NT 4 domain to AD
- Prev by Date: Re: Connecting to a domain controller on a different subnet
- Next by Date: RE: Connecting to a domain controller on a different subnet
- Previous by thread: Re: Windows NT 4 domain to AD
- Next by thread: Re: disabled vs expired
- Index(es):
Relevant Pages
|
