similar to: strange gpo behaviour

On Wed, 17 Apr 2019 18:29:19 +0100 Sérgio Basto via samba <samba at lists.samba.org> wrote: > My experience was : > > 1. Mit kbr doesn't support it, we need to use the old kbr system. Do not use MIT, it is, at best, experimental. > 2. We need disable selinux , selinux permissive is not enough to allow > to write on shared folder sysvol. it cause crashes on windows.

On Tue, 2019-04-16 at 15:00 -0700, Ray Klassen via samba wrote: > -- 3 samba 4.10.2 DC's, binaries compiled from tarballs on Debian > stretch > -- 2 DC's are on the same (main office) LAN, one is at another > location > vpn'ed to the main office > > -- randomly windows 10 pc's will not be able to complete a gpupdate > (repeated tries) with no consistency

Who am I to say this? I am only a lowly user and would-be admin, but it seems to me that one of the most useful features of an AD environment, GPOs, is not fully trust-able under Samba because of instability and ensuing fear, before and after each update, related to sysvol and who knows what. I still love you, though.

On Sat, 2019-04-13 at 07:43 -0400, Nico Kadel-Garcia via samba wrote: > On Fri, Apr 12, 2019 at 7:20 AM Andreas Habel via samba > <samba at lists.samba.org> wrote: > > > > Hi, > > > > I managed to compile 4.10.0 under CentOS 7.6. I did the following: > > I'll put muney down that you did not get it working as a full domain > controller.

On 6/3/2015 11:43 AM, Ryan Ashley wrote: > James, I cloned it using git. I installed it to a private partition > (/samba) back when I was first testing Samba4. It is in the path and > this worked for ages, but recently just stopped. No errors, no warnings, > nothing. Just dead. > > The GP in question is the default domain policy. I already tried > unlinking it and it fails on

On 1/11/2018 10:45 AM, Carlos via samba wrote: > Hi > > Any ? > > Regards; > > > On 10-01-2018 15:11, Carlos wrote: >> >> Every 5 minutes. >> >> This moment(before sysvolreset,) machine is ok . This comend is valid >> now ? >> >> *In DC01 Problem does not exist with sysvol. >> >> Regards; >> >> >>

I am having a strange issue at one location which is running samba 4.1. Two or three PC's out of maybe twenty-five are unable to get to the sysvol share. If I run "gpupdate" on the systems it gives error 1058. Digging deeper says the path was not found, but if I click on the path in the event log it pops right up in notepad (gpt.ini). This tells me that the user accounts can access

Really my user IDs are different, but I can not adjust it. Using Samba 4.3.3 (Upgrade from 4.2 -> 4.3 -> 4.3.3), I think it has something it was initially used with Windows 2003 (no longer usaddo) to replicate data Win 2003 -> Samba. Today only own Samba (which had to increase Schema) Em 29-03-2016 10:27, Sketch escreveu: > On Tue, 29 Mar 2016, Carlos A. P. Cunha wrote: >

Every 5 minutes. This moment(before sysvolreset,) machine is ok . This comend is valid now ? *In DC01 Problem does not exist with sysvol. Regards; On 10-01-2018 14:51, lingpanda101 via samba wrote: > On 1/10/2018 11:42 AM, Carlos via samba wrote: >> HI >> >> Rsync >> >> DC1 to DC2 / DC3 >> >> root / usr / bin / rsync -XAaz --delete-after / opt /

HI Rsync DC1 to DC2 / DC3 root / usr / bin / rsync -XAaz --delete-after / opt / samba / var / locks / sysvol root @ DCXX: / opt / samba / var / Run Windows "gpupdate / force", information error permission (show ID GPO, any gpos ...). Yes, the only gpo, with errors. Regards; On 10-01-2018 14:29, lingpanda101 via samba wrote: > On 1/10/2018 8:59 AM, Carlos via samba wrote:

Good morning Chris > -----Oorspronkelijk bericht----- > Van: Sonic [mailto:sonicsmith at gmail.com] > Verzonden: dinsdag 27 oktober 2020 21:07 > Aan: L.P.H. van Belle > CC: samba at lists.samba.org > Onderwerp: Re: [Samba] GPO fail and sysvol perm errors > > On Tue, Oct 27, 2020 at 4:01 AM L.P.H. van Belle via samba > <samba at lists.samba.org> wrote: > >

Hi! I have 3 Samba 4 , version 4.7.3 running in Ubuntu Server 16.04. All is ok, but GPO in DC3, with erro the permission, with dont load in windows(gpresult /force). My smb.conf all samba server DC. [global]         netbios name = SAMBA-DC103         realm = <DOMAIN>         server role = active directory domain controller         server services = s3fs, rpc, nbt, wrepl, ldap,

The principle was not made any changes to occur this problem. We infra have dc3 and dc4 ADDC. root at dc3:/etc/samba# samba -V Version 4.7.7-Debian (van-blle apt) Result of gpupdate /force in a joined computer client: C:\>gpupdate /force > Updating Policy... > User policy could not be updated successfully. The following errors were > encountered: > The processing of Group Policy

Sorry for the delay, I have been out of town. Your hunch was correct, Rowland. Both getent and id only return local machine accounts, not domain accounts. What have I overlooked which would cause this? I do have winbind in my PAM configuration. James, it has worked for a few years. It recently (in the last year) started having workstations report being unable to access the gpt.ini files. The

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

Dear All, I've recently upgrade from samba 4.1.x to samba 4.2.14 and found that GPO are having issue Specifically when I'm adding new using they *never *got the gpupdate success fully. When I run samba-tool ntacl sysvolcheck or samba-tool ntacl sysvolreset But don't seem to got it fix.. Any suggestion? Thank in advance. #samba-tool ntacl sysvolcheck Processing section

When I do an gpupdate /force a wrong url is used. \\foo\SysVol\foo\Policies\{89E....}\gpt.ini ON my dc the path (in explorer) is \\dc1\sysol\foo\Policies\{89E....}\gpt.ini or \\dc1.foo\sysol\foo\Policies\{89E....}\gpt.ini whats wrong?

Hello Sébastien Le Ray, The PC reply the following... The processing of Group Policy failed. Windows could not resolve the user name. This could be caused by one or more of the following: a) Name Resolution failure on the current domain controller. b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller). The

Hello, i configured group policy via RSAT in my samba 4.1.13 implementation the policy applies correctly to my windows 7 clients but not to my windows XP clients. when i run gpupdate /force in windows XP it replies that the policies are apply correctly .... when i run ./samba-tool ntacl sysvolcheck ERROR(<class 'samba.provision.ProvisioningError'>): uncaught exception -

Hi All, I create a Samba domain and works it's great, the issue that I have is with the GPO's.When applying GPO's then only the computer Policy is applied and not the user GPO. I keep on receiving below error. Has anybody else perhaps been experiencing the same issues? C:\>gpupdate /force Updating Policy... User policy could not be updated successfully. The following errors were