<div>
* Assumes that a new, functional exchange-server is in-place prior to decommissioning of this email server - which should be the case since the client is now on O365*<br />
<br />
The drawbacks should be minimal, if the removal procedure is performed correctly. <br />
This guide explains the process in detail to help minimize possible complications.<br />
<a href="https://supertekboy.com/2013/11/09/uninstalling-exchange-2003-from-small-business-server/" rel="ugc">https://supertekboy.com/2013/11/09/uninstalling-exchange-2003-from-small-business-server/</a>
</div>


<div>
Exactly what I planned and was hoping for.. Have the Install Disk 2 ready to drop and and then uninstall.
</div>


<div>
I'd agree with Cris here. &nbsp;Don't do this.<br />
<br />
The last thing you want is to do is continue supporting the 2003 if you don't have to. If he wants a remote office then either configure a VPN or get another Server for that site.
</div>


<div>
He has new W2012 server at new site. Thought there may be advantage to keeping old server in place for authentication only.. But there will be vpn between two offices. Old office will be in his home with only him connecting.. But I guess I could take it out and just rely on VPN
</div>


<div>
Running on obsolete server software puts server data and end user at risk
</div>


<div>
<div class="content wysiwyg-content">
Have a client that I have started migrating from SBS 2003 to W2012. I have joined the W2012 to the somein and it is setup with A/D. Originally I was going to decommission the SBS2003 completely, moving the FSMO roles, remove Exchange and decommission. Now he is setting up a remote office and I would like to keep the SBS2003 machine at the original office for A/D authentication but have most of the files on the new server at the new / larger location.<br />
<br />
What is the drawback to removing Exchange from SBS2003, but leaving it run?<br />
Only used for the A/D component for local authentication. He has migrated mail to Office365 and only has 6 users. 4 at new location and 2 at old
</div>
</div>


Have a client that I have started migrating from SBS 2003 to W2012. I have joined the W2012 to the somein and it is setup with A/D. Originally I was going to decommission the SBS2003 completely, moving the FSMO roles, remove Exchange and decommission. Now he is setting up a remote office and I would like to keep the SBS2003 machine at the original office for A/D authentication but have most of the files on the new server at the new / larger location.

What is the drawback to removing Exchange from SBS2003, but leaving it run?
Only used for the A/D component for local authentication. He has migrated mail to Office365 and only has 6 users. 4 at new location and 2 at old

Remove Exchange from sbs 2003

Exchange is the server side of a collaborative application product that is part of the Microsoft Server infrastructure. Exchange's major features include email, calendaring, contacts and tasks, support for mobile and web-based access to information, and support for data storage.

Exchange

Windows Server 2003 was based on Windows XP and was released in four editions: Web, Standard, Enterprise and Datacenter. It also had derivative versions for clusters, storage and Microsoft’s Small Business Server. Important upgrades included integrating Internet Information Services (IIS), improvements to Active Directory (AD) and Group Policy (GP), and the migration to Automated System Recovery (ASR).

Windows Server 2003

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).

Windows Server 2012 is the server version of Windows 8 and the successor to Windows Server 2008 R2. Windows Server 2012 is the first version of Windows Server to have no support for Itanium-based computers since Windows NT 4.0. Windows Server 2012, now in its second release (Windows Server 2012 Release 2) includes Foundation, Essentials, Standard and Datacenter, and does not support IA-32 or IA-64 processors.