Setup IFD With Exchange Server Installed
Posted December 23rd, 2008 / No Comments
A SQL guru in our office put together this document on how to setup an IFD with Exchange Server installed:
1. Install the IIS resource kit.
2. Navigate to the CRM4IFDtool.exe
3. Set the tool to these settings.
4. Set Authentication to IFD+OnPremise
5. Add the local subnets that will not be using external addressing.
6. Set the external to https and app root to external name:plus crm port
7. Set the internal app root name: plus port. Find the site ID that you want to add the certificate to. IISweb.vbs /query “name of site using http name.” Look at the first column (“default web site <w3svc/1>. The 1 tells you the ID number for this site. Enter it in the command below “/S:#”
8. Then create a self-signed certificate.
9. Open All Programs, IIS resources, self-signed. Type selfssl.exe /N:CN=”certname” /K:1024 /S:1 /P:443
10. This will add the certificate to the server’s web site.
11. This does not put the certificate in the trusted store for the machine.
12. Open cmd line and type mmc.
13. Select File, then select Add/Remove Snap-in.
14. Select ADD and Certificates.
15. Then select ADD, Computer Acct, Next, Finish, Close, and OK.
16. Expand certificates to trusted store, certificates.
17. Now open IIS Manager.
18. Right click on the CRM site and select Properties. Select Directory Security, Server Certificate. You will go into a wizard mode (you are going to export the certificate to add to trusted certificates).
Select Export the current certificate and NEXT. You can select any path as long as you can get to it from the machine. Set a short password and mark key as exportable. Next, click Finish.
19. Import the certificate to the trusted store. Right-click the certificate folder. Select All Tasks, and then select Import.
Select Next and Browse. Change file type to .pfx. Select File and OPEN.
Click on NEXT and type in short password created from export, NEXT. Mark key as exportable. The Trusted Root Certificate store s/b selected, NEXT and Finish.
21. Close MMC you do not have to save the console, and close IIS.
22. If the above example is exact and you are using port:555 for application then you will need to have network admin allow the port through the firewall to this server
23. Add a public dns name to their external zone (ex: crm.XXXXX.com)
24. Test the application. Have a user open https://crm.XXXXX.com:5555
