Configure the Dynamics CRM 4.0 Outlook Client for an Internet-Facing Deployment
Posted Wednesday, June 24th, 2009
An Internet-Facing Deployment allows users that are not on the internal network of your organization to access Microsoft Dynamics CRM through the web. This functionality is great for those that are in and out of the office or on and off the local network. Like most of us, having CRM accessible through the web is great, but what about the Outlook Client? We all live in Outlook, so below is a scenario and a few helpful hints about configuring users’ Outlook Clients for an Internet-Facing Deployment.
Scenario
- The customer has an IFD set up for its CRM 4.0 users.
- Users outside the domain have configured their outlook client using “Service Provider.”
- Currently, when these users are outside of the local network, they do not have an issue accessing CRM. (They can get to CRM through both the Web and Outlook)
- When users are in the office and connected to the local network, they CANNOT connect to CRM through OUTLOOK.Â
- When users are in the office and connected to the local network, they CAN access CRM through the web successfully.
Process
It is important to have the users configure their Outlook clients while at the office on the local network. The only time that we can configure the Client for both internal and external URLs is while the client workstation is in the office on the local network.
- Â When the users are on the local network, have them configure the Outlook Client using “My Company.”
-
During the configuration, users will come to the option to enter an internal and external URL.
- There will be a check mark between the text boxes. Â Remove the check mark and enter the internal URL used to access CRM. Â For example: Â http://crm
- Then enter the URL that they are using to access CRM through IFD while outside the office in the external URL text box at the bottom. Â For example: http://crm.infinity.com
Â
- Continue to step through the configuration until it completes.
- Restart Outlook.
- Disconnect from the local network, and confirm that the outlook client can still be accessed with full functionality.
Assessment
What we have successfully accomplished is the ability for users to work in the Outlook Client, both on and off the local network. When the users are connected internally, the Outlook Client will connect to CRM using the internal URL by default. Once they leave the internal network, the Outlook Client will attempt to connect using the internal URL, but when it sees that it cannot, it will then use the URL used to connect through IFD.
If we were to configure the Outlook client as ‘Service Provider,’ we do not give users the ability to use the Outlook Client on the local network. This occurs because they have not defined an internal URL for CRM.
As always, if information such as this does not resolve your issue, documentation from Microsoft should be referenced. This post should not replace documentation from Microsoft; however it can serve as a guide to solving your problems and as a helpful reminder.
Tags: IFD Configuration for Outlook, Local Network Access in CRM, Service Provider Access
Posted in Dynamics CRM, IFD, Outlook Client
Not yet using Dynamics CRM? I.B.I.S., Inc. gives you the Dynamics CRM options you want, and the business results you need.
Learn more about our Dynamics CRM solutions
I’m trying to configure CRM for Outlook, but it won’t accept the URL that we use to get to CRM online:
https://companyname.crm.dynamics.com/loader.aspx
Is there some other URL I should be using? I’m totally confused.
You do not need dynamics or https. Try one of these: http://companyname/orgname/loader.aspx or http://orgname:portnumber/loader.aspx for example: http://abc02/ABC/loader.aspx or http://abccompany:5555/loader.aspx ….. or you could try this. Copy from http:// through to before the first / when you are in the main CRM screen on your IE browser. Paste it into the area inside of the configuration wizard.
Tried to give you a few options. Hope one of them helps.