Office 365 & Exchange Online
-
They should not have a local Exchange server at all. How did that even happen!
-
@MrWright4hire said:
No one can share their Calendar properly. They are all using
Office 365 via Outlook. Getting "Auto-Discovery Error," but
diagnostics shows that Auto Discovery is working properly.
N.B.: As a temporary fix, I've recommended that they use the
Web version of the Calendar, instead of using it in Outlook.It's likely detecting the local exchange instance and trying to pull the calendar from that.
-
@MrWright4hire said:
. Getting "Auto-Discovery Error," but
diagnostics shows that Auto Discovery is working properly.
N.B.: As a temporary fix, I've recommended that they use the
Web version of the Calendar, instead of using it in Outlook.Is the office 365 and local exchange using the same domain name?
Also the auto discovery is based on DNS so I'm guessing it's erroring out trying to find their stuff on the local exchange, but the diagnostics just shows that auto discovery works for the local exchange without trying to lookup anything specific to their account. -
@thecreativeone91 and @scottalanmiller they probably had it still up for a back up measure. That's the only thing I can think of as of now. With that said, I agree with you @thecreativeone91 about how the instance.
How would you approach this matter. I would like to move with precision as well as be organized about what order I should take certain steps. I would like to keep my impeccable reputation with this client. lol!
-
@MrWright4hire said:
@thecreativeone91 and @scottalanmiller they probably had it still up for a back up measure.
That's not how it works. That's like storing extra dynamite in your house in case of fire. Having the local Exchange just puts the Office 365 at risk. It makes it dramatically more fragile, harder to troubleshoot and more expensive to support.
-
Depending on how the current environment is configured, you may be able to use the O365 Migration Toolkit to "capture" everything from the Local Exchange Server, and then decommission it, after taking care of all of your DNS entries etc.
-
@MrWright4hire said:
How would you approach this matter. I would like to move with precision as well as be organized about what order I should take certain steps. I would like to keep my impeccable reputation with this client. lol!
If the data is fully migrated to O365 you can decommission the local install. You might need to allow some pop connector or something as that may be what they were using the local for.
https://technet.microsoft.com/en-us/library/bb123893(v=exchg.80).aspx
-
You have to be very careful, if they set it up as the AD master, you can't just turn it off. Office 365 might require it for every transaction.
-
@scottalanmiller said:
@MrWright4hire said:
@thecreativeone91 and @scottalanmiller they probably had it still up for a back up measure.
That's not how it works. That's like storing extra dynamite in your house in case of fire. Having the local Exchange just puts the Office 365 at risk. It makes it dramatically more fragile, harder to troubleshoot and more expensive to support.
and for once, sam is right, baha
O365 is much more durable than a local instance of exchange for a small business.
-
@Hubtech said:
O365 is much more durable than a local instance of exchange for a small business.
Well and what is important here is that this is set up so that BOTH have to work for things to work. So it is all of the risk of Office 365 plus all of the risk of the local Exchange. If either one goes down, email stops working. It's the opposite of a backup.
-
@scottalanmiller said:
@Hubtech said:
O365 is much more durable than a local instance of exchange for a small business.
Well and what is important here is that this is set up so that BOTH have to work for things to work. So it is all of the risk of Office 365 plus all of the risk of the local Exchange. If either one goes down, email stops working. It's the opposite of a backup.
yes, you OP, have inherited a poorly executed migration
-
@scottalanmiller said:
You have to be very careful, if they set it up as the AD master, you can't just turn it off. Office 365 might require it for every transaction.
That's a horrible bad practice if they did.
-
@Hubtech said:
yes, you OP, have inherited a poorly executed migration
Yes, whoever got them to where they are screwed up big time.
-
Commercial Break!!!!!!!
See THIS, meaning your efforts to come to one's rescue, IS WHY I LOVE EVERYONE OF YOU! NO HOMO!
Now back to the intelligent Geek part.P.S. Thank you so much for being there for me.
-
@thecreativeone91 said:
@scottalanmiller said:
You have to be very careful, if they set it up as the AD master, you can't just turn it off. Office 365 might require it for every transaction.
That's a horrible bad practice if they did.
AFAIK, that is the only way that it can exist with Exchange 2007 like this.
-
@scottalanmiller said:
@Hubtech said:
yes, you OP, have inherited a poorly executed migration
Yes, whoever got them to where they are screwed up big time.
Hopefully it was free or less than free lol.
-
Without reading everyone's posts, my guess is it sees the local Exchange server and tries to pull from that. You need to have the client migrate EVERYTHING to Office365 and get off that local server. I don't even want to try and figure out how you have all the MX records, etc setup.
