Migrate Exchange 5.0 to Kolab 2

Alex Chejlyk alex at swiftnetcomputers.biz
Wed Aug 30 18:20:36 CEST 2006


Martin Minkler wrote:
> Alex Chejlyk schrieb:
>
>> The way I've always done it:
>>
>> Connect Outlook to exchange.
>> Export the contacts to a pst. If you have more than one contact list, 
>> export them all separately so each has its own pst. I do this for 
>> safety and archiving.
>> Export the calendar to a pst and a csv. I've had issues with 
>> recurring appointments (never ending until 2032), the csv seems to 
>> get rid of them ;-)
>> If you have more than one calendar, export them all separately so 
>> each has its own pst. I do this for safety and archiving.
>>
>> Disconnect from exchange.
>>
>> Create the shared addressbooks, calendars, etc using the Toltec 
>> connected Outlook.
>>
>> Copy the items from the pst into the appropriate shared areas 
>> (contacts, calendars, etc).
>>
>> That has always worked for me.
>>
>
> Thank You very much for Your quick answer. This sounds like a safe and 
> sound method to me to migrate, admittingly I simply tried exporting 
> the whole exchange-connected personal folder including all subfolders 
> to a pst, then opening that pst with outlook and only then mapping 
> that pst to kolab via toltec - worked like a charm :-)
>
> The problem we now have revolves around email addresses - the exchange 
> users listed in the global ldap address book on the exchange server 
> are exported as I described - in ldap format instead of valid 
> user at domain.tld addresses.
>
> The mail address field contains something like
>
> /o=First Organisation/ou=First administrative 
> Group/cn=Recipients/cn=<name>
>
> Now if I could get the global ldap address book of the kolab server to 
> work it would be feasable to re-create all the local users in that 
> address book, but somehow I cannot seem to do any good or bad.
>
> The search base and server are all set as described in the pdf and the 
> external users I create on the server via the web interface are 
> visible there all right, but with no combination of search base dc's 
> and cn's did I manage to make a single entry show up on the clients - 
> but no error report either, simply an empty list.
>
> Entering the search base that's shown in the web interface when an 
> external user is created on the kolab server doesn't work.
>
> I had a look at /kolab/var/openldap/openldap.log and other logs but 
> didn't find anything.
>
> Anyway: Shouldn't there be a global address book of _internal_ users 
> existent on the kolab server available (under a different search base 
> maybe) as well? That would be sufficient for us as those are the 
> entries that we cannot get out of the exchange server in the proper 
> format but that we already manually created on the kolab server anyway...
>
> confused
>
> Martin
>
>
Are the internal users marked as Internal (Type "I") when you view them 
in the Kolab web administration page? If they are, they won't show in 
the address book. They must be Type "U".

-- 

Cheers, Alex C.




More information about the users mailing list