?
Solved

How to migrate NT 4.0 to 2K3 DC without clients rejoining domain

Posted on 2006-05-17
15
Medium Priority
?
328 Views
Last Modified: 2010-04-18
We are about to decomm our NT 4.0 PDC & bring in our 2K3 DC. I have setup it up with the same IP, same machine name & domain name.

How can my clients (XP) logon to the new DC without me having to rejoin them into the 2k3 domain. Is there some SID thingy here?
0
Comment
Question by:titanax
  • 8
  • 7
15 Comments
 

Author Comment

by:titanax
ID: 16697712
corrections: only the machine name is different, the domain is the same.
0
 
LVL 33

Accepted Solution

by:
NJComputerNetworks earned 2000 total points
ID: 16698713
Yeah...uh, you can't just set up a new domain with the same name and IP and expect these client machine to function in the domain....  This simply would not work...

This is what you need to do...

-Get a desktop machine...  install Windows NT 4.0 as a BDC of your existing NT domain.  This machine is just temporary and I will call this a SWAP machine.
-Install the SP6 on both your NT 4.0 DCs...
- Promote the WinNT SWAP BDC to be PDC of the domain
- Replicate the domain
- (take your old PDC offline...and save this in case you have a failure of your upgrade....)
- Insert a Windows 2003 CD in the SWAP desktop and choose inplace upgrade.. (This will upgrade the domain as well to Windows 2003)
- After the inplace upgrade takes place...you can install Windows 2003 on your real server hard ware.
- Join this server to the windows 2003 domain
- Run DCPROMO to promote this server to a domain controller
- Install the DNS service.
- Enable this new DC as global catalog -- http://www.microsoft.com/windows2000/en/advanced/help/default.asp?url=/windows2000/en/advanced/help/DSSite_enable_GC_server.htm
- Transfer all the FSMO roles to this new server http://support.microsoft.com/default.aspx?kbid=324801&product=winsvr2003
- Run DCPROMO on the old SWAP desktop DC...and choose to remove this server as a domain controller.
- Then remove this server from the domain...  and turn it off...it is no longer needed.
- Make sure all of your internal clients are pointing to the new Windows 2003 DC for DNS resolution....



0
 

Author Comment

by:titanax
ID: 16700094
NJ - pls bear with me here...

How do I:
- -Install the SP6 on both your NT 4.0 DCs... <-- how do I check the sp version installed on the NT 4?
- Promote the WinNT SWAP BDC to be PDC of the domain?
- Replicate the domain?

"- After the inplace upgrade takes place..." <-- you didn't mention doing a DCPROMO on the SWAP, does the inplace upgrade automatically make it a DC?

0
VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

 
LVL 33

Assisted Solution

by:NJComputerNetworks
NJComputerNetworks earned 2000 total points
ID: 16700228
"- After the inplace upgrade takes place..." <-- you didn't mention doing a DCPROMO on the SWAP, does the inplace upgrade automatically make it a DC? ---> YES

