Exchange UM doesn’t answer calls after SP1 upgrade
During an upgrade to Exchange 2010 SP1 I had a nasty problem. After the upgrade of the Unified Messaging server the server didn’t accept any calls.
During an upgrade to Exchange 2010 SP1 I had a nasty problem. After the upgrade of the Unified Messaging server the server didn’t accept any calls.
Generally translations in most software is very accurate. The one I discovered can be found in the Exchange 2010 SP1 Exchange Control Panel (ECP).
The process of installing a rollup for Exchange 2010 can take a lot of time when you have a bad/no internet connection. One of the causes for this is the validation process of the digital signature of the .NET Framework components. When having a bad/no internet connection this can slow down the process, this because of the default time-out of 15000 miliseconds for a single CRL check up to 20000 miliseconds for checking all CRL’s.
Since the release of Exchange 2010 Service Pack 1 the steps for configuring OCS/Lync IM integration for OWA has changed.
Forefront Protection for Exchange 2010 makes it possible to check messages for virusses and spam. Just like every other software Forefront can send messages when an infected message is found. By default Forefront generates an e-mail address during the installation. This may be something you don’t want but where can you change the e-mail address? You would expect that it can be changed in the console but you won’t find it there. To change the e-mail address you will need edit the registry.
Since Exchange 2010 both Outlook 2007 and 2010 will download the offline address book (OAB) by using the Exchange Web Services and not via Public Folders just like Outlook 2003 anymore.
Windows 2008 R2 contains a new version of the file server resource manager (FSRM) which has been improved a lot. One of the options this tool has is to send notifications for example when an alert is activated. Normally this is really easy to configure, the only thing you need is a mailserver which will accept the traffic and will deliver the e-mail.
Despite a lot of people will use an antivirus/antispam solution in the cloud some people will like to have an additional Exchange aware antivirus product installed on their Exchange servers. One of the products which can be used for this is ForeFront Protection for Exchange 2010.
During a migration at a customer I had the following issue, one I haven’t seen before. Selecting the target database went fine but when submitting the move request this resulted in the following error:
As you may already know there are two versions of Exchange 2010 available: