We currently have a single domain controller in our Windows 2000 SP4 domain. I'm hoping to find out if the following is possible, and if so, how many problems am I likely to encounter in implementing the following:
1. Add a new domain controller running Windows 2003 Small Business Server. This server will also run a new database program that I need to install that requires SQL.
2. Demote the existing Windows 2000 dc to a backup dc without upgrading the operating system. We currently don't have any failsafes in place should our main dc go down, so I'm hoping this could minimize our exposure in this area.
3. The Windows 2000 dc is currently running Terminal Services in application mode. I would like for this to continue unchanged once the migration to the new SBS server is completed.
Any comments or suggestions on this would be greatly appreciated.
1. Follow this paper to migrate to SBS 2003:
http://go.microsoft.com/fwlink/?LinkId=16414
3. Follow this paper to add a Windows 2000 Server as a Terminal Server: http://sbsurl.com/tss2k
As far as the failsafe situation there are many, many things that could cause problems on a network, and losing a connection to your DC is probably lower down the list in MY order of importance. I've found that as long as you deploy your server on hardware that is appropriate for the job, configure it according to best practices, and maintain it according best practices then you will find that the reliability is excellent.
Additionally, SBS2003 automatically deploys Exchange in Cached Mode which provides a duplicate copy of a person's mailbox locally. If you run the Configure My Documents Redirection wizard, then the My Documents folder will be on the server with a synchronized cached version on their machine as well. Both of these items allow for accessing email and documents should there be a connection problem.
Jeff
TechSoEasy