After upgrading from Microsoft Exchange 2003 to Exchange 2007 or 2010 you might notice that the "Enable Web-based distribution" option is greyed out. The first thing to check is if you have moved the Offline Address Book generation to an Exchange 2007/2010 server.
However if you have already done this and the option is still disabled it can easily fixed by running ApplyMandatoryProperties on it. This can be done by running the below powershell command
Get-OfflineAddressBook | Set-OfflineAddressBook -ApplyMandatoryProperties
Et voila! you can now "Enable Web-based distribution"
You might notice that, your Microsoft Exchange environment, if your users setup outlook rules to automatically forward their emails to an external email address, these rules will not work and the forwarded email will never leave your organization.
This is because Exchange blocks, by default,automatic forwarding message. To solve this problem you will need to follow the below steps
There are many reasons why one would like to run an Exchange powershell .ps1 script as a scheduled task.
In this post I will share with you how to achieve this on both Microsoft Exchange 2007 and Exchange 2010.
Obviously you should start by creating your .ps1 script for this article we will assume the script location is c:\pcs\YourScript.ps1
After migrating your Exchange Public Folders from Exchange 2003 to Exchange 2007 / 2010 chances are you will start experiencing some problems.
These issues might show up under different symptoms however they all have one common solution.
This is the third, and last, part of the "Installing your first Exchange 2010 CAS" tutorial. In part 1 we discussed migration from Exchange 2003 to Exchange 2010, In part 2 migration from Exchange 2007 to 2010. Today we will discuss the case of mixed Exchange 2003 - 2007 environment.
If you managed to get your Exchange 2003/2007 environment working together then you already know that Exchange 2007 CAS can proxy requests to Exchange 2003 mailbox servers. We also know from part 1 of this tutorial that it is not the case for Exchange 2010.
Right now you have your Exchange 2007 CAS that is internet facing and handling all incoming requests by itself. Basically you should think of this as a combination of part 1 and part 2, one thing is common and it is that the newly introduced Exchange 2010 CAS will be dealing with incoming requests.
For Exchange 2007 Mailboxes
The Exchange2003Url is a new parameter in the Set-OwaVirtualDirectory cmdlet on Exchange 2010. Although Microsoft documentation clearly states that "The Exchange2003Url parameter specifies the Outlook Web App URL for Exchange 2003 mailboxes." It is all over the net that this parameter is also used to redirect requests to Exchange 2007 mailboxes!
I have no idea where this idea is coming from but I can assure you that is not the case.
Upgrading from Exchange 2003 to Exchange 2010
If you are upgrading from exchange 2003 you should know that an Exchange 2010 CAS cannot communicate directly with an Exchange 2003 mailbox. Thus you will need to publish at least 2 URLs one for your Exchange 2010 CAS and one for you Exchange 2003 Back End server or Front End server.
We will assume that https://owa.yourdomain.com/owa will point you to your exchange 2010 CAS server and https://ex2k3.yourdomain.com/exchange will give you access to your exchange 2003 back end or front end server.
By running, on your Exchange 2010 server,