Every time I use RSAT's GPO editor Samba DCs fail sysvolcheck, and require a sysvolreset. This happens on two different DC's (domains). Also on one of the DCs if I attempt the sysvolreset while samba is running I get a continuous: ... idmap range not specified for domain '*' idmap range not specified for domain '*' idmap range not specified for domain '*' idmap range not specified for domain '*' idmap range not specified for domain '*' idmap range not specified for domain '*' idmap range not specified for domain '*' idmap range not specified for domain '*' ... I therefore need to stop samba in order to do the sysvolreset. Are these known issues? Is there a fix? Thank you, Chris
On Sat, 29 Jun 2024 10:50:47 -0400 Sonic via samba <samba at lists.samba.org> wrote:> Every time I use RSAT's GPO editor Samba DCs fail sysvolcheck, and > require a sysvolreset. This happens on two different DC's (domains).How are you running the domains ? have you added any rfc2307 attributes ?> > Also on one of the DCs if I attempt the sysvolreset while samba is > running I get a continuous: > ... > idmap range not specified for domain '*' > idmap range not specified for domain '*' > idmap range not specified for domain '*' > idmap range not specified for domain '*' > idmap range not specified for domain '*' > idmap range not specified for domain '*' > idmap range not specified for domain '*' > idmap range not specified for domain '*' > ... > > I therefore need to stop samba in order to do the sysvolreset.How are you running the sysvolreset command ? I do not get any output from samba-tool when I run it. Rowland