I was hoping we might get some details from the dev's.
Apart from the RPC which might be a bit of an oversight or assumption of a gateway mode of employment.
Then when you create custom OU's which if you are going to use group policies then there is a good chance.
The user manager openchange details only show if the users are in the original users OU.
There is the long running thing because of Samba4 being coupled to an OpenLDAP directory and a refusal to use sAMAccountID which would work.
Seems like shooting your self in the foot because linking Zentyal to M$ DC's will hit this error. Statistically its going to happen.
I guess its perspective as mine is focused on Samba4 as I don't have an interest in the OpenLDAP on 390.
So when I realise Samba4 is being butchered with something I never choose to be installed then maybe someone can at least understand why I really question this.
Apart from those, guys I am finding 3.4 pretty much close to release which with the date is probably very good news.
Anyone else managed to run up all the features I have with 3.4 and found any further bugs or can just confirm yeah things looking pretty good?
I guess if you want to test the RPC then if it works here
http://www.zentyal.com/for-hosting-providers/get-your-zentyal-for-hosting-providers-demo-for-30-days/Then it will be just a short time for a fix.