similar to: sysvolcheck on fresh samba 4.7 DCs

Displaying 20 results from an estimated 10000 matches similar to: "sysvolcheck on fresh samba 4.7 DCs"

2017 May 31
2
Erro sysvolcheck/sysvolreset
Hi My configuration: smb.conf # Global parameters [global] workgroup = MYSERVER realm = interno.mydomain.com.br netbios name = DC-LINUX server role = active directory domain controller server services = s3fs, rpc, nbt, wrepl, ldap, cldap, kdc, drepl, winbindd, ntp_signd, kcc, dnsupdate idmap_ldb:use rfc2307 = yes ldap server
2013 Mar 19
1
samba-tool classicupgrade (from v3 to v4) aborts with "Unable to get id for sid"
I'm trying to upgrade from samba3 -> 4. I ran this command: WORKDIR=/usr/local/mobius /usr/local/samba/bin/samba-tool domain classicupgrade --dbdir=$WORKDIR/var --use-xattrs=yes --realm=infinityhealthcare.com $WORKDIR/smb.conf but it failed with the error given in this email's subject. What does it mean, and how do I fix it? This is just another is a growing line of errors that
2013 Apr 05
2
ClassicUpgrade => EpicFail
ClassicUpgrade of my samba3 data to samba4 fails, with this error: ERROR(<class 'passdb.error'>): uncaught exception - Unable to get id for sid Full log of the classicupgrade is at the end of this email. Project member on this list, Andrew Barlett, wrote that the issue is probably that my Samba 3 passdb was passable in an NT 4 DC mode, but is actually 'invalid' :
2015 Aug 11
4
Error
Hello list, today I update de the version of samba, 4.2.3, when I run this tool, I have this error. 1) - ./samba-tool gpo aclcheck ldb_wrap open of secrets.ldb GENSEC backend 'gssapi_spnego' registered GENSEC backend 'gssapi_krb5' registered GENSEC backend 'gssapi_krb5_sasl' registered GENSEC backend 'spnego' registered GENSEC backend 'schannel' registered
2017 Jun 16
2
Erro sysvolcheck/sysvolreset
Hello! Any idea ? Regards Em 07-06-2017 09:30, Carlos A. P. Cunha escreveu: > > Hello! > > Any idea ? > > > Regards > > > > Em 31-05-2017 12:00, Carlos A. P. Cunha escreveu: >> >> Hi >> >> My configuration: >> >> smb.conf >> >> # Global parameters >> [global] >> workgroup = MYSERVER >>
2017 Oct 26
0
sysvolcheck on fresh samba 4.7 DCs
On Thu, 2017-10-26 at 11:38 +0200, mj via samba wrote: > Hi, > > I joined a new samba-4.7 DC to our AD, replicated everything over, then > turned off the old DCs, seized fsmo roles, and added two extra 4.7 DCs. > > Everything above succeeded without warnings, and everything seems to be > running very well finally, except for the sysvolcheck / sysvolreset. > >
2017 Jun 07
0
Erro sysvolcheck/sysvolreset
Hello! Any idea ? Regards Em 31-05-2017 12:00, Carlos A. P. Cunha escreveu: > > Hi > > My configuration: > > smb.conf > > # Global parameters > [global] > workgroup = MYSERVER > realm = interno.mydomain.com.br > netbios name = DC-LINUX > server role = active directory domain controller > server services = s3fs,
2017 Jun 13
2
GPO Problem
Thanks Elias. But I run samba-tool ntacl sysvolreset and: root at DC02:~# samba-tool ntacl sysvolreset lp_load_ex: refreshing parameters Initialising global parameters Processing section "[global]" Processing section "[netlogon]" Processing section "[sysvol]" Processing section "[sistemas]" ldb_wrap open of idmap.ldb lp_load_ex: refreshing parameters
2017 Jun 06
2
GPO Problem
2017-06-06 15:54 GMT-03:00 Rowland Penny via samba <samba at lists.samba.org>: > On Tue, 6 Jun 2017 15:35:42 -0300 > Epsilon Minus via samba <samba at lists.samba.org> wrote: > >> Hi. I have a problem applying GPO. I do not know where to look >> Reviewing I found this: >> >> # samba-tool ntacl sysvolcheck >> lp_load_ex: refreshing parameters
2020 Feb 26
0
sysvolcheck and aclcheck generates error
Hi, Search on the net but not getting enough information to resolve the issue. As per suggestion to check the sysvol but mine got issues. Currently using CentOS 8.1.1911 and a compiled samba 4.11.4 based on Fedora 31. I tried also to delete the broken GPO policy E4108E65-68AB-4E2D-9A00-A9063B1558E3 but I can't delete it (using samba-tool gpo del {31B2F340-016D-11D2-945F-00C04FB984F9}
2017 Jun 06
2
GPO Problem
Hi. I have a problem applying GPO. I do not know where to look Reviewing I found this: # samba-tool ntacl sysvolcheck lp_load_ex: refreshing parameters Initialising global parameters Processing section "[global]" Processing section "[netlogon]" Processing section "[sysvol]" Processing section "[sistemas]" ldb_wrap open of idmap.ldb Module
2015 Jul 28
2
GPO
Hola Sandy, (mail rethreaded, please don't hijack threads) > Samba4 recently updated to version 4.2.2, but I have noticed that > since a policy which is to put a wallpaper on each machine is not > being implemented in windows 7 after upgrade ... somebody can helpme. Could you check the ACLs on the Sysvol share? samba-tool ntacl sysvolcheck samba-tool ntacl sysvolreset Cheers,
2015 Aug 11
0
Error
most people sadly don't own a crystal ball * what operating system * what was the previous version * self compiled or packages * how does your overall setup look like Am 11.08.2015 um 19:42 schrieb sandy.napoles at eccmg.cupet.cu: > Hello list, today I update de the version of samba, 4.2.3, when I run this tool, I have this error. > > 1) - ./samba-tool gpo aclcheck > ldb_wrap
2023 May 11
1
Usage of '--domain-guid' parameter of 'samba-tool domain provision'
Hello, I was hoping to reprovision the same domain by specifying the domain GUID in the command line tool 'samba-tool domain provision' but I am not sure if I missed something or if there is a bug but the specified domain GUID is not the one which is created for my domain. Specifying the domain SID seems to work as I would expect. I tested it with Samba shipped by Debian 11 (samba2
2017 Apr 28
2
Problem with Samba 4.6
Did the first test on two different servers both are running debian wheezy and packported samba packages. On the server still running 4.6.2 it worked without problems to add the first available printer driver (Brother-DCP116C). On the other server already running 4.6.3 it faile with the error you and marc described. So I downgraded this server to 4.6.2 but i still get the error. Am
2019 Apr 11
1
Online backup results using 4.10.2
Hello,     I would like to share some info on how I was able to successfully run an online backup after several failed attempts. I would constantly get the following error when attempting to run an online backup. ERROR(runtime): uncaught exception - (3221225506, '{Access Denied} A process has requested access to an object but has not been granted those access rights.') Looking
2015 May 26
2
Problems with joining a second DC to AD
> Gesendet: Dienstag, 26. Mai 2015 um 13:31 Uhr > Von: "Rowland Penny" <rowlandpenny at googlemail.com> > An: "Stephan Mattecka" <ste-fun_s at gmx.de> > Cc: samba at lists.samba.org > Betreff: Re: Aw: Re: [Samba] [SAMBA] Problems with joining a second DC to AD > > On 26/05/15 10:42, Stephan Mattecka wrote: > > Gesendet: Donnerstag, 21. Mai
2013 Mar 07
1
Samba 4 classicupgrade: Error converting string to value for line:"CurrentVersion"
Hello, I've seen this upgrade error posted before: https://lists.samba.org/archive/samba/2013-January/171022.html but either there is a different issue or I'm misreading the post. Basically when I run the classicupgrade (samba3 to 4) on a test machine, I get the following (the full debug output will be at the end of my post): ....... key added: key=CurrentVersion,key=Windows
2013 Jun 02
2
dynamic DNS Updates still failing, re-installed 9 more times, tried everything I could think of, now bald.
I have tried everything, This is CentOS 6.4 with SELinux DISABLED, Bind version BIND 9.8.2rc1-RedHat-9.8.2-0.17, samba 4.0.6 downloaded as a tar.gz from samba.org -- I have read EVERY maillinglist, IRC Log, how-to on google, tutorial on samba.org, and many many people have had this problem and not once have any of the posters resolved it, so I am now a desperate man reaching out to you with as
2016 Oct 05
4
Failure gpupdate
Colleagues, I come to seek help to solve this problem. I use Samba 4.4.5. I'm getting errors when running gpupdate / force on local desktops. I get the following error: User policy could not be updated successfully. The following errors were encountered: The processing of Group Policy failed. Windows could not apply the registry-based policy settings for the Group Policy object