After updating Firefox today I encountered the following error when trying to work with the Exchange Control Panel in Exchange 2010 RTM:
Going by the message, “Permission denied for .. to get property Windows.frameElement from”, it looks like a cross-site frame protection issue. I don’t know if the update is responsible for this (Firefox 3.6.8) or this is also the behaviour of earlier Firefox versions. I checked it against IE and that has no issue.
So far for multi-browser support.
As a follow-up on the Exchange 2003 SP3 / Exchange 2010 RTM installation issue, I tried to collect information on the Exchange schema versions provided through Active Directory. This information is available after preparing the forest or domain for a certain Exchange version level.
You can find the information and information on how to use it here.
Exchange fellow Johan Veldhuis blogged about something interesting (or rather, something silly) which you should know about when planning to deploy Exchange 2010 RTM in an Exchange 2007 environment.
Apparently, the Service Pack 3 for Exchange 2007 raises the version number of the schema above the version number set by Exchange 2010. This will result in the following error message when trying to upgrade the schema:
Setup encountered a problem while validating the state of Active Directory. The Active Directory schema version (14625) is higher than the Setup’s version (14622). Therefor, PrepareSchema can’t be executed.
The result: You can’t perform the schema upgrade for Exchange 2010 RTM in an environment where Exchange 2007 SP3 is already applied.
Now this information is not only of interest to current Exchange 2007 users, but also to clients wanting to migrate from Notes to Exchange 2010 for instance. They might want to make use of Exchange 2007 for running the Transporter Suite to connect Notes to Exchange. Implementing Exchange 2010 RTM first is also not an option, because that would prevent the installation of Exchange 2007.
Given this information you could assume the following order of installation would prevent this issue:
But alas, when trying the perform the PrepareSchema of Exchange 2007 SP3 against an Exchange 2010 RTM prepared organization we are presented with the following message:
The exchange organization does not support this version of exchange server
When I retried the same thing but with installing an Exchange 2007 SP2 server , the operation seems to work, i.e.
I also did an Active Directory compare using ADexplorer comparing the PostEx2007SP2-PostEx2007SP3 situation against the PostEx2007SP2-PostEx2010RTM and it showed nothing of interest really, besides the usual ChangedOn, CreatedOn and GUID differences and some changes which had to do with the order of installation.
According to information in the Exchange Server Active Directory Schema Changes Reference dated June 2010, “Exchange 2010 makes the same changes to the Active Directory schema as Exchange 2007 SP2”. But Exchange 2007 SP3 makes some additional changes to the schema, which can be checked here. Looking at the explanation contained in that article, these changes may be required for environments attaching disclaimers to voice mail or fax messages. Of course, those changes won’t be there when you prepared the schema using Exchange 2010 RTM, so those environments using that functionality might expect issues in that area.
To wrap things up, unless it will become officially supported to run Exchange 2010 RTM in (directly) Exchange 2007 SP3 prepared environments, you have to be very careful with planning the order of installation for greenfield scenarios or scenarios where Exchange 2007 SP2 is in-place. I assume Exchange 2010 SP1 will solve the problem as the Exchange 2010 SP1 beta updates the schema to version 14718 (could change with release of SP1).
Microsoft released a tool yesterday to diagnose and troubleshoot configuration issues with Microsoft Exchange 2010 SP1 Unified Messaging. The Unified Messaging Troubleshooting Tool can be used to check call answering scenarios and voice mail functionality, in combination with OCS or UM deployments with IP gateways/PBXs.
The tool itself is actually a new cmdlet, Test-ExchangeUMCallFlow, which replaces functionality of the Exchange UM Test Phone. Because Exchange 2010 SP1 uses a new API, Unified Communications Managed API 2.0 Core SDK (UCMA), the Exchange UM Test Phone can’t connect to SP1 installations.
The Test-ExchangeUMCallFlow cmdlet emulates calls and runs a series of diagnostic tests to assist with identifying misconfigurations or connectivity issues in your Exchange 2010 SP1 Unified Messaging setup. Besides this information it will also output audio quality metrics to help diagnosing audio quality issues in relation to connectivity issues.
You can download the UM Troubleshooting Tool here.
Today Microsoft released a white paper by Greg Taylor (Sr. Program Manager, Exchange Server Customer Experience Team) on publishing Exchange Server 2010 with Forefront Unified Access Gateway 2010 and Forefront Threat Management Gateway 2010. This white paper contains information and guidance on publishing Exchange Server 2010 using Forefront UAG and Forefront TMG. This includes information on how to choose between UAG and TMG for different scenarios as well as steps on how to configure thos products in order to publish Exchange 2010.
You can download the white paper here.
EighTwOne (821) 