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.
There have been lately quite a few buzz around the fact that changing password through Exchange 2010 OWA is failing with the following error even though user is not logged on with the light version of Outlook Web App
This feature isn't supported in the light version of Outlook Web App.
This feature isn't supported if Outlook Web App is set to maximize the blind or low vision experience.
This error is due typically because the operating system on which you are running your Exchange 2010 CAS has been cloned, virtual image template etc..., but not prepared with sysprep before installing Exchange on it.
I have recently needed to move the File Share Witness on a Microsoft Exchange 2007 CCR cluster from its original location to an alternate server and I will share with you how to do it in case you are faced with a similar scenarion.
Step 1: Create & Configure the new File Share Witness
On the server you want to host the new File Share Witness
- Create a new folder say FSW_ClusterName
- Share this folder and give the Cluster Service Account Full Control shared permissions
- As far as NTFS permissions grant Administrators and the Cluster Service Account Full Control
Step 2: Moving the File Share Witness
To move it use the following commands
Lot of people are confused about the difference between ISA/TMG/IAG/UAG, so I thought it would be a good idea to share this information hopping it will clear up this confusion.
Microsoft has lately released the “Forefront Threat Management Gateway (TMG)” formerly known by “Internet Security and Acceleration Server (ISA)”.
Microsoft has also released the “Forefront Unified Access Gateway (UAG)” formerly known by “Internet Access Gateway (IAG)”. By the way both products are run on 64bits only
So this means that TMG is the new version of ISA and UAG is the new version of IAG, mmm pretty simple right?
What is the Difference between TMG and UAG?
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
I have been lately involved in a question on Experts-Exchange that turned into a very interesting adventure that led me to discover a bug in the Dynamic Distribution Groups on Exchange 2007.
I have tested the below on Exchange 2007 SP2 rollup 2 and the bug was still there, however I need to mention that tests also proved it was solved on Exchange 2010.
First let me give you a very brief idea about the setup, for the lab I have setup an EBS server and created 2 mailboxes on it "John Doe" and "Jane Jackson".
Running Get-Recipient shows the 3 mailboxes in this organization
Taking a look at Active Directory Users and Computers also reveals that "John Doe" and "Jane Jackson" are located in the TestOu, the Administrator is located in the Users containter