<div>
Be careful of ExDeploy (the first link). They tend to leave out critical steps, such as virtual directory namespace application and stuff like that. I have a whole deployment guide at home I wrote, but its about 72 pages long :)
</div>


Be careful of ExDeploy (the first link). They tend to leave out critical steps, such as virtual directory namespace application and stuff like that. I have a whole deployment guide at home I wrote, but its about 72 pages long :)

<div>
<div class="content wysiwyg-content">
Hi all we currently have an Exchange Server 2010 Setup, but would like to upgrade to Exchange 2013.<br />
<br />
Minimal Downtime is a Must, I am starting to create a Virtual Exchange Server 2013 I assume I can build this and then move mailboxes etc. over and decommission the old server.<br />
<br />
Does anybody know if this is the correct way without massive disruption and if so and useful guides or anything so that I can make a start<br />
<br />
John
</div>
</div>


Hi all we currently have an Exchange Server 2010 Setup, but would like to upgrade to Exchange 2013.

Minimal Downtime is a Must, I am starting to create a Virtual Exchange Server 2013 I assume I can build this and then move mailboxes etc. over and decommission the old server.

Does anybody know if this is the correct way without massive disruption and if so and useful guides or anything so that I can make a start

John

Exchange 2010 - Exchange 2013

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.