- My Forums
- Tiger Rant
- LSU Recruiting
- SEC Rant
- Saints Talk
- Pelicans Talk
- More Sports Board
- Fantasy Sports
- Golf Board
- Soccer Board
- O-T Lounge
- Tech Board
- Home/Garden Board
- Outdoor Board
- Health/Fitness Board
- Movie/TV Board
- Book Board
- Music Board
- Political Talk
- Money Talk
- Fark Board
- Gaming Board
- Travel Board
- Food/Drink Board
- Ticket Exchange
- TD Help Board
Customize My Forums- View All Forums
- Show Left Links
- Topic Sort Options
- Trending Topics
- Recent Topics
- Active Topics
Started By
Message
Exchange 365 migration - well done, Microsoft, well done
Posted on 4/16/15 at 4:09 pm
Posted on 4/16/15 at 4:09 pm
The masters have done it again.
Yes, it is 8x easier to migrate from Exchange to Google Apps than it is to migrate from Exchange 2010 to Exchange 365 Online.
Well done.
Yes, it is 8x easier to migrate from Exchange to Google Apps than it is to migrate from Exchange 2010 to Exchange 365 Online.
Well done.
3
Posted on 4/16/15 at 4:16 pm to Casty McBoozer
When I was a tier 2 tech, I hated dealing with customers that were migrating to Office 365. The stupid txt record with some verification string, then the 7 or 8 DNS records.. retarded.
That's been my only experience with it, though.
That's been my only experience with it, though.
Posted on 4/16/15 at 4:18 pm to Casty McBoozer
office 365 vs google apps for a small business (25 employees)
which is better?
which is better?
Posted on 4/16/15 at 4:22 pm to hawgfaninc
I think Google Apps is better hands down, but I'm hating on Microsoft right now. DNS is not a problem. Creating TXT records is child's play.
Here's my problem for a cutover migration:
That's fricking great Microsoft, but the "Connectivity Analyzer" passes all tests with the credentials I'm entering. All the mailboxes fail to migrate, however. fricking piece of shite. Who gives a frick about autodiscovering my nuts anyway?
For the Google Apps migration, you download the tool, enter users in a csv, run the tool on the Exchange server, and sit back while it copies the data. fricking Microsoft
Here's my problem for a cutover migration:
quote:
AutoDiscover failed with a configuration error: The migration service failed to detect the migration endpoint using the Autodiscover service. Consider using the Exchange Remote Connectivity Analyzer (LINK ) to diagnose the connectivity issues.
That's fricking great Microsoft, but the "Connectivity Analyzer" passes all tests with the credentials I'm entering. All the mailboxes fail to migrate, however. fricking piece of shite. Who gives a frick about autodiscovering my nuts anyway?
For the Google Apps migration, you download the tool, enter users in a csv, run the tool on the Exchange server, and sit back while it copies the data. fricking Microsoft
This post was edited on 4/16/15 at 4:24 pm
Posted on 4/16/15 at 4:27 pm to Casty McBoozer
Posted on 4/16/15 at 6:50 pm to Casty McBoozer
Used this migration tool about 6 months ago. Easy peasy
Posted on 4/16/15 at 9:05 pm to Casty McBoozer
My email sends when I hit the send button.
Thanks Microsoft.
Thanks Microsoft.
Posted on 4/16/15 at 11:19 pm to Casty McBoozer
I do exchange migrations. I actually just did a 2010 to 365. Not really difficult honestly. I really prefer a hybrid migration, as opposed to a cutover migration.
Posted on 4/17/15 at 1:47 pm to WavinWilly
I've been on the phone with a 365 support engineer. We think the issue is the primary SMTP addresses for the users on Exchange is not the same as what is used to login to OWA. The Exchange Communication Analyzer correctly uses the alternative address for the server, but in the migration, it discovers the mailbox names, but then attempts to autodiscover again on each mailbox using an address that doesn't have autodiscover or SSL certs. I have a fix in the works, but once again, what a PITA. Exchange to GoogleApps would have been way easier.
Page 1 of 1
Popular
Back to top
Follow TigerDroppings for LSU Football News