One thing you forgot to perform before you turned off your Samba 4 DC was to transfer the FSMO roles. Since you've powered off your existing Windows AD DC, the only way to repair it is to seize the RID Master to the samba 4 DC as the Samba 4 DC can't seem to figure out where the appropriate RIDs are.
If you can't... well, sorry but you really hosed the domain entirely. On Wed, Jan 9, 2013 at 8:44 PM, chidokato <[email protected]> wrote: >> Here is my implementation: >> Samba 4 with bind <----------------replicate-------------------- old >> windows AD >> >> After replication, I want to demote Windows AD (WAD) and turn it off. So >> I'll use Samba 4 as only active directory domain controller. >> Everything is fine until I join new client to my domain (samba 4 is now >> only AD, already update DNS). It pop-up an error: "Samba security database >> is corrupted", and here is my samba.log: >> >> ../source4/dsdb/repl/drepl_ridalloc.c:207: Failed to find fSMORoleOwner in >> RID Manager object - Cannot find attribute fSMORoleOwner of CN=RID >> Manager$,CN=System,DC=tuan,DC=local to calculate reference dn >> >> So, it's too much for me to handle this kind of error. Any idea? >> >> Thanks you all. >> -- >> Jade Nguyen - System Specialist >> Network Operation Center, FPT Online Service JSC >> > -- > To unsubscribe from this list go to the following URL and read the > instructions: https://lists.samba.org/mailman/options/samba -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
