locked
Outlook client for non-domain notebook RRS feed

  • Question

  • Hello,

     

    we had CRM running in AD only mode, which worked fine even from outside of domain, using windows-auth. Worked for everyone, except when trying to install outlook client which wasn't joined in domain. Configuration would fail with Unauthorized 401 error, as the outlook client did not send WA auth. 

     

    Then we've changed it to AD+IFD configuration. This is annoying, because now we have to login to CRM web from outside (previously WA would login automatically). But this made Outlook client installation on non-domain PC possible using "online service provider" setting. However, this only works when the PC is not connected to domain network. When it comes to domain network, the outlook client does not connect.

    So what should we do?

    Wednesday, May 26, 2010 4:01 PM

Answers

  • Hi,

    If you will be using the outlook crm client on a machine that is NOT part of the domain you will need to configure IFD authentication.  If these machines that are NOT part of the domain will also be using insider your corporate network, then in the IFD configuration you should ONLY include the ips/network of your server. 

    The ifdconfig tool is used to specify all the ips/networks where on prem integrated authentication will be occuring -- for this to work ok with the outlook crm client they need to be on a workstation that is a domain member.

     


    Alex Fagundes - www.PowerObjects.com
    • Marked as answer by Jim Glass Jr Tuesday, June 1, 2010 5:39 PM
    Wednesday, May 26, 2010 9:01 PM

All replies

  • The CRM Outlook Client on a machine that isn't a member of the domain is not supported. It will give you troubles as one of our clients discovered. Possibly have that user/pc connect via IE ?
    Jerry http://www.crminnovation.com
    Wednesday, May 26, 2010 8:02 PM
  • Hi,

    If you will be using the outlook crm client on a machine that is NOT part of the domain you will need to configure IFD authentication.  If these machines that are NOT part of the domain will also be using insider your corporate network, then in the IFD configuration you should ONLY include the ips/network of your server. 

    The ifdconfig tool is used to specify all the ips/networks where on prem integrated authentication will be occuring -- for this to work ok with the outlook crm client they need to be on a workstation that is a domain member.

     


    Alex Fagundes - www.PowerObjects.com
    • Marked as answer by Jim Glass Jr Tuesday, June 1, 2010 5:39 PM
    Wednesday, May 26, 2010 9:01 PM
  • I see.

    Well, I guess the only solution is to join that workstation to domain. IFD configuration does not work when machine comes into domain network.

    Monday, May 31, 2010 4:10 PM