On 25/07/2023 20:09, Mark Foley via samba wrote:> One of the recommended solutions was using rsync, similar to what I theorized. > I'll try that and post back. > > Seeing as this is a critial aspect of setting up a 2nd DC, I think something on > this howto should be in https://wiki.samba.org/index.php/Joining_a_Samba_DC_to_an_Existing_Active_Directory#Introduction. > Currently, there is just one line, "You will now need to sync Sysvol to the new DC", > but no actual instructions, nor any link to a howto. > > Thanks --Mark >There is, but it is above the part you reference, it looks like the page needs some changes. Rowland
On Tue Jul 25 15:34:15 2023 Rowland Penny via samba <samba at lists.samba.org> wrote:> On 25/07/2023 20:09, Mark Foley via samba wrote: > > > One of the recommended solutions was using rsync, similar to what I theorized. > > I'll try that and post back. > > > > Seeing as this is a critial aspect of setting up a 2nd DC, I think something on > > this howto should be in https://wiki.samba.org/index.php/Joining_a_Samba_DC_to_an_Existing_Active_Directory#Introduction. > > Currently, there is just one line, "You will now need to sync Sysvol to the new DC", > > but no actual instructions, nor any link to a howto. > > > > Thanks --Mark > > > > There is, but it is above the part you reference, it looks like the page > needs some changes. > > RowlandAh, I scrolled up and now I see it. I guess it didn't strike me as a needful requirement to actually do one of those requirements. Since "same ID mappings" are required for for sysvol replication, I did that step first, but didn't think to go back to the previous page. Thanks --Mark
On Tue Jul 25 15:34:15 2023 Rowland Penny <rpenny at samba.org> wrote:> On 25/07/2023 20:09, Mark Foley via samba wrote: > > > One of the recommended solutions was using rsync, similar to what I theorized. > > I'll try that and post back.[deleted] OK, I did the rsync method for SysVol replication. It appears to have worked and copied the ACLs as well. I then ran the sysvolreset. It tool longer, but still gave some errors, though not as many: # samba-tool ntacl sysvolreset set_nt_acl_conn: init_files_struct failed: NT_STATUS_OBJECT_NAME_NOT_FOUND ERROR(runtime): uncaught exception - (3221225524, 'The object name is not found.') File "/usr/lib64/python3.9/site-packages/samba/netcmd/__init__.py", line 186, in _run return self.run(*args, **kwargs) File "/usr/lib64/python3.9/site-packages/samba/netcmd/ntacl.py", line 412, in run provision.setsysvolacl(samdb, netlogon, sysvol, File "/usr/lib64/python3.9/site-packages/samba/provision/__init__.py", line 1754, in setsysvolacl set_gpos_acl(sysvol, dnsdomain, domainsid, domaindn, samdb, lp, use_ntvfs, passdb=s4_passdb) File "/usr/lib64/python3.9/site-packages/samba/provision/__init__.py", line 1630, in set_gpos_acl setntacl(lp, root_policy_path, POLICIES_ACL, str(domainsid), session_info, File "/usr/lib64/python3.9/site-packages/samba/ntacls.py", line 228, in setntacl smbd.set_nt_acl( Is this ignorable? Fixable? It doesn't mean much to me. Note that samba is not yet running, nor is the DNS working yet. Thanks --Mark