Hi Derek,
to 1.
in your enviroment you have to install the CRM Router on each Exchange
machine. The CRM Router only listen to the smtp port and send a notification
to the crm server, if there is a mail, for the crm users.
There is no negative effect on the Exchangeserver, after your default
installation.
to 2.
you can go on with the default port an default url. During the installation
the system is only asking, where and which name has the crm server. if you
want to change the port, pleasse go on with the following steps:
You can create a new website on the Exchange Server to house the Microsoft
CRM Exchange Connector.
Note - If IIS Lockdown is installed you will need to restore the default
settings by launching IIS Lockdown and restoring this.
Create a New Website.
1. Right Click on the machine name in IIS and choose New Website.
2. Choose Next.
3. Provide a Description (This is what will be seen in IIS) I will call this
CRM Exchange.
4. Choose Next.
5. Enter the IP Address, this can be specified as all unassigned or we can
specify the same IP address that the default website is bound to(ipconfig
from a command prompt will return this IP for you.)
6. Specify a different port than what the Default site is running under. I
will use port 81 in my example. (netstat -a will show all open ports if ran
from a command prompt).
7. Specify a host header. This will correlate to a DNS entry that we will
enter in future steps.
In this example, I will use crmex as the host header.
8. Choose Next.
9. You are now going to create a directory to house the CRM Exchange Website
files. This directory can be located anywhere on the machine. Typically it
is located in the following directory \Inetpub\wwwroot\ It is located in
this directory for manageability reasons. For this example I will create a
directory called CRM Exchange located in the following: \Inetpub\wwwroot\CRM
Exchange\ this is done through Windows Explorer.
10. Back on the Web Site Creation Wizard; Choose Browse and navigate to the
CRM Exchange directory created in the previous step.
11. The Allow Anonymous Access to this website can remain checked. (You do
not have any files that will be loaded in this directory that can be
exploited by scripts directly) The allow anonymous access can be unchecked
as well. This check box can be removed as well. Security preference, so it
is not required.
12. Choose Next.
13. In the next window, leave the defaults(Read, Run Scripts).
14. Choose Next.
15. Choose Finish.
The CRM Exchange Website should now be created. We can now create an Alias
Record in DNS so it recognizes when we type http://crmex in a web browser it
knows what site to access.
16. Launch the DNS console; Start | Programs | Administrative Tools | DNS.
17. Expand the machine | Forward Lookup Zones | domain.
18. Right Click on the Domain and choose New Alias.
19. Provide the Alias Name. This will be the same as we specified in step #7
from above. In our example: crmex.
20. Provide the Fully Qualified Name for target host - For this you will
browse out and choose the Host file for our Exchange Server.
21. Choose OK.
22. You should now see a record in DNS that shows crmex as a type of Alias
and Data of your Exchange Server(cwebex1.cweb.local in my example).
23. You may need to stop and start DNS. Not Required, but typically
recommended for this to propagate to all DNS servers if there are multiple.
We should now be ready to install the CRM Exchange Connector:
24. Setup.exe on the CRM Server Disk #1 in the Exchange Folder.
25. Accept the License Agreement and Choose Next.
26. Add the CRM Server: Machine Name as seen in Network Identification on
the CRM Server. In my example cwebdell.
27. Add the Microsoft CRM Website URL: http://crm or http://cwebdell In this
example a DNS alias(crm) has been created for the CRM website, so either of
the sites listed will resolve.
28. Choose Save and Choose Next.
29. Enter the Login information to start the services: This should be the
user that has Enterprise Admin Rights and Schema Rights. This maybe the same
user that installed CRM if they have these rights or use an Exchange
Administrator. This goes back to the case where the Enterprise Admin and the
Schema Admin has access to the mailbox store as I discussed in the very
first step #1.
30. Choose Next.
31. We will now choose the Web Site we created to house the CRM Exchange
Connector files: CRM Exchange as defined in step #3.
32. Installation directory can reside in the default or any drive if space
is an issue.
33. Choose Next.
34. Choose Install.
The CRM Exchange Connector should now be installed. We now need to confirm
the registry entries.
On the CRM Server:
35. Start | Run | Regedit.
36. HKLM\Software\Microsoft\MSCRM\mailserverurl\
a. This will potentially look like the following:
http://cwebex110.6.6.7:81:ex/MSCRMCo...ilDispatch.SRF
b. We need to edit this to look like the following:
http://crmex:81:/MSCRMConnector/ICRMEmailDispatch.SRF where crmex is the
alias we have defined in both the host header information for IIS on the
Exchange Server and the Alias entry we created for DNS.
37. Once edited we will need to Stop and Restart the CRM Exchange Queue
Service on the Exchange ServeràStartàProgramsàAdministrative ToolsàServices
38. You should now be able to test and send emails.
--
Ich hoffe, das hilft / I hope, this helps.
Freundliche Grüsse,
Alfred Göbel (MS)
(Microsoft kann für die Richtigkeit und Vollständigkeit der Inhalte in
dieser Newsgroup keine Haftung übernehmen.)
"Derek Tinney" <dtinney@shaw.ca> schrieb im Newsbeitrag
news:OIT7debAEHA.132@TK2MSFTNGP10.phx.gbl...
