Microsoft Dynamics CRM – Steve Suh

I tried installing the e-mail router with forwarding rules from CRM 4.0 to Exchange 2010 (E14). 

The Environment:

CRM Server – Windows Server 2003, Dynamics CRM 4, Rollup Update #4

Exchange Server – Windows Server 2008, Exchange 2010 E14 beta

Some findings:

1. Outgoing e-mails works fine with the router.  Two things I had to change to make it work though were making sure the Exchange Server name matched the certificate name for the exchange server.  The other was for the Access Credentials when Other Specified was selected to not use theDomain\Administrator account.  This appears to be an account that Exchange does not allow to send e-mails.  I changed this to another service account that had rights to CRM as well (just in case) and got the e-mail router to work.

 

2. Accessing the Forward Mailbox does not work.  There were two prerequisites for the Forward Mailbox option to work that Exchange 2010 does not have. 
   • One is WebDav, this looks to have been deprecated  (http://social.technet.microsoft.com/Forums/en-US/exchange2010/thread/7aabb536-b226-4d01-ada4-d1271b46fdfa).
   • The other is the existence of legacy IIS virtual directories for Exchange and ExAdmin.  When Testing Access with for the forward mailbox it returns errors repeating 404 or general timeouts when trying to access the mailbox.  When reviewing the IIS logs the router looks like it’s requesting the /Exchange/[Mailbox_Name] and the /ExAdmin/Admin/[Domain]/MBX/[Mailbox_Name] and both of these return a 404.  For Exchange 2007 you can create these via the powershell command new-owavirtualdirectory with the -owaversion parameter.  But this parameter is not available with the current bits.