<div>
<div class="content wysiwyg-content">
We have a situation where we have an SBS 2000 server carrying on a variety of tasks - it acts as the Terminal Server, Exchange server, SQL server, the whole shooting works for an office. &nbsp;We would like to split some of the jobs off this server onto an SBS 2003 server - the SBS 2000 would still remain the Terminal Server and would run some of the more difficult to reinstall apps but the SBS 2003 server would run Exchange, anti-virus, spam filtering and some of the SQL apps.<br />
<br />
Is this configuration doable? What domain issues might we run into?
</div>
</div>


We have a situation where we have an SBS 2000 server carrying on a variety of tasks - it acts as the Terminal Server, Exchange server, SQL server, the whole shooting works for an office.  We would like to split some of the jobs off this server onto an SBS 2003 server - the SBS 2000 would still remain the Terminal Server and would run some of the more difficult to reinstall apps but the SBS 2003 server would run Exchange, anti-virus, spam filtering and some of the SQL apps.

Is this configuration doable? What domain issues might we run into?

SBS 2000 and SBS 2003 - coexistence

Small Business Server (SBS) is a line of server operating systems targeted at small businesses by bundling the operating system with a number of other Microsoft products that would normally need to be purchased or licensed separately. The most notable inclusions are Exchange, SQL Server, SharePoint and ISA/TMG (Microsoft's firewall and proxy server).

Active Directory (AD) is a Microsoft brand for identity-related capabilities. In the on-premises world, Windows Server AD provides a set of identity capabilities and services, and is hugely popular (88% of Fortune 1000 and 95% of enterprises use AD). This topic includes all things Active Directory including DNS, Group Policy, DFS, troubleshooting, ADFS, and all other topics under the Microsoft AD and identity umbrella.