search for: gpupdated

On 4/18/23 4:44 AM, Rowland Penny via samba wrote: > I think what you are saying is this, using oddjob-gpupdate replaces > the 'apply group policies = yes' line in smb.conf > > Anderson compiled oddjob-gpupdate and it didn't work using sssd, but > the same basic setup on the OS using winbind did. > > As far as I can see, oddjob-gpupdate or 'apply group

On 17/04/2023 15:47, David Mulder via samba wrote: > On 4/14/23 2:23 AM, Anderson Sampaio Mello via samba wrote: >> Hello Samba Team, how are you? >> >> I'm joining linux clients in the company's environment and I would >> like to >> apply GPOs to linux clients, I'm in the testing phase. >> >> I'm testing with ubuntu clients version

Hi folks, The last log record from journalctl -xeu winbind directly after winbind startup is: Jun 13 12:41:36 datasrv winbindd[582]: gpupdate_cmd_done: gpupdate failed with exit status 1 For completeness, the log entries for winbind startup is displayed below. Things seem to work though, but I have never seen it before (I don't like error messages). When I noticed the message I

On Thu, 13 Jun 2024 16:26:17 +0200 Peter Milesson via samba <samba at lists.samba.org> wrote: > Hi folks, > > The last log record from journalctl -xeu winbind directly after > winbind startup is: > > Jun 13 12:41:36 datasrv winbindd[582]: gpupdate_cmd_done: gpupdate > failed with exit status 1 > > For completeness, the log entries for winbind startup is

On 13.06.2024 17:21, Rowland Penny via samba wrote: > On Thu, 13 Jun 2024 16:26:17 +0200 > Peter Milesson via samba <samba at lists.samba.org> wrote: > >> Hi folks, >> >> The last log record from journalctl -xeu winbind directly after >> winbind startup is: >> >> Jun 13 12:41:36 datasrv winbindd[582]: gpupdate_cmd_done: gpupdate >>

On 4/14/23 2:23 AM, Anderson Sampaio Mello via samba wrote: > Hello Samba Team, how are you? > > I'm joining linux clients in the company's environment and I would like to > apply GPOs to linux clients, I'm in the testing phase. > > I'm testing with ubuntu clients version 22.04 and the software I used to > join the samba AD was sssd. > > The 22.04 ubuntu

Hello Samba Team, how are you? I'm joining linux clients in the company's environment and I would like to apply GPOs to linux clients, I'm in the testing phase. I'm testing with ubuntu clients version 22.04 and the software I used to join the samba AD was sssd. The 22.04 ubuntu client has joined and everything is working fine except for the GPOs for linux clients. I compiled

Hi! I have a problem with gpupdate having a trust with a M$ -ADS domain. Before creating the trust gpupdate worked fine. Then i added the trust and then gpupdate gives the following error: Updating policy... Computer Policy update has completed successfully. User Policy could not be updated successfully. The following errors were encount ered: The processing of Group Policy failed. Windows

On 4/14/23 2:23 AM, Anderson Sampaio Mello via samba wrote: > Hello Samba Team, how are you? > > I'm joining linux clients in the company's environment and I would like to > apply GPOs to linux clients, I'm in the testing phase. > > I'm testing with ubuntu clients version 22.04 and the software I used to > join the samba AD was sssd. > > The 22.04 ubuntu

brief: gpupdate when run during login, fails with unable to get SID token. The same command run interactively runs with no issues. The SID is for the user (Peter) and the user can login over ssh. I can repost all the logs and configs here if needed. samba built from git master branch using bootstrap configure flags. tested both with built in heimdal and mit krb. after a bunch of testing with

On 13.06.2024 20:33, Peter Milesson via samba wrote: > > > On 13.06.2024 17:21, Rowland Penny via samba wrote: >> On Thu, 13 Jun 2024 16:26:17 +0200 >> Peter Milesson via samba <samba at lists.samba.org> wrote: >> >>> Hi folks, >>> >>> The last log record from journalctl -xeu winbind directly after >>> winbind startup is:

hello list, I noticed that when I run the command gpupdate in the clients I get the following error C:>gpupdate Updating policy... Computer policy could not be updated successfully. The following errors were enc ountered: The processing of Group Policy failed. Windows attempted to read the file \eccm g.cupet.cusysvoldomainPolicies{31B2F340-016D-11D2-945F-00C04FB984F9} gpt.ini from a domain

> read the file \eccm > g.cupet.cusysvoldomainPolicies{31B2F340-016D-11D2-945F-00C04FB984F9} > gpt.ini from a domain controller and was not successful. That is just an incorrect configured sysvol share. The computer computer$ impersonates itself through user SYSTEM. And that one does not have rights to gpt.ini. Same for you... I suggest, start reading here, it explains all.

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; >> >> >>

Post you ipconfig /all output of the pc. You primary dns suffix or connection suffix is wrong, at least thats my first guess. Greetz, Louis > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens basti via samba > Verzonden: dinsdag 7 februari 2017 12:25 > Aan: samba at lists.samba.org > Onderwerp: Re: [Samba] gpupdate use wrong url

Ok, try this. Gif the pc a uid and check again. If it works then, its a share or security right. Gpupdate /force works because at that point you "user"/user has a uid and gid. The error occurs at start up because the COMPUTERNAME$ doent have access to that gpt.ini. Resetting sysvol in that case doent help because the right on the gpt.ini is set by the group you assigned to the

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?

Hi, I am using samba 4.1.7 as Domain Controller. Actually I have two samba servers DC1 and DC2. DC1 is the primary DC and DC2 joined as another DC. We use the Active Directory for a couple of weeks. The directory replication works fine, and a sysvol replication works with rsync. (I set it up based on the samba wiki). But I have a problem with the authentication. If I log in to a windows

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: >

Check rights on sysvol (using samba-tool), check rsync process if several DC. 2016-03-29 13:07 GMT+02:00 barış tombul <bbtombul at gmail.com>: > command prompt >> run as administrator > > Microsoft Windows [Version 6.1.7601] > Copyright (c) 2009 Microsoft Corporation. All rights reserved. > > C:\Users\btombul>gpupdate /force > Updating Policy... > >