titanax
asked on
How to migrate NT 4.0 to 2K3 DC without clients rejoining domain
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?
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?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
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?
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?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
ok getting it...
So the promotion process begins on the SWAPfrom BDC to PDC. This automactically demotes my present PDC to BDC, yes?
So the promotion process begins on the SWAPfrom BDC to PDC. This automactically demotes my present PDC to BDC, yes?
ASKER
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?
My DNS & DHCP services reside on 2 separate member NT servers; not on the PDC - do I have to make any provisioning for this?
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
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
ASKER
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 ?
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 ?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
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?
Will this be a problem when I do FSMO? Will the clients be affected?
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.
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.
ASKER
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?
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?
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.
ASKER
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 !!
Thank you for the detailed explanations...if I could give you 1000 points I would !!
ASKER