Tom's Guide | Tom's Hardware | Tom's Games
![]() |
![]() |
![]() |
Currently we have a NT PDC and an NT BDC. We are installing a new file server with Windows 2000 Server. I'm wondering if it makes sense to enable the new server with Active Directory and make it our PDC. Will this be a problem if our BDC is an NT server? What problems can we expect? Or, should we stick with the NT Server as the PDC until we get the other server to Windows 2000?
Thanks.

To answer one question forthright, Win2K has a PDC "emulator" capability for just the reason you ask. If you upgrade the NT PDC to Win2K, the new OS will "act" as the PDC for the rest of the migration. That is, *IF* you want to make the Domain a native Win2K Domain.
Look here for more info :)
http://www.win2000mag.com/Articles/Index.cfm?ArticleID=7736

A few things are not right here. You say you are installing a new server and ask "if it makes sense to enable the new server with Active Directory and make it our PDC". Well, you can't. You can not install a new Windows 2000 server as a domain controller into an existing NT domain. If you want to maintain your current NT domain and convert it to a Win2k Active Directory domain your only option is to upgrade the NT PDC to Windows 2000. You can then install additional w2k servers into the domain and make them domain controllers if you wish. You can continue to use NT BDCs in a W2k domain that is in mixed mode - the default. When all DCs are converted to w2k you can then switch the domain to native mode if you choose.
There is a PDC emulator as Jinx mentions. Amoung other things it will act as the PDC to NT BDCs when in mixed mode. The PDC emulator is still required even in a native mode domain.
Hope that helps. Good luck.

![]() |
![]() |
![]() |

This post is quite old and has been locked from receiving new replies. Please create a new posting instead.
| Ads by Google |