Since I was having so much trouble moving to a new PDCe I decided to format and start fresh using the procedure suggested by a previous answer:
http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Server/2000_Server/Q_23066450.html ID:20608985Author:KCTSDate
:01.08.200
8 at 06:50AM PSTExpert Comment
Rank: Sage
Is this what you were looking for?Yes No
KCTS:
For a start you should not have seized the FSMO roles - you should have transferred them - seizing should only be a last restort data loss can result
You have also missed making the new server a global catalog and of course all of your clients need to be pointed at the new machine for their preferred DNS server if the old server is being removed.
The proper procedure is as follows:-
First install Windows 2003 on the new machine
Assign the new computer an IP address and subnet mask on the existing network
Make sure that the preferred DNS server on new machine points to the existing DNS Server on the Domain (normally the existing domain controller)
Join the new machine to the existing domain as a member server
From the command line promote the new machine to a domain controller with the DCPROMO command from the command line Select "Additional Domain Controller in an existing Domain"
Once Active Directory is installed then to make the new machine a global catalog server, go to Administrative Tools, Active Directory Sites and Services, Expand, Sites, Default first site and Servers. Right click on the new server and select properties and tick the Global Catalogcheckbox. (Global catalog is essential for logon as it needs to be queried to establish Universal Group Membership)
Install DNS on the new server. Assuming that you were using Active Directory Integrated DNS on the first Domain Controller, DNS will automatically replicate to the new domain controller along with Active Directory.
Dont forget to set the default gateway (router) and DNS Servers. Talking of which all the clients (and the domain controllers themselves) need to have their Preferred DNS server set to the new domain controller
Next move the FSMO roles to the new DC as described in
http://www.petri.co.il/transferring_fsmo_roles.htmYou can now demote the Old DC by running DCPROMO on them to remove Active Directory.
I followed everything to the letter. . .
I ran dcdiag and for the following error:
Starting test: NetLogons
Unable to connect to the NETLOGON share! (\\DOMAIN2B\netlogon)
[DOMAIN2B] An net use or LsaPolicy operation failed with error 1203, No
network provider accepted the given network path..
......................... DOMAIN2B failed test NetLogons
Starting test: Advertising
Warning: DsGetDcName returned information for \\server.server
s, when we were trying to reach DOMAIN2B.
Server is not responding or is not considered suitable.
Warning: DOMAIN2B is not advertising as a time server.
Now what?
