That's a sticky wicket... Regards,
Don Guyer Catholic Health East - Information Technology Enterprise Directory & Messaging Services 3805 West Chester Pike, Suite 100, Newtown Square, Pa 19073 email: [email protected]<mailto:[email protected]> Office: 610.550.3595 | Mobile: 610.955.6528 | Fax: 610.271.9440 For immediate assistance, please open a Service Desk ticket or call the helpdesk @ 610-492-3839. [cid:[email protected]] From: [email protected] [mailto:[email protected]] On Behalf Of N Parr Sent: Wednesday, September 25, 2013 10:47 AM To: '[email protected]' Subject: [Exchange] RE: Best Practices/Steps for Exchange Cloud to On Premises 500 pst's from multiple sites with users involved, I think I would find a new job first. The problem we have moving mailbox's is I'm told the current cloud host says they won't give us a logon that has full access to all our mailboxes. So that means we have to get everyone's passwords or reset the mailbox password before we move it. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Michael B. Smith Sent: Tuesday, September 24, 2013 4:35 PM To: [email protected]<mailto:[email protected]> Subject: [Exchange] RE: Best Practices/Steps for Exchange Cloud to On Premises That is what I consider a "worst choice" scenario. SOMETIMES it may be necessary. Usually, it is not. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Haluška Andrej Sent: Tuesday, September 24, 2013 11:29 AM To: [email protected]<mailto:[email protected]> Subject: [Exchange] RE: Best Practices/Steps for Exchange Cloud to On Premises You can also create the mailboxes in advance, test it, redirect new emails to the new server and move the data via PST. When I did this last time (between two independent environments, no trust possible) we were able to move 120GB of data (300+ mailboxes) in 14 hours. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of N Parr Sent: Tuesday, September 24, 2013 3:13 PM To: '[email protected]' Subject: [Exchange] RE: Best Practices/Steps for Exchange Cloud to On Premises Well that just made my day, actually month, maybe rest of year. So we just have to deal with ongoing mail which could be a big deal with this much data to move. Perhaps we can script a new contact for every user and set it to forward as the mailbox move is started. I'm sure it's covered in the stuff you told me to look up. Thanks Michael! From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Michael B. Smith Sent: Tuesday, September 24, 2013 8:00 AM To: [email protected]<mailto:[email protected]> Subject: [Exchange] RE: Best Practices/Steps for Exchange Cloud to On Premises New-MoveRequest and New-MigrationBatch authenticate just like a user and move the mailboxes. You do have to specify an account that can open the mailbox. If you have an admin account for the tenant use that, otherwise you can do a unique credential per mailbox. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of N Parr Sent: Tuesday, September 24, 2013 8:55 AM To: '[email protected]' Subject: [Exchange] RE: Best Practices/Steps for Exchange Cloud to On Premises Forgive my ignorance but how do you move mailboxes like that if the existing server isn't part of AD. I've done migrations before between server versions but never with non-AD integrated server you can't set a trust up with. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Michael B. Smith Sent: Tuesday, September 24, 2013 7:46 AM To: [email protected]<mailto:[email protected]> Subject: [Exchange] RE: Best Practices/Steps for Exchange Cloud to On Premises You do exactly the same thing that you would do for onboarding Exchange 2010 or Exchange 2013 to Office 365. :) Identify the mailboxes, use New-MoveRequest or New-MigrationBatch. Read up on those. The most challenging thing is to deal with ongoing email during the migration process. One server or the other has to be "master" and if a particular user is not present on one server it must be forwarded to the other. Another common Office 365 issue for Staged Exchange Migrations. You can read up on those solutions also. This is why you don't find much unique data - it's the same. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of N Parr Sent: Tuesday, September 24, 2013 8:33 AM To: '[email protected]' Subject: [Exchange] RE: Best Practices/Steps for Exchange Cloud to On Premises Sorry, first time doing this, left out some important info. Moving from hosted exchange, non-AD integrated. About 500 users all office 2010, most in the Midwest scattered across 5 states but also India, Australia, etc. Same domain will be used after migration as currently. At first it seems pretty simple to work up instructions for the users to add their new account and move data from hosted to new. Could probably be scripted also. I keep thinking someone has had to have done this before and there's all kinds of things I'm not thinking of. I have a smart team to work with but I'm the only admin that has any Exchange experience and hosts his own mail. Thanks From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Michael B. Smith Sent: Monday, September 23, 2013 3:57 PM To: [email protected]<mailto:[email protected]> Subject: [Exchange] RE: Best Practices/Steps for Exchange Cloud to On Premises What is the platform being used by the third party host? From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of N Parr Sent: Monday, September 23, 2013 4:14 PM To: '[email protected]' Subject: [Exchange] Best Practices/Steps for Exchange Cloud to On Premises I'm Googling around for this and all I get is office365 articles. How to coexist, how to migrate to 365. Maybe I'm not digging far enough in to the results. Our goal is to migrate users from a 3rd party host currently being used to a new in house 2013 environment. I know it seems counterintuitive to the world direction but powers that be have decided there's a significant cost savings considering all the other licensing we are doing and the # of users. Thanks Confidentiality Notice: This e-mail, including any attachments is the property of Catholic Health East and is intended for the sole use of the intended recipient(s). It may contain information that is privileged and confidential. Any unauthorized review, use, disclosure, or distribution is prohibited. If you are not the intended recipient, please delete this message, and reply to the sender regarding the error in a separate email.
<<inline: image001.jpg>>
