Moving SBS 2000 domain to new 2003 R2 Server

brianx2t
brianx2t used Ask the Experts™
on
We recently bought a new and more powerful server in order to run Microsoft Great-Plains accounting software. The new server is running Server 2003 R2 Standard Edition 32bit and was simply added to our current SBS 2000 domain as a second DC. We have since transferred any necessary apps to the new server having done away with Exchange Server in favour of mDaemon. I now want to decomission the old SBS 2000 server and transfer all domain management and server roles to the new 2003 server but running DCPROMO on the old server fails, saying that it 'Failed finding a suitable domain controller for the domain xxxx.co.uk'  and that the 'specified domain either does not ecist or could not be contacted'. DNS is working fine on both machines, and I've pointed the SBS 2000 DNS to each server in turn to try and alleviate the problem, but still I cannot demote the SBS server. BTW I have also flagged the new server as GC and removed it from the old server.
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®

Commented:
You are doing it Completely wrong.
You have to follow the migration steps to do this. SBS Domain is very different from Windows 2003 or 2000 domain and cannot be decomission the way you think.
http://www.microsoft.com/windowsserver2003/sbs/upgrade/default.mspx
http://download.microsoft.com/download/6/d/c/6dccf9b4-d915-4c95-b5af-100b89e02add/SBS_MigratingSBS2k.doc 

Good luck!
Principal Consultant
Most Valuable Expert 2016
Top Expert 2014
Commented:
Did you also buy Server 2003 Core CALS for all of your users?  Because your current SBS CALs will no longer be valid.

Additionally, if you were using Outlook XP without a full Office Suite license, you'll have to discontinue using that too.

You will not be able to demote the SBS server, but if you've added the new Server 2003 as a DC and your AD has fully replicated, added it as a GC Server, then you can sieze the FSMO roles.  That's done by shutting off the SBS 2000 and never turning it back on in the domain again, and following this KB article http://support.microsoft.com/kb/255504 to seize the roles.

You need to be running DNS and DHCP on your new server as well.  After seizing the FSMO roles you'll have to manually tidy up the AD and DNS to remove any references to the old server.  It's a VERY messy project and one that I'd never attempt in the manner in which you are doing.

Jeff
TechSoEasy

Author

Commented:
Many thanks TechSoEasy, it looks as though yours is the route I need to take. Unfortunately the new server is very much up-and-running, otherwise I am now aware of some much easier routes. The new server has its own CALs, and all users are running seperately licensed Office software, so licensing is not an issue. DNS is running on the new server, but DHCP is handled by the router - is this likely to be an issue?
Bootstrap 4: Exploring New Features

Learn how to use and navigate the new features included in Bootstrap 4, the most popular HTML, CSS, and JavaScript framework for developing responsive, mobile-first websites.

Jeffrey Kane - TechSoEasyPrincipal Consultant
Most Valuable Expert 2016
Top Expert 2014

Commented:
Well, unfortunately, the other route was not only easier... but MUCH less expensive.  Plus by not upgrading to SBS 2003 you've missed out on the greate features like integrated SharePoint and Remote Web Workplace.  

At any rate... keeping DHCP on the router won't hurt.

Jeff
TechSoEasy

Author

Commented:
Can you point me in the right direction for sorting out AD? The DNS should be simple enough (assuming I just remove any references to the old server).

Author

Commented:
Sorry, I asked too soon - it's all in the MS document.

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial