Hi Mark, 
i’m trying a similar solution, I’ve provisioned my AD structure with
exchange 2010 tools but I’m having a lots of troubles. Openchange_provision
it’s not needed, but you have to provision openchangedb. Now the troubled
parts, my users are under an OU, so theyr CN are something like:
CN=Daniele,OU=EFFEGIDI,DC=xxxx,DC=yyyy. Openchange dislikes this kind of
structure, it expect something like CN=daniele,CN=users,DC=xxx,DC=yyyy. This
cause that openchange_newuser –create works only with administrator. What
I’ve done is to change some parts of provision.py sources in order to
correctly consider my OU. 
By this way I didn’t hit a success, I’ve simply changed kind of error, it
seems exchange 2010 AD structure provision differs from openchange
provision. Creating new users in openchange returns errors because it can
find some entries inside ad structure. 
Unfortunately I have not virtual machine with, I can’t be more accurate with
error messages and thing I’ve done to workaround ‘em. Anyway, if you can
step over these problems, please share!
Cheers,
 

Daniele Borini 

EDP Manager 

Effegidi International SpA

Via Provinciale per Sacca, 55 - 43052 - Colorno - Italy 

tel +39 0521319316 

fax +39 0521319322 

e-mail d.bor...@effegidi.it 

www.effegidi.it 

Prima di stampare,pensa all'ambiente ** Think about the environment before
printing 
 
  _____  

Da: Mark [mailto:mclar...@gmail.com] 
Inviato: mercoledì 8 maggio 2013 19:46
A: users@sogo.nu
Oggetto: [SOGo] Openchange with a member DC server
 
Hi all,
 
Was wondering if there are any special steps necessary for using openchange
with samba 4 as a member DC server. The samba server has replicated the AD
structure from the master which already has a exchange entry.
 
Running openchange_provision failed as there was already an entry for
exchange. I am not a windows administrator so not too familiar with AD
entries.
 
Should it just work if I point an outlook client at the ip address of the
sogo/samba server?
 
Will be testing it tomorrow when I get to a windows client tomorrow.
 
cheers

<<image001.gif>>

Reply via email to