Elias
Tue May 02 03:43:01 CDT 2006
Thanks for that suggestion. Unfortunetly we and our clients
use hostheaders to access the crm webpage.
For Example:
http://customer1/loader.aspx
So this workaround doesn't work in this case.
Regards,
Elias
"Waite, James A" <james.waite.nospam@mapson.obsltd.com> schrieb im
Newsbeitrag news:OwoM6aeaGHA.3532@TK2MSFTNGP05.phx.gbl...
> This would seem to be a known issue.
>
> This work-around was provided to me by MS.
>
>
> A. Change the URL that the CRM Outlook Client computer is using
> (HKEY_CURRENT_USER\Software\Microsoft\MSCRMClient). to the IP address of
> the CRM server instead of the name of the server.
> 1. Click on Start->Run and type regedit to open the registry editor.
> 2. Backup the registry by clicking on File->Export and save the file in a
> location.
> 3. Now make the changes to the CRM URL
> (HKEY_CURRENT_USER\Software\Microsoft\MSCRMClient) to the IP address
> instead of server name.
> 4. Exit out of registry.
>
> B. Then add that IP address to the Local Intranet or Trusted Site zone in
> Internet Explorer. (In the IE window, click on tools->Internet options
> and
> click on the security tab to do this.)
>
> Care should be taken when editing the registry blah blah blah....
>
>
> James
>
>
> <stephenejones@yahoo.co.uk> wrote in message
> news:1146129261.934072.276280@y43g2000cwc.googlegroups.com...
>> Looks like Microsoft are shirking their responsibilities again with
>> this one!
>>
>> Yet another in a long-line of real oddities of CRM!
>>
>> I agree, its not an acceptable solution - we're looking at a
>> large-scale implementation of CRM, and we have numerous complexities -
>> clients not in domain, the guys who manage the desktops/CRM roll-out
>> have no control over DNS (which is hosted by a different team with
>> Unix, not with AD), etc. We simply can't spend lots of time having to
>> modify client settings all the time (FQDN, DNS aliases, IP addresses)
>> simply because MS won't identify and address these issues (certainly
>> not until a Service Release!). If Sun Microsystems did this approach,
>> it would get slaughtered! (and MS wonders why there's a slow take-up of
>> MS stuff in the Higher/Further Education sector!)
>>
>> Steve
>>
>
>