Old Windows 2003 Server and New Windows 2008 Server
I have an old server(Server1) running Win Server 2003 that needs to be replaced, set as domain.old.local(IP 192.168.0.5). I have a new server(Server2) that is running Win Server 2008 that is set as new.local(IP 192.168.0.242). From a XP Pro workstation that is set as a workstation I can ping the new server with the "ping 192.168.0.242" fine, but if I try "ping new.local" it fails. All I'm trying to do is have one XP workstation join the new domain, but I keep getting domain not found when I try to join the new.local domain. Any ideas?
November 4th, 2009 6:02am

Hi Loperzrx, Thank you for posting in windows server forums, Please provide unedited ipconfig /all from server(DC ) and the client I see a potential name resolution issue, for troubleshooting further please do also provide the event logs which are of suspect .
Free Windows Admin Tool Kit Click here and download it now
November 4th, 2009 7:28am

Hello,doyou really like to configure everything new with the 2008 machine installed with a new domain name? If yes ignore my posting, otherwise follow the next steps to add the 2008 machine to the existing domain and keep all information about users, computers and group policies etc.:!!!NEVER START BEFORE HAVING CREATED AND TESTED A BACKUP OF YOUR DATA/MACHINE!!! - Do you use any kind of Exchange in the 2003 domain? If yes, which one? - On the old server open DNS management console and check that you are running Active directory integrated zone (easier for replication, if you have more then one DNS server) - run replmon from the run line or repadmin /showrepl(only if more then one DC exist), dcdiag and netdiag from the command prompt on the old machine to check for errors, if you have some post the complete output from the command here or solve them first. For this tools you have to install the support\tools\suptools.msi from the 2003 installation disk. - run adprep /forestprep and adprep /domainprep and adprep /rodcprep from the 2008 installation disk against the 2003 schema master(forestprep) / infrastructure master(domainprep/rodcprep), with an account that is member of the Schema/Enterprise/Domain admins, to upgrade the schema to the new version (44) or 2008 R2 (47) - you can check the schema version with "schupgr" or "dsquery * cn=schema,cn=configuration,dc=domainname,dc=local -scope base -attr objectVersion" without the quotes in a command prompt - Install the new machine as a member server in your existing domain - configure a fixed ip and set the preferred DNS server to the old DNS server only, think about disabling IPv6 if you are not using it, some known problems exist with it. Follow (http://blogs.dirteam.com/blogs/paulbergson/archive/2009/03/19/disabling-ipv6-on-windows-2008.aspx) to disable it - run dcpromo and follow the wizard to add the 2008 server to an existing domain, make it also Global catalog and DNS server. - for DNS give the server time for replication, at least 15 minutes. Because you use Active directory integrated zones it will automatically replicate the zones to the new server. Open DNS management console to check that they appear - if the new machine is domain controller and DNS server run again replmon, dcdiag and netdiag (copy the netdiag from the 2003 to 2008, will work) on both domain controllers - Transfer, NOT seize the 5 FSMO roles to the new Domain controller (http://support.microsoft.com/kb/324801 applies also for 2008), FSMO should always be on the newest OS DC - you can see in the event viewer (Directory service) that the roles are transferred, also give it some time - reconfigure the DNS configuration on your NIC of the 2008 server, preferred DNS itself, secondary the old one - if you use DHCP do not forget to reconfigure the scope settings to point to the new installed DNS server - if needed export and import of DHCP database for 2008 choose "netshell dhcp backup" and "netshell dhcp restore" command (http://technet.microsoft.com/en-us/library/cc772372.aspx) Demoting the old DC - reconfigure your clients/servers that they not longer point to the old DC/DNS server on the NIC - to be sure that everything runs fine, disconnect the old DC from the network and check with clients and servers the connectivity, logon and also with one client a restart to see that everything is ok - then run dcpromo to demote the old DC, if it works fine the machine will move from the DC's OU to the computers container, where you can delete it by hand. Can be that you got an error during demoting at the beginning, then uncheck the Global catalog on that DC and try again - check the DNS management console, that all entries from the machine are disappeared or delete them by hand if the machine is off the network for ever - also you have to start AD sites and services and delete the old servername under the site, this will not be done during demotionBest regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties, and confers no rights.
November 8th, 2009 10:53pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics