Do NOT install Exchange 2010 SP1 on your Edge/TMG server
If you are running Exchange 2010 Edge on Forefront TMG do NOT install Exchange 2010 SP1 on it yet. Doing so will lead to crash your TMG Managed Control service with the error
The Forefront TMG Managed Control service failed to initialize. Error information: Command failed with error: The term 'Get-AntiSpamUpdates' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again
Can’t install Exchange 2010 RTM when Exchange 2007 SP3 exists
I am faced with a very funny issue at a client where I'm migrating from Lotus Domino to Exchange.
As you might know Microsoft didn't release migration tools from Lotus to Exchange 2010 directly so the path was Domino -> Exchange 2007 and then Exchange 2007 -> Exchange 2010.
Since Exchange 2007 SP3 has been released a couple of days ago I've installed it on, what I was planning to be, a temporary server.
I was surprised today that I was not able to install Exchange 2010 and setup.com /PrepareSchema failed with the following error.
BIS & other EWS applications in Exchange 2007 to 2010 coexistence
I have received comments about my "Installing your first Exchange 2010 CAS" 3 parts - tutorial that it didn't include any reference to services other than OWA. The reason behind this is simply because other services like ActiveSync, POP3, IMAP4, will work through proxying without the need for any additional configuration other than what has already been covered.
However I have faced a strange issue with Exchange Web Services and coexistence of Exchange 2007 and 2010. Since it is clearly stated on technet that
Clients that use Exchange ActiveSync, Exchange Web Services, POP3, and IMAP4 can't use redirection.
I thought it is safe to assume that EWS traffic will be proxied just like it is the case of ActiveSync, POP3 and IMAP4. My thoughts were further confirmed by the same technet article stating that Proxying supported between Client Access servers in the same Active Directory Site for the Exchange Web Services protocol (check section "Client Access protocols for redirection and proxying"), but obviously my thoughts were wrong!
Doing some tests with requests hitting the Exchange 2010 CAS server & using the famous test exchange connectivity website showed failures for users who's mailboxes are still on Exchange 2007 with the following error, while the test passed for users who's mailboxes are now on Exchange 2010.
The Client Access server version doesn't match the Mailbox server version of the resource that was being accessed. To determine the correct URL to use to access the resource, use Autodiscover with the address of the resource.
So it seems that the only way for EWS to work in a mixed Exchange 2007-2010 environment is that the application itself should support Autodiscover.
This is bad news, it means that my client will need to edit manually the settings for all its Blackberry Internet Service (BIS) users!
At this point I am still unsure if it is a bug but it looks like one, so if someone has more insight about it I would really appreciate the feedback.
Exchange 2010 DAG IP fails to be brought online
While running an Exchange 2010 Database Availability Group you might encounter an error in the System Log of your mailbox server stating that
Cluster IP address resource 'Cluster IP Address' cannot be brought online because the cluster network 'Cluster Network 2' is not configured to allow client access. Please use the Failover Cluster Manager snap-in to check the configured properties of the cluster network.
Open the Failover Cluster Manager go to Networks and select the faulty network reported in the above error. You will notice that "Allow clients to connect through this network" is enabled.
This seems to be a bug and the solution is pretty easy, you just need to deselect "Allow clients to connect through this network", click on Apply, select it again and apply once more the new configuration, this should take care of the error right away.
Get-OwaVirtualDirectory fails with: “An iis directory entry couldn’t be created access is denied”
After deploying Microsoft Exchange 2010 in your existing Exchange 2007 organization you might face the following error from using either Exchange Management Shell or Exchange Management Console
An IIS directory entry couldn’t be created. The error message is Access is denied. HResult = –2147024891
The error looks like this in EMS
Exchange 2010 mmc fails with “An error caused a change in the current set of domain controllers” after demotion of a Domain Controller
After demoting one of your Domain Controllers you might be faced with the following error when using the Exchange 2010 Management Console.
An error caused a change in the current set of domain controllers
This error might appear at different places in you Exchange 2010 Management Console and under different error messages that all have the sentence above in common. However using the Exchange Management Shell works flawlessly.
As weird as it might sound manually specifying a Domain Controller for the Exchange Server to use did not solve the problem, however during my troubleshooting I tried to log on as another user and the error was miraculously gone.