- -Install the SP6 on both your NT 4.0 DCs... <-- how do I check the sp version installed on the NT 4?  (Run  -> WINVER or during boot on the blue screen the SP will display)
- Promote the WinNT SWAP BDC to be PDC of the domain?  (Do this in Server MAnager....highlight the BDC and choose PROMOTE to PDC on file bar...  Or you might be able to right click the BDC ...can't remember)
- Replicate the domain?  (Do this in Server MAnager.... highlight the DC and synchronize domain)
0
 

Author Comment

by:titanax
ID: 16705269
ok getting it...

So the promotion process begins on the SWAPfrom BDC to PDC. This automactically demotes my present PDC to BDC, yes?
0
 
LVL 33

Expert Comment

by:NJComputerNetworks
ID: 16708091
yes
0
 

Author Comment

by:titanax
ID: 16719247
Will the transition affect the clients - will it cause a downtime & hence best done after hours?

My DNS & DHCP services reside on 2 separate member NT servers; not on the PDC - do I have to make any provisioning for this?
0
 
LVL 33

Expert Comment

by:NJComputerNetworks
ID: 16719615
DHCP can stay on the NT 4.0...  but DNS must be on the Windows 2003 machine.  How are you using DNs in NT 4.0 environment?  Do you have linux or Unix machines registered in DNS?  If so, you will have to add these entries on your new Windows 2003 server (and point your Windows members of the domain to the Windows 2003 DNS).

DNS is a requirement for Active Directory...and NT 4.0 DNS is not compatible.  So, you will have to move DNs to the new Windows 2003 machine.  When you run DCPROMO on the Windows 2003 server, make sure that your TCP/IP settings does NOT point to the Windows NT server.  Instead, before you run DCPROMO, set DNS 1 to 127.0.0.1 or to the IP address of itself.  Only then, should you run DCPROMO.  

DCPROMO will detect that DNS is not running on the Windows 2003 server and install it and configure it for DNS automatically through the DCPROMO wizard.

After DCPROMO is run, you can manually add any DNS records to this server that you have running on your Windows NT 4.0 DNS server.

-later  
0
 

Author Comment

by:titanax
ID: 16740438
As I posted earler: "My DNS & DHCP services reside on 2 separate member NT servers"

I do not have any linux or unix machines, but I do have quite a bit other entires (eg: 1 entry point to our intranet abroad & the other to our Notes server) - there are no documentations for this.

Right now I have already built SWAP as a PDC, but C:\ is only 4MB so I'm thinking of using Powerquest Volume Manager to resize it.

I'm also considering migrating the DNS service to the BDC 1st then promote it to a PDC. My idea is during the W2K3 upgrade, the DNS gets upgraded too...is this valid?

How do I migrate the DNS server & all its entries to the BDC ?
0
 
LVL 33

Assisted Solution

by:NJComputerNetworks
NJComputerNetworks earned 2000 total points
ID: 16741753
0
 

Author Comment

by:titanax
ID: 16796818
1 other question (almost there, I think)...my existing NT domain name is "NORTHWINDS" & the new DC I'm buIlding has a different domain name "NORTHWINDS.LOCAL"

Will this be a problem when I do FSMO? Will the clients be affected?
0
 
LVL 33

Expert Comment

by:NJComputerNetworks
ID: 16797731
No, this is not a problem....  In NT 4.0 domains, only a Netbios domain can be used (i.e. Northwinds).  However, in Windows 200x, a domain is known by two names:  The Netbios domain name (i.e. Northwinds) and the Fully Qualified Domain Name (i.e. Northwinds.local).  

The FQDN, northwinds.local is created because Windows 200x domains have an updated resolution mechanism (DNS) and an updated domain database (Active Directory).

Any Windows 2000 or higher operating system in a Windows 200x domain will primarily use the FQDN name of the domain. These clients rely on DNS functionality to "talk" to the domain.  This is why it is very important to install internal Windows 200x DNS in your domain.  Secondarily, they will use the Netbios domain name.  Windows NT 4.0 and Win9x clients will use the NetBios name of the domain.

In any case, there will be no problem in your environment with the names that you are using.  This is totally normal.
0
 

Author Comment

by:titanax
ID: 16852091
got it, noticed that on some of our the clients show pcxx.northshore. while some others show pcyy.northshore.local.

WRT the SWAP, do I really need to demote - dcpromo it? Can't I just shut it down & remove off the LAN after the FMSO?

0
 
LVL 33

Expert Comment

by:NJComputerNetworks
ID: 16852339
If you just shut down the DC...without DCPROMO... the swap DC will remain in AD.  This will cause replication problems as the other DC will still continue to try to replicate data to it.  This is why the DCPROMO is needed to clean out AD.
0
 

Author Comment

by:titanax
ID: 16883284
NJ, you have been brillant! My network has been successfully migratied with 0 casualties...couple of stragglers...but DNS tweaks sorted those out!!

Thank you for the detailed explanations...if I could give you 1000 points I would !!
0

Featured Post

Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

So you have two Windows Servers and you have a directory/folder/files on one that you'd like to mirror to the other?  You don't really want to deal with DFS or a 3rd party solution like Doubletake. You can use Robocopy from the Windows Server 200…
While rebooting windows server 2003 server , it's showing "active directory rebuilding indices please wait" at startup. It took a little while for this process to complete and once we logged on not all the services were started so another reboot is …
Integration Management Part 2
How can you see what you are working on when you want to see it while you to save a copy? Add a "Save As" icon to the Quick Access Toolbar, or QAT. That way, when you save a copy of a query, form, report, or other object you are modifying, you…

621 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question