I have recommended to all my clients to wait until SP1 is released and then 
evaluate the product at that time.

I have done a few of these migrations. I've gotten new clients who have pulled 
me in to complete the migrations after another consulting company failed.

Public folder migrations to "modern public folders" are always difficult. The 
new EAC looks fine, until you find out that you have to drop to PowerShell to 
do many of the things you used to could do in EMC. S/MIME isn't present in OWA. 
... the list is long.

From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On 
Behalf Of Paul Cookman
Sent: Monday, December 16, 2013 1:13 PM
To: exchange@lists.myitforum.com
Subject: [Exchange] RE: Good Upgrade document to 2013.

I see, thanks for the advice.

The business reason is really to keep up to date for customer perception. There 
isn't a set date but February was about the time that fitted into workloads.

Are you putting customers off upgrading at the moment then until the fixes are 
resolved or would you advise to maybe skip a version?

From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> 
[mailto:listsad...@lists.myitforum.com] On Behalf Of Michael B. Smith
Sent: 16 December 2013 17:20
To: exchange@lists.myitforum.com<mailto:exchange@lists.myitforum.com>
Subject: [Exchange] RE: Good Upgrade document to 2013.

I stated the question wrong. Exchange 2010 is a great, stable, feature-rich 
product. Exchange 2013 is optimized for the cloud, misses quite a number of 
on-premises features compared to Exchange 2010, is still relatively buggy, and 
consumes about twice as many resources as Exchange 2010. Do you have a good 
business reason for moving to Exchange 2013?

From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> 
[mailto:listsad...@lists.myitforum.com] On Behalf Of Paul Cookman
Sent: Monday, December 16, 2013 12:15 PM
To: exchange@lists.myitforum.com<mailto:exchange@lists.myitforum.com>
Subject: [Exchange] RE: Good Upgrade document to 2013.

I am just upgrading from 2010 to 2013 but like to follow a good document so I 
don't miss anything.

From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> 
[mailto:listsad...@lists.myitforum.com] On Behalf Of Michael B. Smith
Sent: 16 December 2013 17:07
To: exchange@lists.myitforum.com<mailto:exchange@lists.myitforum.com>
Subject: [Exchange] RE: Good Upgrade document to 2013.

Can I ask why? Why do you want to do this?

From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> 
[mailto:listsad...@lists.myitforum.com] On Behalf Of Paul Cookman
Sent: Monday, December 16, 2013 11:32 AM
To: 'exchange@lists.myitforum.com'
Subject: [Exchange] Good Upgrade document to 2013.

Does anyone know of a really good document for upgrading\coexisting exchange 
2010 to 2013 including moving smtp, public folders, everything step by step?

Also a little concerned about public folders moving 100 gig to 2013, I found in 
2003/2007 you had to do in stages as it stopped email while it was coping 
across. Any issues seen from 2010 to 2013 or will it trickle across?

Kind regards,

Paul.



______________________________________________________________________
This email has been scanned by Selection Services Ltd using the Symantec Email 
Security.cloud service.
______________________________________________________________________

______________________________________________________________________
This email has been scanned by Selection Services Ltd using the Symantec Email 
Security.cloud service.
______________________________________________________________________

______________________________________________________________________
This email has been scanned by Selection Services Ltd using the Symantec Email 
Security.cloud service.
______________________________________________________________________

______________________________________________________________________
This email has been scanned by Selection Services Ltd using the Symantec Email 
Security.cloud service.
______________________________________________________________________

______________________________________________________________________
This email has been scanned by Selection Services Ltd using the Symantec Email 
Security.cloud service.
______________________________________________________________________

Reply via email to