On 10/13/06 4:00 PM, "Pertschi, Darrin" <[EMAIL PROTECTED]>
wrote:
> Peter,
> Yeah, it¹s looking like that is the case; only seeing changes after the Sync
> (not send/receive).
>
> Remo,
> I remember reading that the front-end does not support delegation or GAL when
> in reference to working outside the network from a public net connection. What
> about when plugged into the LAN? Will delegation and Gal work since I¹ll have
> a valid internal LDAP server specified in the account prefs?
>
> Thank you all for the feedback by the way...
It seems as if we're talking about a couple of different things here, and
perhaps confusing some terms. Let's try to demystify.
1. "GAL access" ... you can browse the GAL (and other address lists) using
only the front end server, which is defined in the Entourage Exchange
account settings. However, this generally only lets you _browse_ in
Entourage, using the Address Book. If you're searching (as when composing a
new message), you're not necessarily using the newer GAL access. Instead ...
2. Global Catalog access ... this requires access to a Global Catalog
server via LDAP/LDAPS and is often blocked by the organization running
Exchange, presumably for security reasons. The Global Catalog server is
defined separately from the Exchange server in the Entourage Exchange
account settings. You're probably using this for almost all address book
lookups that require _searching_.
3. Delegation ... use of outright delegation -- the "act on behalf of"
privileges, as opposed to sharing ("you can see my data") privileges --
requires access to a back end server and cannot currently use SSL in
Entourage 2004 SP2. Sharing can work with access only the front end servers
(so I can see colleagues' calendars, for example), but delegation does not,
currently. My experience, and YMMV, is that Sharing is needed more than
Delegation.
4. The background Exchange sync schedule is, as I recall, 2 minutes. Sync
can be forced manually with "Send/Receive All" as of Entourage 2004 SP2; I
believe it affects all Exchange mailboxes that are defined within that copy
of Entourage (including Shared mailboxes). You may get more frequent syncs
or update notices if you are within the same LAN as your Exchange servers
and can receive UDP updates. Certain folders may have more priority than
others in the sync process (i.e. it stands to reason that your Inbox might
sync first).
As for the actual problem with sharing a mailbox in this manner, I'm not
sure why Entourage is not catching on to the changes if they are visible
within OWA. I don't think I have 12 people sharing a mailbox, though.
It sounds like you have Outlook/Win users implicated, as well. Are they in
cached mode? I'm wondering if the delay you're seeing is just because
everyone is performing a sync, as that could _potentially_ lead to ~5 minute
delays. (Two minutes on the originator, two minutes for the receiver.) But
generally, I see changes made in Entourage sync up to the mailbox right
away. The background process of getting updates Entourage _wasn't_
previously aware of is, as I recall, every 2 minutes.
Are you seeing any errors in the Entourage Error Log (Window > Error Log)
during sync? There are occasionally errors in synchronizing data,
particularly to shared mailboxes -- and may be related to your version of
Exchange, or patches applied.
As for the rationale for pointing Entourage users to the front end as a
matter of course, is simply that the front end is usually available both
inside and outside your network. Listing the front end server address
(preferably a generic address that points to your front ends in a generic
sense, perhaps even with load balancing or round robin) as the Exchange
server within the Entourage Exchange account settings means that your users
will have fewer differences in behavior, and less need for workarounds like
VPN access, when they are local to your LAN and remote/mobile.
However, this assumes that you provide direct access to your front end
servers (rather than going through ISA servers, for example); if you cannot,
then you already have some problems setting up your Exchange environment to
be entirely Entourage-friendly. You may have others, as well.
Assuming you have back end server access when you need it (i.e. delegation,
servers for which can be configured separately, see the "Advanced" button
under the Delegation tab in the account settings), an appropriate VPN tunnel
when back end server access is needed remotely, and an ISA server is not
involved, I see no downside or caveats to front end server access _all the
time_. I do this and we recommend it for my whole site.
The Setup Assistant guides you to settings which should _work_ but they are
not necessarily _optimal_ for your site. Because they are derived from
Global Catalog queries, they return answers that point to back end servers
by default.
A _lot_ of this detail is covered in the MacEnterprise.org Webcast from June
and that could be where you've seen some of these details mentioned before.
HTH.
--
Jeremy Reichman
--
To unsubscribe:
<mailto:[EMAIL PROTECTED]>
archives:
<http://www.mail-archive.com/entourage-talk%40lists.letterrip.com/>
old-archive:
<http://www.mail-archive.com/entourage-talk%40lists.boingo.com/>
