<div>
<div class="content wysiwyg-content">
We have an Exchange Enterprise 2003 server on an Windows 2003 server and do not have many issues. &nbsp;We have about 100 users and about 10 remote users who use WebAccess and we are considering going to Exchange 2007 but have no real requirement or reason to go to 2007 at this time. &nbsp;We wanted to see what people think of Exchange 2007 and is it worth it to rock the boat just to say we moved to 2007or should we stay with Exchange 2003 for awhile since it fills our needs and we have no issues? &nbsp;
</div>
</div>


We have an Exchange Enterprise 2003 server on an Windows 2003 server and do not have many issues.  We have about 100 users and about 10 remote users who use WebAccess and we are considering going to Exchange 2007 but have no real requirement or reason to go to 2007 at this time.  We wanted to see what people think of Exchange 2007 and is it worth it to rock the boat just to say we moved to 2007or should we stay with Exchange 2003 for awhile since it fills our needs and we have no issues?  

Moving from Exchange 2003 to 2007

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

Within Internet message handling services (MHS), a message transfer agent or mail transfer agent (MTA) or mail relay is software that transfers electronic mail messages from one computer to another using a client–server application architecture. A MTA implements both the client (sending) and server (receiving) portions of the Simple Mail Transfer Protocol (SMTP). The terms mail server, mail exchanger, and MX host may also refer to a computer performing the MTA function. The Domain Name System (DNS) associates a mail server to a domain with mail exchanger (MX) resource records containing the domain name of a host providing MTA services.