Nice article, however you don't speak about ACL in openldap. This part was the tricky one for
me, as you have to mix samba and kolab access to ldap.

If you compare slapd.conf from Samba and Kolab, you'll be able to write a mixed slapd.conf to
allow samba and kolab access, but as your users aren't stored in the same place as original
kolab installation, you'll have access problem.

In Kolab, your users are stored in the root of the ldap :

cn=test,dc=example,dc=com

In Samba, your users are stored in branch Users or People of your ldap :

I had problems being able to log into the Kolab webadmin (to administer the services, distribution lists, etc.) and also getting the Kolab accounts actually created if I used anything but the default rootdn that Kolab used (cn=manager,cn=internal,dc=...)

I just updated my Samba PDC to use the Kolab default rootdn and all was good.

On another note, on subsequent installs, I would unfortunately get a "Could log in to database; invalid credentials" error. I have not found a solution to that as yet, and it only pops up on some installs :-(

so if i trying to install php-mhash it will install php-4 and install it on my server while
the following article use embedded php from the kolab install so my question is how should i add phpmhash to that php used by kolab itself and getting rid of this error

Ok now if i log into the LAM using manager and create user, group,samba domain all these said that attribute created successfully but i can't see it in my passwd,shadow and even not a single home directory is created .
if i run the lamdaemon test it will show the following error:

Aren't you connecting to a non-Kolab webserver (i.e., Apache which was installed on that machine *before* Kolab?). Kolab provides its own Apache.

No i am using kolab webserver as i think whole document is based on that as we see LAM and PHPLDAPADMIN is untar in the /kolab/var/kolab/www
thats mean we have to use APACHE provided by the kolab itself