search for: garthk

I have an (apparently) valid Samba4 DC to which I have transferred all FSMO roles in preparation for running dcpromo and demoting the Win DC. All of the logs look good on the Samba DC and showrepl indicates no errors. Unfortunately, the Win DC does not seem to detect the Samba DC when I attempt to run dcpromo and it throws a nasty warning about AD data being lost. If I run Sites and Services,

I've posted before about this but I'll add more info. I've set up two Samba DCs in a domain, using both 4.0.7 and 4.1RC1, and all works great including Forest and Domain DNS repl in both directions. When I add a Samba 4.0.7 or 4.1RC1 DC to an existing Win2003 PDC with Forest level of 2003, Forest and Domain DNS repl is only from PDC to DC, never in the other direction. I've

All, I've posted a few times about this but without response so it seems that not many folks are trying to do this. So, before I spend many more hours on this trying to make it work, a simple yes or no question: Has anyone successfully demoted a Win 2003 PDC without error after joining a Samba 4.x DC to it? That's it. I'm primarily interested in "yes" responses but

When I DCPROMO a Win2003 server into an existing Samba4.1RC1 domain with two Samba DCs, all appears to be working correctly from the Samba side but the WinDC never starts sharing SysVol as it should. "Sites and Services" shows all DCs as expected and forcing repl with the Samba PDC works correctly while doing that with the second Samba DC shows the following: "The following

Greetings, The ultimate goal is a full implementation of Samba4/OpenChange/SOGo but that onion has too many layers to shoot for the whole thing at once. So, I've added a Samba/Ubuntu12.04 DC to the AD and want to get it totally correct before proceeding with OC. I have two questions (at the moment): First, PAM is not included on the Samba DC and I need to know if it is a requirement. The