Thomas Schierle <[EMAIL PROTECTED]> wrote: >Entourage (in contrast of Outlook Client Mac) is meant to be a pure >RFC conformant client, therefore don't expect E. to connect to >Exchange provided calendars unless Exchange makes them fully >accessible via iCal.
I was once told that Entourage would understand �Invitations� from Exchange even if it wouldn�t act as a full peer with Outlook clients. I.e. that while Entourage wouldn�t act as an Exchange client as such, it /would/ understand stuff sent from Outlook given certain limitations. Since Exchange exposes your Calendar as just another IMAP folder I figured it�d be natural to enable some form of interaction here. >Well, if Exchange or Active Directory share their databases via LDAP, >there should be no major problem -- either ask your admin or give some >details... Exchange 5.5 ATM, but we do run a W2K AD (which two are not on speaking terms ATM AFAIK). A migration to Exchange 2k is in the cards, but we have some peculiarities in our configuration that makes this labour intensive to do without dataloss. Asking my admin would be a problem as in this context _I_ am the admin. Since I know pretty much nil about Exchange, AD, or LDAP,, I�d appreciate some hand-holding (think �small words, big letters� ;D) in getting Entourage to talk to Exchange, for starters, and AD, for the long haul. The local Microsoft Certified something-or-other manages the Exchange side, and I could probably figure the LDAP bit out given time, but I was kinda hoping there was a more elegant solution. >btw, why do you want to import five thousand Contacts if you have an >LDAP server available? Eventually E'rage doesn't permit to do so >because working from a local contact database is likely to spoil >corporate goals? ;-) I want to do it because right now I can�t talk to that LDAP tree at all and I want to have those addresses available without having to manually add each one. I expect there�s some reasonably easy way to dump the Exchange directory -- and munge it using Perl, or somesuch, to be importable into Entourage -- but I�d kinda like to hear from others before I start reinventing a square wheel. >You've done a lot of bashing (IMHO because not getting the distinction >between E'rage and Outlook Client right), �bashing� in what sense? My connotations to the word imply that you feel I�m critizising Entourage in some manner? I get the distinction between the two very, painfully, clearly. I tried to use Outlook:mac and decided it wasn�t worth the pain (running it in Classic on Mac OS X, talking to the Exchange server over a GSM dialup, hooked up to the laptop using IrDa!). Now I�m hoping I can coerce Entourage into doing the few things that are essential -- out of the myriad things Outlook /can/ do but which I don�t need -- so I can use that instead of resorting to just POPing mail and leaving everything else to memory and habit. >but you missed a major and valid >point -- the missing ability of E'rage to write to an LDAP database. Not an issue for me, at all. Apart from sending mail I need only read access to Exchange and the directory (whether it�s Exchange or AD). Being able to Update or send new Meeting/Event Requests/Notifications is nice, but not essential. I simply need easy (bi-directional) access to address-to-name mappings and the ability to get Entourage�s Calendar synchronized with my Outlook (i.e. Exchange) Calendar. -- 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/>
