[Samba] Sysvol reset

[Anders Östling]

Hi Rowland
Thanks for testing this (non) error message. I have upgraded to 4.23.5, and
the situation is unchanged. Running a sysvolreset (without having
identified any errors with sysvolcheck) results in these messages.
I suppose it does not affect anything,  so I changed my script to only run
the reset in case the check signalled errors.
Thanks again for your help
/Anders

On Tue, Jan 27, 2026 at 5:04 PM Rowland Penny via samba <
samba at lists.samba.org> wrote:

> On Tue, 27 Jan 2026 09:06:33 -0500
> Sonic via samba <samba at lists.samba.org> wrote:
>
> > On Mon, Jan 26, 2026 at 3:46 PM Anders Östling via samba
> > <samba at lists.samba.org> wrote:
> > >
> > > I have a script that regularly (every hour) runs a sysvolreset on
> > > the DC that holds the PDC emulator (actually all) roles. This has
> > > used to work fine, but now it spits out (approx 50 lines)
> > > 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 have two domains that were migrated from NT4 PDC,s and one of them
> > has this same issue.
> > It seems to run fine and testparm reports no errors. Yet sysvolreset
> > reports those warnings whether or not sysvolcheck shows any issues.
> > Any edits to a GPO via RSAT will make sysvolcheck fail and sysvolreset
> > needs to be run.
> > I suspect it displays a warning for each user if not more, as those
> > messages print for quite a while.
> >
>
> To confirm my thoughts as to where the message is coming from, I edit
> my smb.conf file and commented out the default domain lines and then
> ran 'testparm -s' and among the output was:
>
> idmap range not specified for domain '*'
>
> Examining the sysvolreset code, it seems that it needs to get
> parameters and values from the smb.conf file and it looks like it uses
> the testparm code or something based on it (I didn't dig too deep).
> From this, I am now certain that this is one of those Samba errors that
> isn't actually an error, it would be an error on a DC if you had
> specified any domain range in the smb.conf file.
>
> Rowland
>
> --
> To unsubscribe from this list go to the following URL and read the
> instructions:  https://lists.samba.org/mailman/options/samba
>


-- 
------ -------------------- 8 ------------------ ------
IT truism: "A permanent solution is a temporary solution that works so well
that noone want to replace it."

Anders Östling
+46 768 716 165 (Mobil)