On 10/16/2015 09:41 AM, Steve Ankeny wrote:
On 10/16/2015 09:18 AM, Martin Simovic wrote:

On 15 Oct 2015, at 18:13, Chris Coleman <[email protected]> wrote:


On 10/15/2015 10:32 AM, Martin Simovic wrote:

On 14 Oct 2015, at 21:06, Chris Coleman <[email protected]> wrote:

You can try:
sudo openchange_provision --standalone --ignore_already_exists

This command line switch seems to be unimplemented: openchange_provision: error: no such option: —ignore_already_exists

I am using openchange 3:2.4-zentyal6 package from inverse repository. Maybe the way to go is to delete the CN=ms-Exch-Access-Control-Map attribute directly from directory? I am going to find out the hard way ..

Regards
Martin.
Sorry, try --ignore-already-exists (instead of --ignore_already_exists), e.g.
sudo openchange_provision --standalone --ignore-already-exists

Yes, that works, Thanks. Now I get further but:

root@pdc:~# openchange_provision --standalone --ignore-already-exists
NOTE: This operation can take several minutes
[+] Step 1: Register Exchange OIDs
[+] Step 2: Add Exchange attributes to Samba schema
[+] Step 3: Add Exchange auxiliary classes to Samba schema
[+] Step 4: Add Exchange objectCategory to Samba schema
[+] Step 5: Add Exchange containers to Samba schema
[+] Step 6: Add Exchange *sub* containers to Samba schema
[+] Step 7: Add Exchange CfgProtocol subcontainers to Samba schema
[+] Step 8: Add Exchange mailGateway subcontainers to Samba schema
[+] Step 9: Add Exchange classes to Samba schema
[+] Step 10: Add possSuperior attributes to Exchange classes
No elements to add found in /usr/share/samba/setup/AD/oc_provision_schema_possSuperior.ldif
[+] Step 11: Extend existing Samba classes and attributes
No elements to add found in /usr/share/samba/setup/AD/oc_provision_schema_modify.ldif
[+] Step 12: Generic Exchange configuration objects
[+] Step 13: Exchange Organization objects
Error: "(64, 'structural objectClass msExchAdminGroup is not a valid child class for CN=Administrative Groups,CN=First Organization,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=example,DC=com')" when adding element:

And I continue stuck. Still unable to provision entirely or deprovision either.

Best Regards
Martin.


didn't get a chance to do this until today . . .

mine was successful --

AND, I was able to configure and start 'openchange-ocsmanager' WITHOUT shutting down Samba-AD-DC That solves one problem I've had with DCERPC/OpenChange! Thanks for all who helped over the last few weeks.

Now, when I tried to setup the Outlook mailbox, I received the error --

"The name cannot be resolved. The requested operation failed because no search criteria were given to the Microsoft Exchange Address Book."

I followed the directions in the "Outlook Configuration Guide," pg 18

When I looked in '/var/log/ocsmanager/ocsmanager.log,' I found the following --

Starting server in PID 1885.
serving on http://127.0.0.1:5000
2015-10-17 07:44:28,313 INFO [openchange.web.auth.NTLMAuthHandler] [worker 0] client did not pass auth cookie 2015-10-17 07:44:28,321 INFO [openchange.web.auth.NTLMAuthHandler] [worker 1] client did not pass auth cookie 2015-10-17 07:44:28,358 INFO [openchange.web.auth.NTLMAuthHandler] [worker 1] acquiring lock /var/cache/ntlmauthhandler/ntlm-127.0.0.1.lock (1885) 2015-10-17 07:44:29,019 INFO [openchange.web.auth.NTLMAuthHandler] [worker 2] acquiring lock /var/cache/ntlmauthhandler/ntlm-127.0.0.1.lock (1885)

So, it appears to be an authentication issue. Any suggestions on where to start?

As far as I know, it's using HTTPS & SSL (it gives me the certificate) I added 'autodiscover.smbdomain.com' to the hosts file on the Windows Remote Desktop Server where the client resides (and, it "pings" correctly)

I get no response from '_autodiscover._tcp.smbdomain.com. IN SRV 0 0 443 sogo.smbdomain.com.'

Maybe I need to add a CNAME to my Samba DNS records?

Anyway, I appreciate any ideas I can try in troubleshooting the problem.

--
[email protected]
https://inverse.ca/sogo/lists

Reply via email to