similar to: win2003 AD migration to SAMBA 4.6 - dnsupdate problem

Hi Tomas, > I want to migrate old 2003 domain to Samba - join SAMBA 4.6(DC2) to win > 2003 domain like DC, move sysvol, FSMO, demote old server(DC1), etc., > etc. - > https://wiki.samba.org/index.php/Joining_a_Samba_DC_to_an_Existing_Active_Directory > > > My problem are DNS Updates, I have kerberos working (added enctypes = > rc4-hmac for compatibility), May I ask you

Good morning people from Argentine. again bothering with a doubt, It is posiblle, audit change password, create-delete-change users? and more? i have a file server with audit and works really really well and now I want more! any ideas? thanks for samba....i love it

Because of other issues using ADUC, I tried to remove a domain member using: > samba-tool group removemembers "Domain Computers" MARKA\$ Removed members from group Domain Computers As shown, it say it "Removed members", but ... > samba-tool group listmembers "Domain Computers" : LABRAT$ : OHPRSSTORAGE$ MARKA$ : COMMON$ : listmembers still shows the computer

Hi Louis, normally you are building these wonderful samba debian packages for us :-) Is there a reason, that you didnt create packages for samba 4.8? Tfh! Oliver

When trying to join a new DC to an existing Samba4 domain, I am getting this WERR_DS_DRA_MISSING_PARENT error. Does any have any suggestions on how to fix it? My original 6 dc's are running the last free Sernet (4.2.14) on CentOS6 and the error occurs if I use Sernet 4.2.14 or 4.7.5-Debian. I finally have time to upgrade and something is broke. Thanks, Steve # samba-tool domain join

hi! Query, I have 3 DCs, in each of the servers should have configured the other two DCs in the resolv.conf? or with only the primary is enough? Maybe that's my problem that does not replicate the dc3 with the dc2 thanks to all!

Hi all, I'm running in circles trying to debug replication failures on samba 4.7.6: dc00 : is a VM on KVM host (attached to a bridge on local LAN) dc01 : is a similarly configured VM on another KVM host. I've forcibly demoted and re-promoted dc01 but I still cannot get automatic replication to work: root at dc00 ~]# samba-tool drs showrepl Krynn\DC00 DSA Options: 0x00000001 DSA

Hi guys. I've got working samba AD server. It is playing nicely with Windows 10 and also successfully authenticating Linux machines with SSSD. On the Windows machines I have our EMC storage smb mounted via group policy. Managing permissions for users and groups there, as you know, happens with right click, security etc.. As you may have already guessed the troubles come when my Linux

Hi list, are there preparations for upgrading a samba 4.8.5 to 4.9.1 via van-belle-repository to change the backend db? Is there some handwork necessary? Regards, Oliver

I have just installed a samba 4.7.4 from source. All right! wbinfo -u  and wbinfo -g return the list of users and groups from the domain But I can not use they in the DC filesystem. For instance: # touch ttt # chgrp 'domain admins' ttt chgrp: invalid group: ‘domain admins’ That should I do to ?

Dear list, I had to change the name of the AD DC on a test setup (only one DC). What changes do I have to apply for samba? This is using bind9_DLZ. Thanks, Christian

Hi Guys, We're trying to add a BDC in Samb4 classic domain setup. The Samba 3 How -To and Samb3 by Example covers this but uses the old slapd.conf option, we are using the slapd.d config. I couldn't find a similar document for Samba4 Can you please advise that the following steps will work? LDAP in the existing PDC is working using the smbldap tools - Setup the LDAP in BDC

For my current small office configuration, the machine serving as a NT4 Style PDC is also the main file server. Works fine. In reading up on creating an updated configuration, I see The Samba Wiki states the following: "The Samba AD DC is able to provide file shares, just like all other installation modes. However, the Samba team does not recommend using a DC as a file server" Does

Hello Folks, We're using Samba as AD servers along with Windows AD Servers (2008R2 FL). We also use SCCM (Current Branch) that is dependent on AD for lab deployments (Windows 10). Currently, SCCM (current branch) supports 2008R2 FL, but for how long??? Samba does not support 2012R2, 2016, 2019 FL. We'd like to remove the Windows Servers from our AD infrastructure, but would also like

Hi Denis. Since we have "tricky" people working on the Linux machines we prefer NFS because it's less hassle to mount and requires no credentials. Basically because of the users we tend to choose the easiest possible way for them to access the needed resources. I guess pam-script module mounting is exactly for this purpose, but I'll to research more since I'm not familiar

Our Domain Controller is running Samba 4.6.2 We have both Windows 7 & 10 on our network. All of the Windows 7 workstations seem to be updating their reverse PTR records just fine, but the Windows 10 workstations seem to always fail. Here are the named logs from the DC: 23-May-2018 13:53:08.965 update-security: error: client 192.168.254.210#60093: update 'tipping.lan/IN' denied

UNOFFICIAL I am running several small networks with Samba 4 acting as AD/DC. I want to upgrade the OS and Samba on the older servers. But I understand that to upgrade the OS, I need to do a new install (at least to get from Centos 6 to 7). I don't have the luxury of new hardware, so creating a secondary DC and taking over from PDC is not an option. These are small networks so recreating the

On Fri, 2018-03-23 at 10:44 -0400, lingpanda101 via samba wrote: > > Andrew in another topic discussed the issue. See below. > > "This is the failed re-index thing we had brought up by a number of > other posters late last week. I'll be working on that today. > > Run the sambaundoguidindex script and stay with 4.7 for now until I can > fix it. A patch for

I just installed a samba4 dc and I see that Power Users group is missing, is possible to create that group so that a workstation joined in the domain can install software using users belonging to that group and how it can be done? actually simply creating a group with that name doesn't get any privilege to that group users.

Hi Louis, > > At this point i can not recommend to upgrade to 4.9.0 or 4.9.1, a side note on this. > The bug in question why im blocking it for production, does not happen for domain members and AD-DC's but it's still a risk in my opinion. > Because for this bug, your obligated to set the idmap ... : settings or run : net groupmap add sid=S-1-5-32-546 unixgroup=nobody