There several unbreakable rules that you must deal with when migrating from NT4 to Win2K (and from Exchange 5.5 to Exchange 2000):
1. Installing Active Directory (AD) on any Win2K server automatically creates an Active Directory (AD) Domain Controller (DC).
2. A Win2K DC CANNOT exist in an NT4 domain.
3. An NT4 PDC CANNOT exist in a Win2K AD domain (although an NT4 BDC can).
4. To migrate an NT4 Domain to Win2K and AD, you MUST install Win2K and AD on an NT4 PDC (will not work on a BDC).
5. Exchange 2000 MUST have access to an AD DC (but it doesn't need to be installed on a DC).
Given that you don't want to upgrade your current PDC, you really have 3 options:
1. Create a separate Win2K domain and Exchange2K organization and recreate accounts (and mailboxes) from scratch. This option is really dependant on the total number of users you have and the stability of your current NT domain and Exchange organization. While this option might take more work, if you are currently experiencing any ongoing problem with either NT4 or Exchange, this might be the cleaner way to go (i.e. you won't be tranferring any problems from your old domain/Exchange organization to the new one.)
2. Upgrade your current PDC enough to perform a standard domain/Exchange migration/upgrade. Install Win2K/AD/Exchange on your new server as and additional DC and Exchange server. Transfer all FSMO rolls from your old server to the new one and demote the old DC. Move mailboxes form one Exchange2K server to the other. Decommision the old server .
(continued)