similar to: Wiki should have Readme First

Missing features from memory from following this mailinglist: - Win7 join to AD still requires two registry changes. - SYSVOL is not replicated, use a cronjob with rsync. - Domain-Trust works only in one direction (which one?). - winbind does not work on DCs, use a separate file server. - Joining an AD requires one of its DCs in the same subnet? - Cluster filesystems destroy TDB files, use CTDB. -

On 11/28/2014 9:23 AM, Klaus Hartnegg wrote: > > Is there anything else that I could try, > or do I just have to stay on protocol NT1 > as long as we still use this old software? > > Klaus Try in [global] acl allow execute always=true -- Regards -------------------------------------- Gerald Drouillard Technology Architect Drouillard & Associates, Inc.

Hello, what do you think about replacing the user documentation page (https://wiki.samba.org/index.php/Samba) with https://wiki.samba.org/index.php/HowTo_Guide? The HowTo Guide is a table of content, we worked out in a past documentation team meeting. Everything from the current user documentation page is already link there and even more. I know that currently there are many red (not

On Wed, May 13, 2015 at 1:20 PM, Klaus Hartnegg <hartnegg at uni-freiburg.de> wrote: > Am 13.05.2015 um 17:30 schrieb S?bastien Le Ray: > >> No they aren't >>> >> >> Yes they are >> > > Not sure about this, but mostly irrelevant anyway, because of this effect > in the other direction: > > If you have set Windows ACLs, and then change

Am 26.04.2018 um 20:07 schrieb Harry Jede via samba: > No, i have created 2 users with same sid. > > root at capella:~# pdbedit -Lv | grep "User SID" | sort|uniq -d > root at capella:~# > > root at capella:~# pdbedit -L|grep Failing > ldapsam_getsampwsid: More than one user with SID [S-1-5-21-3958726613-3318811842-4132420312-21010]. Failing. count=2 >

On Fri, 24 Apr 2015, Klaus Hartnegg wrote: > Am 24.04.2015 um 01:02 schrieb Carl G. Riches: >> I'm unable to join a Windows 7 PC >> to the Samba 4 domain when "hosts allow" is defined > >> hosts allow = 127 10.208.29. 10.108.29. > > Maybe the new version insists there must be a dot after the 127. > I put the dot in, to no avail. I also modified the

Hi, Is it normal that "chown $user $file" and "chown :$group $file" destroy the Windows-ACLs? Is it normal that changing the file owner in Windows does not change the file owner in Linux, but changing the file owner in Linux does change the file owner in Windows? This should be mentioned in >

Thanks for your help and replies. Yes, I meant "store dos attributes". It's pretty clear now that I need to keep the parameter 'store dos attributes=no' since 1) the server is an AD member server and 2) the map* parameters don't do the right thing under ZFS / NFSV4 ACLs. I've read that the steps Klaus Hartnegg listed resolves the issue on ZFS on Linux; however, I

Am 10.06.2015 um 03:25 schrieb Mike: > I'm learning to be very deliberate with changing posix and windows acl's so > I don't disturb users' access to files and folders. > I check acl's on a specific file/folder on the server with getfacl. > Then make one small acl modification to one file in a sub-directory of a > share. > Then record the difference reported

Am 29.09.2016 um 16:26 schrieb v g via samba: > Really? Easy and useful, huh? Live sync of directories is VERY useful. So useful that I just try to kill the purchase of EMC Isilon, precisely because it cannot replicate with Windows.

Am 10.04.2018 um 18:46 schrieb Rowland Penny via samba: > Thanks for the updates, I just wish more people would report errors & > typo's I can send some more, this time from classicupgrade. Again I do not want to do these changes myself, a samba expert should have a look. Feedback for wiki page Migrating_a_Samba_NT4_Domain_to_Samba_AD_(Classic_Upgrade) Tried on Devuan 1 with

Hi, Following the wiki page Setting_up_a_Share_Using_Windows_ACLs windows shows me this error after clicking on Shares: Disk Management could not start the Virtual Disk Service (VDS) on 'COMPUTER'. This can happen if the remote computer does not support VDS, or if a connection cannot be established because it was blocked by Windows Firewall. Tested on a new provisioned AD-DC server.

Hi Klaus, I haven't used that tool for at least 13 years but I do recall that, among other things, it read from the registry. Coupled with the fact that Samba 4 AD is not a complete implementation of AD I can't imagine that it could possibly work. More to the point, I'd be seriously concerned about the results. This is not something I'm prepared to test in a production

Hi, when I don't want to switch to Active Directory, but don't want to be stuck on version 3.6 either, can I simply give samba 4 a copy of the old smb.conf file? Will it be able to store all windows acl's in extended attributes, or is this improvement only available in combination with letting it run as active directory domain controller? thanks, Klaus

Hi, Just wondering: What are you guys using to deploy software on your windows (7) workstations within the samba4 AD? These are options I know of: * wpkg (but it seems it's development is not too active) * wpkg-gp using the group policies * www.opsi.org (Client Management System for Windows clients) * standard windows software deployment, but I think that's msi-only This page also has

On Tue, 2015-03-10 at 11:37 +0100, Klaus Hartnegg wrote: > Am 10.03.2015 um 11:00 schrieb Sergio Rizzi: > > By reading https://wiki.samba.org/index.php/Roadmap#Trust_support seems > > that trust support is not finished yet, btw in changelogs seems that in > > 4.2.* (with winbindd) interdomain trusts are now working. > > The release notes say that windindd "paves

Hi, maybe this thread should ask an even more general question: How are AD-DC admins supposed to test upgrades? If there is more than one AD-DC, an upgraded DC which causes problems cannot (must not) be restored from backup. This is one of the reasons why I do not want to switch to AD. A PDC *can* simply be restored from backup. It is even enough to switch back to the previous contents of

Am 15.05.2015 um 16:30 schrieb Reindl Harald: > the real problem in that thread is that the ordinary chmod/chown > permissions are called repeatly "acls" which is not wrong by the > definiton of "access control list" but mixing that with "windows ACLs" > and "posix ACLs" where on the FS layer we just have ACLs set with > "setfacl" it

Am 06.06.2018 um 12:41 schrieb Rowland Penny via samba: > I think that 'standalone' machines will continue Thank you very much for clarification. This means that SMB1 and PDC are the problems, not lack of AD. But if we later need to switch to AD, is there a method like classicupgrade to do it? Currently classicupgrade of a standalone server Samba 3 creates a standalone server Samba

Upgrading Win7-32 (connected to Samba as NT-PDC) to Win10 requires - disable HardenedUncPaths (MutualAuth & Integrity) - install NTVDM - enable LegacyConsole otherwise the logon-script in Netlogon does not run, even if samba.cnf contains "server max level = NT1" Is Samba as NT-PDC supposed to handle HardenedUncPaths? Did I miss that I should have enabled that somehow in smb.conf?