Displaying 20 results from an estimated 2000 matches similar to: "[Announce] Samba 4.19.5 Available for Download"
2024 Jan 31
0
[Announce] Samba 4.18.10 Available for Download
Release Announcements
---------------------
This is the latest stable release of the Samba 4.18 release series.
Changes since 4.18.9
--------------------
o? Ralph Boehme <slow at samba.org>
?? * BUG 13688: Windows 2016 fails to restore previous version of a
file from a
???? shadow_copy2 snapshot.
?? * BUG 15549: Symlinks on AIX are broken in 4.19 (and a few version
before
????
2024 Jan 31
0
[Announce] Samba 4.18.10 Available for Download
Release Announcements
---------------------
This is the latest stable release of the Samba 4.18 release series.
Changes since 4.18.9
--------------------
o? Ralph Boehme <slow at samba.org>
?? * BUG 13688: Windows 2016 fails to restore previous version of a
file from a
???? shadow_copy2 snapshot.
?? * BUG 15549: Symlinks on AIX are broken in 4.19 (and a few version
before
????
2023 Apr 18
2
gpo client linux sssd does not apply
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
2023 Apr 17
1
gpo client linux sssd does not apply
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
2023 Apr 18
1
gpo client linux sssd does not apply
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
2023 Apr 18
1
gpo client linux sssd does not apply
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
2023 Apr 14
1
gpo client linux sssd does not apply
On 14/04/2023 15:51, Anderson Sampaio Mello via samba wrote:
> Thanks everyone for the reply.
>
> But actually the samba documentation:
>
> https://wiki.samba.org/index.php/Group_Policy#SSSD
>
> and from David Mulder(dmulder):
>
> https://dmulder.github.io/group-policy-book/policy-refresh.html#sssd-refresh
>
> It makes it clear that sssd does support samba AD
2023 Apr 14
4
gpo client linux sssd does not apply
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
2023 Aug 11
1
GPO not getting updated on Windows 10
On 8/10/23 8:48 PM, Anantha Raghava H A via samba wrote:
> Hi,
>
> Our Domain controller environment is working for over 6 years without
> a break. It started with Samba Version 4.6.5 and today running 4.18.5.
> We have only Windows 10 clients across our organisation.
>
> Off late, we have observed that GPOs are not getting updated when we
> change some GPOs and link
2023 Apr 18
1
gpo client linux sssd does not apply
On 18/04/2023 18:15, David Mulder via samba wrote:
> I was able to get it to work by setting up a simple smb.conf, and doing
> a `net ads join`. SSSD is still the auth provider.
>
> My simple smb.conf looks like this:
>
> dmulder at dmm-tw:~> cat /etc/samba/smb.conf
> [global]
> ?? ?idmap config * : backend = tdb
> ?? ?idmap config * : range = 10000-20000
>
2024 Mar 27
0
[Announce] Samba 4.20.0 Available for Download
Release Announcements
---------------------
This is the first stable release of the Samba 4.20 release series.
Please read the release notes carefully before upgrading.
NEW FEATURES/CHANGES
====================
New Minimum MIT Krb5 version for Samba AD Domain Controller
-----------------------------------------------------------
Samba now requires MIT 1.21 when built against a system MIT Krb5
2024 Mar 27
0
[Announce] Samba 4.20.0 Available for Download
Release Announcements
---------------------
This is the first stable release of the Samba 4.20 release series.
Please read the release notes carefully before upgrading.
NEW FEATURES/CHANGES
====================
New Minimum MIT Krb5 version for Samba AD Domain Controller
-----------------------------------------------------------
Samba now requires MIT 1.21 when built against a system MIT Krb5
2014 May 16
1
Login by AMI ok, by AJAM fails
I have setup an Ast 11.6 host and I want to login via AJAM. I setup manager.conf, http.conf described in the docs. When I login via the AMI it works fine (see below), but when I login via AJAM the same credentials fail (see further down)
Can someone tell me how to fix this?
-----------
Connection closed by foreign host.
root at pbx:/tmp# telnet localhost 5038
Trying 127.0.0.1...
Connected to
2024 Jun 14
1
winbind error after startup on Samba member server
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:
2024 Jun 13
1
winbind error after startup on Samba member server
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
2024 Jun 13
1
winbind error after startup on Samba member server
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
2024 Jun 13
1
winbind error after startup on Samba member server
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
>>
2024 Apr 08
0
[Announce] Samba 4.19.6 Available for Download
Release Announcements
---------------------
This is the latest stable release of the Samba 4.19 release series.
Changes since 4.19.5
--------------------
o? Ralph Boehme <slow at samba.org>
?? * BUG 15527: fd_handle_destructor() panics within an
smbd_smb2_close() if
???? vfs_stat_fsp() fails in fd_close().
o? Guenther Deschner <gd at samba.org>
?? * BUG 15588: samba-gpupdate:
2024 Apr 08
0
[Announce] Samba 4.19.6 Available for Download
Release Announcements
---------------------
This is the latest stable release of the Samba 4.19 release series.
Changes since 4.19.5
--------------------
o? Ralph Boehme <slow at samba.org>
?? * BUG 15527: fd_handle_destructor() panics within an
smbd_smb2_close() if
???? vfs_stat_fsp() fails in fd_close().
o? Guenther Deschner <gd at samba.org>
?? * BUG 15588: samba-gpupdate:
2018 Nov 06
0
GPUpdate
> 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.