Hi Kevin,
There's currently no manual way to tell Entourage which autodiscover
server to use, however if you can provide us with some information
regarding
how your server environment is set up, we may be able to suggest a
workaround.
Regards,
Hui Nee Chin - huchinATmicrosoftDOTcom
Microsoft Entourage Test
Disclaimer: This mail is provided "AS IS" with no warranties, and confers
no rights.
On 6/27/08 4:29 AM, in article
barry-988441.12290327062008@[EMAIL PROTECTED]
"Barry Wainwright"
<barry@[EMAIL PROTECTED]
> wrote:
> In article <56B21BBD-967F-4E0E-AA05-5D725438DB3F@[EMAIL PROTECTED]
>,
> Kevin Bird <KevinBird@[EMAIL PROTECTED]
> wrote:
>
>> I think both answers haven't gotten at the true problem here... the
problem
>> is not in configuration at all. The issue is that even when properly
and
>> totally configured, the autodiscover service is polled (if it is the
same as
>> Outlook 2007 -- once per hour) and this information is used to locate
>> free/busy etc. When the client cannot find this information in DNS,
and
>> without a mechanism to locally override the autodiscover resolution
process
>> and point the client at a particular server for autodiscover
operations, this
>> process fails, thus causing free/busy, configuration of out of office
>> messages, delegate operations, and availability in meeting requests to
fail.
>> I have seen no place in the user interface nor a file location nor a
>> scripting parameter in Entourage 2008 to configure the override domains
and
>> specify the XML. Take a look at
>>
http://exchange-genie.blogspot.com/2007/07/autodiscover-ad-attribute.html
>> under the section "deploying an xml file" -- this is what I (and likely
>> others) need to be able to do, specify the domain with the local
location of
>> the file, and the xml in the file, and the option to prefer the local
vs the
>> network attempt.
>
> OK, sorry - I misunderstood your first query.
>
> I'm not aware of any mechanism that allows you to change the places that
> Entourage looks within the application. It may (should?) be possible to
> configure the location of the xml files defining the server information
> within the DNS server (set up a alias record to redirect the default
> autodiscover.domain.local to your preferred location), but I admit to
> being no expert in this type of set-up.
>
> I will escalate this query and try and get a more authoritative
> statement form MS.
|
