<div>
Nice one sembee, I was looking at the specific setup of the receive connectors over the last week and im confident once replicated the coexistance will work. Have you any other suggestions on this server? I will double check the receive connectors again anyway as there are several. <br />
I was not too sure whether the send connectors would be picked up automatically so i planned to just manually enter them in my project plan in case. <br />
<br />
One more thing of note is that I am planning to add a DAG server once the 2010 server is decommissioned. <br />
<br />
Thanks a lot for this!
</div>


<div>
Any idea if i could move 400GB worth of mailboxes in 48 hours? <br />
<br />
The specs for the two servers are the same disk wise, they are sitting on a powervault san with 7.5k SAS disks in them connected by direct cable host to san. There are actually two different arrays in the SAN come to think of it, I will check if they are on the same array or not as this will affect the mailbox move time.
</div>


<div>
that could be tight. It is not only the size that makes the difference but it is also the number of items in each mailbox. A smaller mailbox with more items can take longer to move. You can stage a lot of moves at once (I recommend using a csv file) but Exchange only moves so many at one time. If you are going from one server to another, you probably will only get 2 at a time moving while the rest wait. (maybe 4. has been a while since we migrated)<br />
&nbsp; You can help by having everyone empty deleted items.<br />
<br />
Also, just because the DB says 400 GB, it may not have that much data. Exchange databases cannot shrink on their own, they only grow. If you remove mailboxes, you only create &quot;white space&quot; in the Database. However, this &quot;White Space&quot; does not migrate.
</div>


<div>
Why do you want to move the mailboxes in 48 hours?<br />
There is no need to rush the process. <br />
Mailboxes from Exchange 2010 can be moved &quot;hot&quot;, with the user getting a prompt at the end to restart Outlook, no need to do it out of hours. <br />
Setting up full coexistence between the two versions for client access is also very easy. <br />
<br />
I haven't done an &quot;against the clock&quot; migration for years, there is simply no need - unless the source server is about to die. <br />
<br />
Simon.
</div>


<div>
No it isnt dying, but I have a couple of days with the business closed so was considering it. The plan as of now is to do them over the working week, I was considering suggesting changing it. Also my rollback is a domain controller restore(all 2 of them) and remove Exchange2013 server, might be better roll back this weekend than next although I doubt we will be rolling back very much tbh.<br />
<br />
I will leave it till next week so ;) thanks
</div>


<div>
I wouldn't even contemplate a rollback. It will cause you more problems than you think it resolves. <br />
Do a staged installation (prep first) if you are concerned. If something goes wrong after that, recovery is easier without having to rollback the domain. <br />
<br />
SImon.
</div>


<div>
I agree, a rollback is not a good idea. If you follow the standard procedures for Migrating, you can do this over a long period of time. I assumed you had issues that required a quick move. If you do not, do this in stages. Make sure your send and receive all come via the Exchange 2013 &nbsp;server (OWA also) and is working. Migrate a test account (create one for just that purpose) and make sure you can send mail back and forth between it and other mailboxes and send and receive to an external address. Once that works, then migrate as you go. The way mailbox moves happen is this: the user has access until the last little bit, then there is a short hiccup while the move finishes and the user is on the new server. I would do them at night over a few weeks.<br />
&nbsp; Paul Cunningham (exchangeserverpro.com) has a great ebook about migrating that covers just about every base.
</div>


<div>
Hey,<br />
<br />
It all went according to plan anyway, well did have a couple of majors. <br />
For anybody installing Exchange 2013 on 2008 R2 be aware of this issue, a bug in windows update and CBS that takes update 2619234 over 6 hours to install, this is a 1.4MB update. <br />
<br />
Also had an issue with receiving mail through 2010 server once I rerouted the mail to the new server. Fortunately got that one resolved quickly, another bug, 2010 server had 2013 servers IP setup as a relay on a receive connector. <br />
<br />
Points have to go to Sembee im afraid. <br />
<br />
Cheers Guys.
</div>


<div>
<div class="content wysiwyg-content">
Guys.<br />
<br />
I am doing a Exchange 2010 to Exchange 2013 migration over the weekend, both servers are single CAS servers hosting all roles. <br />
&nbsp;<br />
I have a question in regards to Exchange 2013 server autodiscovering the receive and send connectors from 2010. <br />
I am prepared for this even if it does not autodiscover them, I will manually input them. <br />
<br />
Any other info would be great my migration plan is built from this MVP article <a href="http://www.msexchange.org/articles-tutorials/exchange-server-2013/migration-deployment/migrating-small-organization-exchange-2010-exchange-2013-part1.html" rel="ugc">http://www.msexchange.org/articles-tutorials/exchange-server-2013/migration-deployment/migrating-small-organization-exchange-2010-exchange-2013-part1.html</a><br />
<br />
I am pretty confident in my migration plan but you can never be too sure. Thanks in advance.<br />
<br />
Regards M
</div>
</div>


Guys.

I am doing a Exchange 2010 to Exchange 2013 migration over the weekend, both servers are single CAS servers hosting all roles. 
 
I have a question in regards to Exchange 2013 server autodiscovering the receive and send connectors from 2010. 
I am prepared for this even if it does not autodiscover them, I will manually input them. 

Any other info would be great my migration plan is built from this MVP article http://www.msexchange.org/articles-tutorials/exchange-server-2013/migration-deployment/migrating-small-organization-exchange-2010-exchange-2013-part1.html

I am pretty confident in my migration plan but you can never be too sure. Thanks in advance.

Regards M

Exchange 2010 - 2013 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

Windows Server 2008 and Windows Server 2008 R2, based on the Microsoft Vista codebase, is the last 32-bit server operating system released by Microsoft. It has a number of versions, including including Foundation, Standard, Enterprise, Datacenter, Web, HPC Server, Itanium and Storage; new features included server core installation and Hyper-V.