I am working with a customer that’s running Exchange 2010 on-premises and want to move to Office 365 in a hybrid scenario. The hybrid servers are running Exchange 2010. After implementing a hybrid scenario everything was working fine, but after some time I received calls that free/busy wasn’t working correctly anymore.
When a user with a Mailbox in Exchange online and he wants to schedule a meeting with a Mailbox in Exchange 2010 on-premsises all goes well and the user can see all free/busy information from all users.
When a user with an on-premises Mailbox (on Exchange 2010) wants to schedule a meeting with a Mailbox in Office 365 free/busy information from a Mailbox that’s not Domain joined he cannot check the availability information from Mailbox in Exchange Online as shown in the following screenshot:
Continue reading Free/Busy cross-premises not working correctly
Recently I had to reinstall my entire infrastructure, and one of the servers was the Office Web Apps server. Unfortunately the server was willing to do anything, the only thing I got was a white screen, or the ‘old’ WebReady Document view appeared. The discovery URL (https://webapps.exchangelabs.nl/hosting/discovery) was working fine, so at least something was working.
Another thing that was clearly visible was that processor utilization regularly peaked to 100%, sometimes staying at 100% for a longer period of time:
Continue reading Office Web Apps 2013 server not working, CPU Utilization 100%
One of the first steps in troubleshooting your Exchange environment (or any Windows environment) is checking the Event Viewer. The Application log shows tons of entries, and step one is to filter out only the Error messages:
Continue reading Filtering event log entries
Customer wanted to enable the Exchange Online Archive on his Exchange Online Mailbox. Open the Exchange Admin Center, select the user and in the actions pane select “enable” under In-Place Archive. Continue reading Unable to perform the save operation when enabling Exchange Online Archive
The recommended way of installing the Exchange 2013 Edge Transport server is on a workgroup member (stand-alone server) in the DMZ. However, it is not uncommon that customers are implementing an Active Directory domain in their DMZ for management purposes.
Continue reading Edge Transport server fails in Active Directory domain