Office 365 "Oops" Stories
-
I recently interviewed an O365 expert on our podcast, who reviewed the questionnaire his company has customers complete, before helping them migrate to O365... to help avoid a big "oops" moment.
I thought it might be helpful (and a little entertaining), to gather some first-hand O365 migration "lessons learned" stories...
Do you have an "oooops" moment that you can share about your migration to Office 365, that the other IT brethren should hear?
-
I know a lot of shops "oops" and deploy ADFS before looking into if they should or not.
-
I know an admin that once the mailboxes were migrated to o365 went in to exchange and deleted the mailboxes. Seems logical, but also deletes their AD account...
-
We had a client who wanted to do their own migration but has us as backup.
First step is they wanted to clean up all AD accounts and see how many licenses were actually needed etc. They accidently deleted AD (every account).
Needless to say we ended up doing the whole migration.
-
Client who again was trying to save money and wanted to do it themselves and use us for support "if" needed.
He got all the accounts setup in 365 but couldnt' figure out why email wouldn't go to them (didn't set A records or txt records). And couldn't figure out how to get rid of the onmicrosoft.com part....
Again we ended up doing the whole thing.
-
Client who did the "migration" themselves. Got 365 setup with all the accounts got email flowing. Then deleted his exchange server.
Then went around and deleted MS office from everyone's computers. Installed new office on everyone's machines.
Did you find the step he missed?
Yes he got fired for that. As it wasn't managements decision to not hire us to do the migration it was his.
-
I sense a trend.
-
@Minion-Queen said in Office 365 "Oops" Stories:
Client who did the "migration" themselves. Got 365 setup with all the accounts got email flowing. Then deleted his exchange server.
Then went around and deleted MS office from everyone's computers. Installed new office on everyone's machines.
Did you find the step he missed?
Yes he got fired for that. As it wasn't managements decision to not hire us to do the migration it was his.
did he loose address books?
-
@Dashrender said in Office 365 "Oops" Stories:
@Minion-Queen said in Office 365 "Oops" Stories:
Client who did the "migration" themselves. Got 365 setup with all the accounts got email flowing. Then deleted his exchange server.
Then went around and deleted MS office from everyone's computers. Installed new office on everyone's machines.
Did you find the step he missed?
Yes he got fired for that. As it wasn't managements decision to not hire us to do the migration it was his.
did he loose address books?
I'm guessing that he lost the email.
-
He lost EVERYTHING email, address books, archived email EVERYTHING!
-
@Minion-Queen said in Office 365 "Oops" Stories:
He lost EVERYTHING email, address books, archived email EVERYTHING!
aww.. I would have figured he would have realized that before he uninstalled Office per your comments.. but perhaps he did it all in a weekend without checking anything..
Damn yo!
-
@Dashrender said in Office 365 "Oops" Stories:
@Minion-Queen said in Office 365 "Oops" Stories:
He lost EVERYTHING email, address books, archived email EVERYTHING!
aww.. I would have figured he would have realized that before he uninstalled Office per your comments.. but perhaps he did it all in a weekend without checking anything..
Damn yo!
And no backups, of course. (I'm assuming.)
-
@BRRABill said in Office 365 "Oops" Stories:
@Dashrender said in Office 365 "Oops" Stories:
@Minion-Queen said in Office 365 "Oops" Stories:
He lost EVERYTHING email, address books, archived email EVERYTHING!
aww.. I would have figured he would have realized that before he uninstalled Office per your comments.. but perhaps he did it all in a weekend without checking anything..
Damn yo!
And no backups, of course. (I'm assuming.)
For local deploymenst with data stored on desktops... I'm guessing no.
-
@scottalanmiller said in Office 365 "Oops" Stories:
@BRRABill said in Office 365 "Oops" Stories:
@Dashrender said in Office 365 "Oops" Stories:
@Minion-Queen said in Office 365 "Oops" Stories:
He lost EVERYTHING email, address books, archived email EVERYTHING!
aww.. I would have figured he would have realized that before he uninstalled Office per your comments.. but perhaps he did it all in a weekend without checking anything..
Damn yo!
And no backups, of course. (I'm assuming.)
For local deploymenst with data stored on desktops... I'm guessing no.
Oh, never picked up that piece.
Now the error makes sense.
-
@Dashrender said in Office 365 "Oops" Stories:
@Minion-Queen said in Office 365 "Oops" Stories:
He lost EVERYTHING email, address books, archived email EVERYTHING!
aww.. I would have figured he would have realized that before he uninstalled Office per your comments.. but perhaps he did it all in a weekend without checking anything..
Damn yo!
Exactly!
-
I take it the data never actually made it to the O365 system.
-
Nope he never "migrated" anything other that the DNS records :P. So new email flowed just fine. He have to move the data to Office365 for it to grab it.
And he blew away the onsite exchange server and all the data on the desktops before he verified that it all was where it should be, in the new system.
Hence we when we do this one we actually migrate the data to 365 and 2 you don't delete the server for months until you are sure everything is where is should be and working correctly.
-
@Minion-Queen said
Hence we when we do this one we actually migrate the data to 365 and 2 you don't delete the server for months until you are sure everything is where is should be and working correctly.
Shoot I have a room of servers here from upgrades ... just in case.
I'd have backups of backups before trying something like that.
Just ... because comptuers
-
@BRRABill said in Office 365 "Oops" Stories:
@Minion-Queen said
Hence we when we do this one we actually migrate the data to 365 and 2 you don't delete the server for months until you are sure everything is where is should be and working correctly.
Shoot I have a room of servers here from upgrades ... just in case.
I'd have backups of backups before trying something like that.
Just ... because comptuers
YES!!! Yeah no such luck there. No backups at all. Except for I think one user who had put crashplan or something on their machine cause they were paranoid (I think there might have been good reason).
-
@Minion-Queen said in Office 365 "Oops" Stories:
@BRRABill said in Office 365 "Oops" Stories:
@Minion-Queen said
Hence we when we do this one we actually migrate the data to 365 and 2 you don't delete the server for months until you are sure everything is where is should be and working correctly.
Shoot I have a room of servers here from upgrades ... just in case.
I'd have backups of backups before trying something like that.
Just ... because comptuers
YES!!! Yeah no such luck there. No backups at all. Except for I think one user who had put crashplan or something on their machine cause they were paranoid (I think there might have been good reason).
I'm not sure "paranoid" would apply to those users.
