On 10/4/06 5:03 PM, "Elliott Hill" <[EMAIL PROTECTED]> wrote:
> The LDAP server entry is so that entourage can have access to the Exchange > Global Address List. So which ever server houses the AD/GAL, this address > should go here. LDAP runs along side AD so you don¹t need to do anything more > as far as activating LDAP. The LDAP server entry should be one of your Global Catalog servers, to be specific about it in case you need to talk to Exchange admins. I would strongly suggest you see if a "generic" hostname can be set up to point to alias to one or more of your Global Catalog servers. Maybe something like "globalcatalog.company.com" would do, but that's up to your org. This would let you put a generic name in the LDAP config in Entourage and any other LDAP client that needs GC access, and it's much better than specifying an individual GC server by name (what happens if you replace that GC server with another, or it goes down expectedly or unexpectedly?) and definitely better than IP address (ditto). Access to the Global Catalog is often blocked outside of an organization's network -- so you may have problems with home/remote/laptop users. They may need to set up a VPN tunnel to your org's network, if you have that service available to them. I note, Frank, that you specified the following setup: > 11.2.1 (051004) > Mac OS = 10.47 > OWA address 192.xxx.xxxx.xxx/exchange I would highly recommend that you specify a generic name for your OWA front end server(s) -- again, if you don't have a generic name for the front end servers, I'd alias one. The actual Exchange server field in Entourage is very flexible now, and the Webcast noted below mentions some of the options you can use when filling it in. Also, for setup of Entourage in a larger environment, you should be aware that it's very scriptable. If you check the archives of the MacEnterprise.org mailing list, you'll find a recent thread with an example AppleScript script that should help in setting up any number of Entourage clients for Exchange. We also have our own script developed in-house, and you can save time/effort and get better, more consistent results. The Setup Assistant is geared towards getting you up and running with values it can discover from the Global Catalog. Those discovered values may not be the _best_ values for your org's goals or Exchange environment. It can pay to tweak them. Note that, to the best of my knowledge, Entourage will not negotiate its WebDAV or LDAP connections up from non-SSL _to_ SSL, so if you're going to enable SSL for either/both of these protocols, you should do it upfront and check the relevant checkboxes in each client you configure. That way, you won't have to revisit each one. If your Exchange and Global Catalog get certs that are rooted to a commercial certificate authority, you'll also have easier setup than you would if you used a self-signed CA (which you'd have to import into Mac OS X's X509Anchors keychain). You definitely _should_ upgrade to a newer release of Entourage; v11.2.1 is more than a year old now. I can suggest some resources for understanding Entourage clients more thoroughly: * the Microsoft Office 2004 Resource Kit v2, on the MacTopia site (www.microsoft.com/mac) * the June 2006 MacEnteprise Webcast (www.macenterprise.org, look for Webcasts) on Entourage and Exchange * the Microsoft KB, which has articles on Entourage * the Entourage MVPs site. ... these can help you understand how it works with Exchange. I know we have a number of users who also see spinning beach balls in Entourage on a periodic basis. You may want report this issue to Microsoft through your sales/support channel, particularly if you have a support contract. In the meantime, disabling software that may poll the Entourage database _might_ help reduce the problem; I can't say it's been effective for me yet. Anti-virus software, application launchers that index Entourage data (such as LaunchBar and QuickSilver), and other tools (like EntourageABmenu) is at least possibly related; I can't say for sure. As for cached mode, yes, Entourage is always in cached mode today. We've had problems with both Entourage and Outlook that may be related to the caching, but they may not either. I can't say that I have a reproducible problem scenario that is specifically caused by Entourage's caching. While Outlook and Entourage use different protocols to communicate with Exchange, blaming issues on MAPI/RPC vs. WebDAV at the protocol level is -- to me personally, at least -- a red herring until proven otherwise. 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/>
