Office 365 Users Not able to view Free/Busy and Room information of On-Premises

The other day I had to validate and solve a problem with calendar synchronizations between Office 365 and Exchange 2010 (and vice verse). I was aware that On-Premises users could see the status of all users calendars, but Office 365 users only could see the Office 365 users status. (Office 365 users were not able to view F/B information of On- Premises user mailboxes).

This scenario is valid for Exchange 2010/2013 and Office 365 hybrid architectures with or without ADFS. The errors that I had were this:

Trying to share a Calender between On-Prem and an Office 365 User:

"One or more users cannot be added to the folder access list"

The outlook/webmail calendar had errors:

"No Information. No free/busy information could be retrieved"

"The recipient's server could not be contacted. Contact your administrator"

Let's see the necessary steps for the resolution.

Exchange 2010 Inter-Organizations Migration – Remote Move

The migration scenario:

• Two different forests;
• Exchange 2007 in one forest and Exchange 2010 in the other;
• Exchange 2007 with SP2 installed.

Requirements:

• Create a DNS Conditional Forwarding on the source domain for the destination domain;
• Create a DNS Conditional Forwarding on the destination domain for the source domain;
• Before starting the migration itself, you need to trust between the two domains and deactivate SID Filtering:
• Netdom trust destination.local /domain:source.local / quarantine: No / usero: destination\user / passwordo: *******
• Netdom trust source.local /domain:destination.local / quarantine: No / usero: source\user / passwordo: ********

 

This way, when migrating with ADMT, users' SIDs remain the same (Filtering Disabled), thus ensuring the same permissions on files and groups in the target domain.

 

With ADMT installed on a server machine in the target domain, migrate the users/groups from the source to the destination (need to install the password exporter on a Domain Controller at the source, so we can guarantee the passwords are the same in both domains)

O In this document I will not go ahead with the ADMT settings.

 

Redirecting Webmail (OWA) URLs in IIS for All Exchange Versions

In this post I will show you how to redirect all OWA requests to the correct HTTPS address. It works not only with OWA, but with EWS and/or ECP.

I’ve been doing this for as long as I can remember in Exchange 2007/2010/2013 so that requests go automatically to https://owa.customer.com/owa (or /exchange). So, if someone goes to http://owa.customer.com or https://owa.customer.com, they get redirected to the correct (secure) URL.

Migrate Exchange 2007-2010 Public Folders to Exchange 2013

 

In this Post I wil show you how to migrate Public folders from an earlier Exchange to Exchange 2013 (The process is the same in Exchange 2007 and 2010). It will not work with Exchange 2003.

First of all, the requirements:

• The user that will do the migration must belong to Organization Management and Recipient Management groups (Active Directory);
• All the mailboxes must already be in Exchange 2013 (All Mailboxes migrated). I will not cover in this Post how to migrate Mailboxes;
• The Public Folders migration must be planned (because there is a downtime);
• Before the migration, do a Full Backup of the legacy Exchange Server and Public Folders.

 The Migration process:

1. Download the migration Scripts;
2. Prepare the Migration;
3. Generate the CSV files;
4. Create the Public Folders Mailboxes in Exchange 2013;
5. Start the Migration;
6. Lock the Public Folders to Finalize the migration (requires downtime);
7. Finalize the Migration;
8. Unlock and Test the Public Folders.

Side Notes:

• Can not exist Public Folders in Exchange 2013 before the migration;
• All DNS Records must "point" to Exchange 2013 (like webmail, autodiscover, etc.);
• For some reason, if there are any Mailbox in Exchange Legacy, the public folder will be pointing to the Exchange Legacy;
• If there are Public Folders already created in Exchange 2013, all Migrated Mailboxes will automatically be pointing to the Exchange 2013 Public Folder instead of Exchange Legacy.

 

Ok, now that we have all the requirements, let's start!

Publishing Exchange 2010 Services in ISA 2006 or TMG 2010 with Certificates

 

 

In this Post I will show you how to Publish all of the Exchange Services in Firewall Rules (with certificates) so you can access it through Webmail, ActiveSync and/or Outlook Anywhere.

This will work with Microsoft Exchange 2007/2010 and Microsoft ISA 2006 and TMG 2010. Other versions of Exchange will work, but you will need to change some of the paths in the Firewall.

The Steps are:

1. Create and Import the Certificates;
2. Configure the Exchange Server;
3. Create the Web Listener in the Firewall;
4. Configure of the Publishing Rules
1. WebMail (OWA)
2. Outlook Anywhere
3. ActiveSync
5. Troubleshooting

With this configuration you can access your Email from Outside/Internet using your favorite browser or any mobile application that use Exchange Services or ActiveSync. With Outlook Anywhere you can use your Outlook like you were in the Office.

So, let's begin!