similar to: future of non-AD samba?

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

On Wed, 6 Jun 2018 12:24:20 +0200 Klaus Hartnegg via samba <samba at lists.samba.org> wrote: > Hi, > > We plan to upgrade servers, and wonder which configuration is > future-proof. Must we switch to AD, or will a new Standalone Server > also continue to serve Windows 10 clients? > > Several messages suggest that new Windows sometimes cannot access old > Samba.

Am 26.04.2018 um 19:39 schrieb Rowland Penny via samba: > 'workgroup' is another way > of saying 'netbios domain name', so 'workgroup\user' means exactly > the same as 'domain\user' According to "man smb.conf" workgroup is not the same as netbios name. > When you provision a domain, it will set the netbios domain name to the > left hand

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

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

Hi, This is a collection of notes that I took while setting up an AD-DC. I do not want to edit the Wiki pages myself, without first asking experts whether my assumptions are correct. Klaus ---- On page Setting_up_Samba_as_an_Active_Directory_Domain_Controller the section Configuring Winbindd on a Samba AD DC is not necessary, because the same info is also included in the next

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

Many first time users of Samba-4 seem to struggle with the same issues. I suggest the Wiki should have a Readme First similar like this: http://www.klaus-hartnegg.de/gpo/14-03-12-samba4.html It basicly says that Samba 4 can behave either like Samba 3, or as AD-DC, in which case it should do nothing else. Then it lists the main differences, limitations, and requirements. I would love to see a

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.

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

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

Hi, I want to switch from an old samba 3.6 of a Linux distribution, to a new and self compiled samba, which is in different directories (usr/local/samba). Which files do I need to copy from the old place to the new? Which ones are only temporary files, and can be discarded? This is from the output of "smbd -b" old: SBINDIR: /usr/sbin BINDIR: /usr/bin SWATDIR:

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.

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

I cannot connect as guest from Win10 to Samba anymore, since I removed "server max protocol = NT1" net use \\%IP%\testshare /user:"" "" /persistent:no System error 58 has occurred. The specified server cannot perform the requested operation. It works when I supply a userid and password. It works from Win7. It fails only in the combination Win10, SMB3,

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