http://www.itstuff.ca/2009/12/blackberry-enterprise-server-fully.html

Good stuff here, we have already been looking at migrating to Exchange 2010 so this is really good news for us.

A co-worker of mine found this support article which fixed the issue and saved my bacon.

SYMPTOMS
When you start Microsoft Office Outlook 2007 and then connect to a mailbox that is hosted on a mailbox server that is running Microsoft Exchange Server 2007, you receive the following security warning message:

The name of the security certificate is invalid or does not match the name of the site.

CAUSE
You replace the default self-signed Exchange 2007 certificate with a different certificate.

By default, the URL that is stored in these objects references the NetBIOS name of the server. For example, a URL that resembles the following URL is stored:

https://NetBIOS_name.contoso.com/autodiscover/autodiscover.xml

This may differ from the host name that is used in the FQDN of the replacement certificate. For example, the replacement certificate may have an FQDN that resembles the following FQDN:

mail.contoso.com

This issue causes a name mismatch error to occur. Therefore, you receive the security warning message when you try to connect Outlook 2007 to the mailbox.

RESOLUTION
To resolve this issue, modify the URLs for the appropriate Exchange 2007 components. To do this, follow these steps:
1. Start the Exchange Management Shell.
2. Modify the Autodiscover URL in the Service Connection Point. The Service Connection Point is stored in the Active Directory directory service. To modify this URL, type the following command, and then press ENTER:

Set-ClientAccessServer -Identity CAS_Server_Name -AutodiscoverServiceInternalUri https://mail.contoso.com/autodiscover/autodiscover.xml

3. Modify the InternalUrl attribute of the EWS. To do this, type the following command, and then press ENTER:

Set-WebServicesVirtualDirectory -Identity “CAS_Server_Name\EWS (Default Web Site)” -InternalUrl https://mail.contoso.com/ews/exchange.asmx

4. Modify the InternalUrl attribute for Web-based Offline Address Book distribution. To do this, type the following command, and then press ENTER:

Set-OABVirtualDirectory -Identity “CAS_Server_name\oab (Default Web Site)” -InternalUrl https://mail.contoso.com/oab

5. Modify the InternalUrl attribute of the UM Web service. To do this, type the following command, and then press ENTER:

Set-UMVirtualDirectory -Identity “CAS_Server_Name\unifiedmessaging (Default Web Site)” -InternalUrl https://mail.contoso.com/unifiedmessaging/service.asmx

6. Open IIS Manager.
7. Expand the local computer, and then expand Application Pools.
8. Right-click MSExchangeAutodiscoverAppPool, and then click Recycle.

Source: http://support.microsoft.com/kb/940726

Certificate, Exchange Server, Outlook

http://www.msexchange.org/tutorials/Exchange-ISINTEG-ESEUTIL.html

I know of many occasions where this has been required to get Exchange up and going in a crunch.

I found this article really helpful:

http://www.aspfree.com/c/a/BrainDump/Migrating-to-Exchange-Server-2007/1/

Overall I had to say I found the proccess really simple. The install lets you specify your existing exchange environment and auto creats the routing between them.

Migrating mailboxes was a one click seamless move.

Now if I could only figure out where Microsoft moved all the settings I need. Sigh.

To fix this you need to get rid of a key in the registry.

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Exchange

You can export it, do the install and import it back if you need but it needs to be gone for the install to work.

Here was the error when trying to activate.

{e} MAPIMailbox::MAPIMailbox(2) – OpenMsgStore (0x8004011d) failed

A reboot of the exchange server followed by a reboot of the BES server fixed the issues but we weren’t sure if this was a coincidence or caused by switching the VM’s over to a different Virtual Center server

Shortly after that we moved over a different set of Exchange server and BES servers and the exact same issue occurred.

Be aware!

Best practice I have found when doing the migration is to use a POP connector on your Exchange server. This allows for a gradual migration and eliminates any lost email during the time when you are changing over the MX records.

Microsoft includes a free POP connector with Windows Server 2003 SBS and yet for some unknown reason doesn’t include one with the real version of Exchange. Still, using SBS is in fact it’s own punishment so it’s not a huge loss.

I recommend the Exchange Connector product by Quantum Software Solutions. It’s really straight forward to use and very customizable. You get a 30 day free trial, which is all you need if you are only using it for migration purposes, though I think it is well worth paying for if you think you are going to use it on a ongoing basis.

Here is the link

http://www.quantumsoftware.com.au/

http://www.bbhub.com/2007/01/08/bes-admin-my-email-is-not-synching-properly/