risoy
asked on
NT4 upgrade to W2k3, PDC delegation to a fresh W2k3
We've got an NT4 PDC and want to upgrade to Windows 2003. I understand that the best procedure is to install a fresh NT4 BDC, promote it to PDC and upgrade to Windows 2003 Server.
I reckon it must be better running off a non-upgraded machine. So, can I install Windows 2003 Server on a third machine (the one I want it to run on eventually) and promote this one to be PDC and discard the temporary upgraded NT4?
Hope you understood my question :-)
I reckon it must be better running off a non-upgraded machine. So, can I install Windows 2003 Server on a third machine (the one I want it to run on eventually) and promote this one to be PDC and discard the temporary upgraded NT4?
Hope you understood my question :-)
ASKER
But can I do this process on another computer than the one I want it to eventually be running on.
I understand there is no such thing as PDC/BDC on Windows Server 2003?
I currently have only one PDC and a server with Windows 2003 that is not yet configured as Domain Controller. If I install NT on a third computer (not my PDC and not my Windows 2k3) as BDC. Disconnect my original PDC, promote my new BDC to PDC. Upgrade to Windows Server 2003. Is there now anything that needs to be transferred between my new Windows 2003 and the one I have allready prepared?
I understand there is no such thing as PDC/BDC on Windows Server 2003?
I currently have only one PDC and a server with Windows 2003 that is not yet configured as Domain Controller. If I install NT on a third computer (not my PDC and not my Windows 2k3) as BDC. Disconnect my original PDC, promote my new BDC to PDC. Upgrade to Windows Server 2003. Is there now anything that needs to be transferred between my new Windows 2003 and the one I have allready prepared?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Well, the process described is a little off. You need to install the new BDC, promote it while the the old PDC is still online so it can transfer roles. Then upgrade the new PDC (third machine) to Win2003. This will create the domain and you can have it in mixed (NT4 and 2k3) mode. No turn off the old NT4 machine. Then rename the one you want to be 2K3 for good to the old name and then promote it to be a DC, transfer FSMO roles, dcpromo the temporary machine. You should be all set at that point.
ASKER
> Then rename the one you want to be 2K3 for good to the old name
Can't I give it a new name?
Can't I give it a new name?
You can, it sounded like you wanted to keep it the same which simplifies dealing with client machines and drive mappings and such. If that won't be an issue you can name the new one whatever you'd like.
ASKER
I see. I probably do, just wanted to check if there were any limitations.
> transfer FSMO roles
Is there a simple procedure on how to do this?
> transfer FSMO roles
Is there a simple procedure on how to do this?
It is 5 roles.... and the corresponding snap-in for each. For details please use Help on the server.
PDC emulator from Active Directory Users and Computers
Infrastructure Master from Active Directory Users and Computers
Domain Naming Master from Active Directory Domains and Trusts
Relative ID Master from Active Directory Users and Computers
Schema Master from Active Directory Schema
PDC emulator from Active Directory Users and Computers
Infrastructure Master from Active Directory Users and Computers
Domain Naming Master from Active Directory Domains and Trusts
Relative ID Master from Active Directory Users and Computers
Schema Master from Active Directory Schema
ASKER
Should there be any problems upgrading while other users are connected?
After I have promoted the new machine to PDC, can I disconnect it from the newtwork and then upgrade to W2k3? Should there be a problem for the users running off the BDC?
Is the BDC then backup for the new W2k3 machine? Or do they have compatibility problems?
After I have promoted the new machine to PDC, can I disconnect it from the newtwork and then upgrade to W2k3? Should there be a problem for the users running off the BDC?
Is the BDC then backup for the new W2k3 machine? Or do they have compatibility problems?
If you users see only an BDC in network they can not change any password and you will can not create any new accounts. The network will remain opperational in this time.
Afther the new w2k3 server will join to the network you will perform an clean reinstall for any BDC, and then run dcpromo.
Afther the new w2k3 server will join to the network you will perform an clean reinstall for any BDC, and then run dcpromo.
Be carefoul at DNS! make the DNS AD integrated. If you lose the DNS you lose de domain...
ASKER
I struggle a little with the naming conventions.
Currently our domain is named COMPANYNAME
But changing the domain name is only applicable to a fresh install i suppose. But in that case, should it be COMPANYNAME.COM or ROOT.COMAPNYNAME.COM, or one domain per location, say LONDON.COMPANYNAME.COM and PARIS.COMPANYNAME.COM?
Currently our domain is named COMPANYNAME
But changing the domain name is only applicable to a fresh install i suppose. But in that case, should it be COMPANYNAME.COM or ROOT.COMAPNYNAME.COM, or one domain per location, say LONDON.COMPANYNAME.COM and PARIS.COMPANYNAME.COM?
In W2k and W2k3 you will have 2 name. One dns name that is like company.com and another NetBIOS name COMPANY. I sugest to use name .local not .com. This long name (or FQDN) can be changed at install or upgrade and should reflect your network topologies.
ASKER
If I want localization in the naming structure I can do this by assigning a primary DNS suffix of f.ex. LONDON.COMPANYNAME.COM, whilst leaving the domain common for all locations?
Found quite a good article here:
- http://www.microsoft.com/windows2000/techinfo/reskit/en-us/default.asp?url=/windows2000/techinfo/reskit/en-us/cnet/cncf_imp_TYHP.asp
Found quite a good article here:
- http://www.microsoft.com/windows2000/techinfo/reskit/en-us/default.asp?url=/windows2000/techinfo/reskit/en-us/cnet/cncf_imp_TYHP.asp
ASKER
Thanks for the help.
Yes it is possible. I have try this with W2k before. I have install an BDC, then I disconnect the pdc from network. I have promoted the fresh BDC as PDC, then I install W2kServer. If the test was a failure, I just have to remove the Win2kServer and reconnect the old PDC. But this is OK only if you dont have another BDC. If is more BDC in network you should disconnect this computer form network.
Good luck.
Dan
MSCE MCSA