NT4 to Active Directory 2003 Qs
Mike
I have several migration questions for a NT 4 migration:
I plan to migrate to AD 2003 in the following way:
-Add BDC to NT 4 domain, remove from production network and promote as PDC.
-Upgrade PDC to Win2003R2.
-Build a permanent Domain controller on Win2003R2 sync with upgraded
Win2003R2, then remove the upgraded machine.
-If i Have the Win2003R2 on the same network as teh original NT4 system will
this cause conflict?
-Would I be best keeping the production and migration networks separate and
have the new Win2003R2 system have the same IP as the NT4 PDC?
-Will the XP PCs need to be re-joined to the domain or will their accounts
carry to Active Directory?
-Will the XP client domain name need to be chaned from domainname to
domainname.local or will this migration not change the domain name to
.local?
Thanks for the answers in advance?
Mike
Paul Bergson
and do an in place upgrade. You can leave the NT4 machines in place (member
server or bdc's) on the network as long as you like you just can't upgrade
to DFL/FFL 2003 until you remove the BDC's, but you can leave member servers
as long as you like.
If you change the domains you will need to join these XP machine to the new
domain. If you upgrade you shouldn;t have to.
--
Paul Bergson
MVP - Directory Services
MCTS, MCT, MCSE, MCSA, Security+, BS CSci
2008, 2003, 2000 (Early Achiever), NT4
Please no e-mails, any questions should be posted in the NewsGroup This
posting is provided "AS IS" with no warranties, and confers no rights.
"Mike" <nos...@test.com> wrote in message
news:%233l9KEg...@TK2MSFTNGP04.phx.gbl...
Mike
Thanks for your response. I didn't type my intentions clearly. I'm
planning on doing an in-place upgrade, but thought it best I use a temporary
machine to be the NT4 BDC that syncs SAM, then I remove it, promote to PDC,
then do in-place upgrade. This machine would be a temporary machine and
would sync AD to a permanet Win2003 domain controller with the same IP as
the original PDC. This way doing everything off-line and separate from the
production network making testing/troubleshooting easier. Also, my clients
could have same WINS server and DNS server references.
If I do an in-place upgrade,
-The AD domain name will be the same correct? (in other words it will not
be a FQDN such as domain.local)? I'm assuming this is the case if I won't
have to change the workstation domain (by re-joining the new domain.local).
Thanks for the answers I've never done a NT4 -> AD migration, just AD->AD,
and my NT 4 memories are rusty (haven't used since 2001)
Thanks,
Mike
"Paul Bergson" <pbb...@nospammsn.com> wrote in message
news:73742E4C-8B7F-4DB3...@microsoft.com...
Massimo
news:%233l9KEg...@TK2MSFTNGP04.phx.gbl...
> I plan to migrate to AD 2003 in the following way:
> -Add BDC to NT 4 domain, remove from production network and promote as
> PDC.
> -Upgrade PDC to Win2003R2.
> -Build a permanent Domain controller on Win2003R2 sync with upgraded
> Win2003R2, then remove the upgraded machine.
The right steps are as following:
- Upgrade (in-place) the PDC to Windows 2003
- Add Windows 2003 DCs
- Remove (or upgrade) all NT4 BDCs
The member computers (servers/clients) aren't going to notice any
difference, the domain account database will remain the same and everything
will work smoothly.
The only problem with this approach is, NT4 and Windows 2003 usually run on
quite different hardware, so maybe your NT4 PDC won't support an in-place
upgrade; even if it did, you'll have an unclean installation, and some
limitations, like the system partition that on NT4 can be at most 4GB in
size. To overcome these problems, usually this is the standard approach:
- Get a temporary machine which can run NT 4 and Windows 2003 (a virtual
machine is a perfect tool here)
- Install NT4 as BDC and promote to PDC
- Upgrade (in-place) the machine to Windows 2003
- Install as many new Windows 2003 domain controllers as you wish, this time
using production hardware
- Remove the NT4 BDCs
- Demote and remove the temorary machine
You really shouldn't disconnect any DC (NT and/or 2003) from the network: if
you do upgrade operations offline, you'll end up with two different domains,
you won't be able to resync them and you'll have to manually migrate the
member computers.
Massimo
Jorge de Almeida Pinto [MVP - DS]
for both see:
UPGRADE:
http://blogs.dirteam.com/blogs/jorge/archive/2006/05/01/Example-NT4-to-AD-upgrade.aspx
MIGRATION: http://blogs.dirteam.com/blogs/jorge/search.aspx?q=ADMT&p=1
--
Cheers,
(HOPEFULLY THIS INFORMATION HELPS YOU!)
# Jorge de Almeida Pinto # MVP Identity & Access - Directory Services #
BLOG (WEB-BASED)--> http://blogs.dirteam.com/blogs/jorge/default.aspx
BLOG (RSS-FEEDS)--> http://blogs.dirteam.com/blogs/jorge/rss.aspx
------------------------------------------------------------------------------------------
* This posting is provided "AS IS" with no warranties and confers no rights!
* Always test ANY suggestion in a test environment before implementing!
------------------------------------------------------------------------------------------
#################################################
#################################################
------------------------------------------------------------------------------------------
"Mike" <nos...@test.com> wrote in message
news:#3l9KEgY...@TK2MSFTNGP04.phx.gbl...
Mariusz Kruk
epsilon$ while read LINE; do echo \>"$LINE"; done < "Mike"
>Hi,
>
>I have several migration questions for a NT 4 migration:
>
>I plan to migrate to AD 2003 in the following way:
>-Add BDC to NT 4 domain, remove from production network and promote as PDC.
>-Upgrade PDC to Win2003R2.
>-Build a permanent Domain controller on Win2003R2 sync with upgraded
>Win2003R2, then remove the upgraded machine.
Can't you do it just the "official way"?
You should set up a new AD domain, then create trust relationship
between domains, migrate users/machine accounts using ADMT and voila.
--
Kruk@ -\ | Microsoft Office 2000: Ach, jak wygodnie
}-> epsilon.eu.org |
http:// -/ |
|
Massimo
news:slrngkoe58.4b...@epsilon.rdc.pl...
> Can't you do it just the "official way"?
> You should set up a new AD domain, then create trust relationship
> between domains, migrate users/machine accounts using ADMT
> and voila.
...why?!?
Massimo
Meinolf Weber [MVP-DS]
Additional see here:
http://www.microsoft.com/windowsserver2003/evaluation/whyupgrade/nt4/nt4domtoad.mspx
Best regards
Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
Paul Bergson
stay the same. So you will have to ways to refer to the domain netbios and
fqdn. You won;t have to do anything to the existing clients.
--
Paul Bergson
MVP - Directory Services
MCTS, MCT, MCSE, MCSA, Security+, BS CSci
2008, 2003, 2000 (Early Achiever), NT4
Please no e-mails, any questions should be posted in the NewsGroup This
posting is provided "AS IS" with no warranties, and confers no rights.
"Mike" <nos...@test.com> wrote in message
news:OPj0begY...@TK2MSFTNGP02.phx.gbl...