search for: asalluhi

Havany Hi, Did you try 133 mask instead of 0133 ? We use to disable acl for this kind of share and do something like that : [share] path = /a/share/path create mask = 133 directory mask = 022 valid users = @agroup write list = @sagroup force group = @agroup nt acl support = No Regards, Arnaud Cruzel Le 25/10/2024 ? 12:25, Gilles via samba a ?crit?: > Hello, > > On a Linux

Hello, Le 06/06/2024 ? 15:40, Rowland Penny via samba a ?crit?: > On Thu, 6 Jun 2024 13:33:04 +0200 > Havany via samba <samba at lists.samba.org> wrote: > > >> - Classisupgrade is destructive for the NT4 Domain, but we can keep >> data of the old NT4 Domain and we can rollback to this with ours >> Ansible playbooks. We will loose all change between migration

Hi Darin, Le 05/06/2024 ? 17:34, Darin via samba a ?crit?: > > > Hello Havany, > I am just going to jump into this discussion. > Welcome! >> We try 2 scenarios : - A "Big bang" migration to an new domain made from scratch : but we need to migrate all users, computers, laptops, filers without loosing profiles, files server access... In a short time (1-2 weeks

Hi samba list, I work on an classicupgrade of our NT4/ldap domain. On my tests (DC and filer are on FreeBSD and zfs file system, client is a Windows 10 22H2): -> I'm able to do this classicupgrade and keep all users able to connect on computers with their domain account. -> In a second step I configure samba DC to improve security and by the way I upgrade our FL to 2012_R2, schema