<div>
Follow this<br />
<a href="http://www.networkworld.com/community/node/47632" rel="ugc">http://www.networkworld.com/community/node/47632</a>
</div>


Follow this
http://www.networkworld.com/community/node/47632 [http://www.networkworld.com/community/node/47632]

<div>
See my guide here that will explain all the steps for you: <a href="https://www.experts-exchange.com/Software/Server_Software/Email_Servers/Exchange/A_2881-Migrate-Small-Business-Server-2003-to-Exchange-2010-and-Windows-2008-R2.html" rel="ugc">https://www.experts-exchange.com/Software/Server_Software/Email_Servers/Exchange/A_2881-Migrate-Small-Business-Server-2003-to-Exchange-2010-and-Windows-2008-R2.html</a><br />
<br />
It's written for SBS2003 but the process is exactly the same.
</div>


See my guide here that will explain all the steps for you: https://www.experts-exchange.com/Software/Server_Software/Email_Servers/Exchange/A_2881-Migrate-Small-Business-Server-2003-to-Exchange-2010-and-Windows-2008-R2.html [https://www.experts-exchange.com/Software/Server_Software/Email_Servers/Exchange/A_2881-Migrate-Small-Business-Server-2003-to-Exchange-2010-and-Windows-2008-R2.html]

It's written for SBS2003 but the process is exactly the same.

<div>
<div class="content wysiwyg-content">
I am migrating our Exchange 2003 to 2010. We are a small company with 125 mailboxes, very few Public Folders. Clients use Outllook 2003, 2007, POP. Some Outlook Clients use RPC/HTTP. Also use OWA.<br />
<br />
Existing: Exchange 2003 SP2 (Ver 6.5 build 7638.2) &nbsp;Windows Server 2003 R2 SP2<br />
<br />
New System: New Hardware, Windows 2008<br />
<br />
Org:<br />
1 Domain, with DC's on Windows 2003 SP2. Firewalled, Internal Cert Server with Root Certificates loaded on clients systems as deployed.<br />
<br />
Question1: Will this plan work?<br />
<br />
1. After Backups, Install new Server and Exchange<br />
2. Move Mailboxes and Public Folders.<br />
3. Change Firewall redirects to new server.<br />
4. Change Internal DNS to point to new server<br />
5. Leave Old Exchange Server up for a few weeks then uninstall.<br />
<br />
From all I have read this should be fine but I am real nervous about this move.<br />
<br />
Thanks for any reply.
</div>
</div>


I am migrating our Exchange 2003 to 2010. We are a small company with 125 mailboxes, very few Public Folders. Clients use Outllook 2003, 2007, POP. Some Outlook Clients use RPC/HTTP. Also use OWA.

Existing: Exchange 2003 SP2 (Ver 6.5 build 7638.2)  Windows Server 2003 R2 SP2

New System: New Hardware, Windows 2008

Org:
1 Domain, with DC's on Windows 2003 SP2. Firewalled, Internal Cert Server with Root Certificates loaded on clients systems as deployed.

Question1: Will this plan work?

1. After Backups, Install new Server and Exchange
2. Move Mailboxes and Public Folders.
3. Change Firewall redirects to new server.
4. Change Internal DNS to point to new server
5. Leave Old Exchange Server up for a few weeks then uninstall.

From all I have read this should be fine but I am real nervous about this move.

Thanks for any reply.

Exchange 2003 to 2010 migration

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

Microsoft Outlook is a personal information manager from Microsoft, available as a part of the Microsoft Office suite. Although often used mainly as an email application, it also includes a calendar, task manager, contact manager, note-taker, journal, and web browser.

Outlook

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.