similar to: Volume Activation with Samba AD

Am 24.07.2018 um 18:34 schrieb Thomas Glanzmann: > Hello Christian, > >> what I meant is not acting as a KMS server but something new Microsoft >> introduced. In windows 10 the tool vor managing Volume Licences asks if >> you have a KMS server or if you want to use AD for activating the >> software. I haven't tried it yet as I would need to setup a test >>

On Tue, 2018-07-24 at 19:15 +0200, Christian Naumer wrote: > Am 24.07.2018 um 18:34 schrieb Thomas Glanzmann: > > Hello Christian, > > > > > what I meant is not acting as a KMS server but something new Microsoft > > > introduced. In windows 10 the tool vor managing Volume Licences asks if > > > you have a KMS server or if you want to use AD for activating

Hello Christian, > what I meant is not acting as a KMS server but something new Microsoft > introduced. In windows 10 the tool vor managing Volume Licences asks if > you have a KMS server or if you want to use AD for activating the > software. I haven't tried it yet as I would need to setup a test > environment. > So I asked here to see if somebody tried it before. I can

Hello Andrew, > I'm also interested in working with someone who is willing to set up a > reproduction (perhaps testing with windows AD) and feed me logs etc. I could do that. Are you planning on implementing a KMS server in Samba similiar to kmspico[1]? [1] https://www.officialkmspico.com/ Cheers, Thomas

Hello, what I meant is not acting as a KMS server but something new Microsoft introduced. In windows 10 the tool vor managing Volume Licences asks if you have a KMS server or if you want to use AD for activating the software. I haven't tried it yet as I would need to setup a test environment. So I asked here to see if somebody tried it before. I can test this with samba but I don't have a

Hello all, as the title says. Has anybody ever tried using a Samba AD for storing KMS keys (at least I think this is how it works...)? Regards Christian -- Dr. Christian Naumer Research Scientist Plattform-Koordinator Bioprozesstechnik B.R.A.I.N Aktiengesellschaft Darmstaedter Str. 34-36, D-64673 Zwingenberg e-mail cn at brain-biotech.de, homepage www.brain-biotech.de fon +49-6251-9331-30

> Am 20.05.2019 um 16:41 schrieb L.P.H. van Belle via samba <samba at lists.samba.org>: > > Hello Cristian, > > Well, nothing to say about your steps, these looks good. > And lmdb could be disable in the sernet packages, cant say, i dont know. > > And only one DC has these problems or all? If only one DC crashed. > Which DC crashes. Last added? Oldest? I

Thanks, Can you post the output of : samba-tool drs showrepl -d0 If needed anonimize or send it direct to me. Greetz, Louis > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens > Christian Naumer via samba > Verzonden: woensdag 10 mei 2017 11:55 > Aan: samba at lists.samba.org > Onderwerp: Re: [Samba] Kcc connection >

Hello you all, I did some more tests used Samba 4.10.4 and still the same Problem. I also upgraded all the DCs and the problem is the same on all of them. Downgraded all of the an problem is gone. I went up to loglevel 5 an saw nothing that was related. How do I debug further? @rowland: I wrote to bugzilla-maintenance at samba.org to get an bugzilla account but haven't gotten any feedback.

Ok here is the output: If the output of the other DCs is needed let me know. On the other DCs there are kcc connections for all other DCs. Just not on dc1. [root at dc1 ~]# samba-tool drs showrepl Default-First-Site-Name\DC1 DSA Options: 0x00000001 DSA object GUID: 1781607c-77e8-405d-8c3a-b7e142dd30c4 DSA invocationId: dc096a8a-773d-4a63-8e2a-288ab747557b ==== INBOUND NEIGHBORS ====

Am 30.08.19 um 13:09 schrieb L.P.H. van Belle via samba: > Now Christian, this failes for me. > radtest -t mschap 'NTDOM\username" 'passwd' localhost 0 testing > ( MS-CHAP-Error = "\000E=691 R=1 C=58f41f1a946ac94a V=2") > > So my question here is, are the username at REALM logins also working for you. > And are you using in smb.conf : winbind use

Hello Lois, thanks for looking into this. Have you looked at what the original poster shared in the bug report? https://bugzilla.samba.org/show_bug.cgi?id=14268 I don't have a big problem with this, just trying to help. Maybe the original poster can say more with regards of the problem he has with this. here are more of my details. Regards #####samba-debug-info.txt##############

Hai, Did you configure mutual authentication and integrity for the new share? I suspect something related to this, since you posted : > \\mydomain\sysvol does work, as well as \\mydomain\netlogon. > But, there is some issue with any \\mydomain\newshare. Good info here : https://blogs.technet.microsoft.com/askpfeplat/2015/02/22/guidance-on-deployment-of-ms15-011-and-ms15-014/

There is bug for this: https://bugzilla.samba.org/show_bug.cgi?id=12303 I am testing this option to resolve this: client ipc signing = No But I am not yet sure if it works. Regards Christian Am Mittwoch, den 16.11.2016, 15:41 -0500 schrieb Sonic via samba: > Domain users using Windows 7 systems lose the ability to connect to > Samba shares. Some users can connect one day but then

Hello, I think the configuration changed in 4.6. see here: https://wiki.samba.org/index.php/Idmap_config_ad Regards > Am 18.02.2018 um 00:00 schrieb Andrey Repin via samba <samba at lists.samba.org>: > > Greetings, All! > > I'm stumbled upon an event I can't understand. Rolled out a new Ubuntu 17.10 > box in preparation for eventual 18.04 launch and… it just

Am 29.04.2018 um 12:35 schrieb Zdravko Zdravkov via samba: > [sssd] >> domains = xxxx >> config_file_version = 2 >> services = nss, pam >> [domain/xxxx] >> ad_domain = xxxx >> krb5_realm = XXXX >> realmd_tags = manages-system joined-with-samba >> cache_credentials = True >> id_provider = ad >> krb5_store_password_if_offline = True

Yes that seems to be working as desired. Thanks much. On Tue, Nov 13, 2018 at 10:50 AM Christian Naumer via samba < samba at lists.samba.org> wrote: > I don't know if this still works but it does what you want: > > https://www.samba.org/samba/docs/current/man-html/idmap_nss.8.html > > > Regards > > > Am 13.11.18 um 15:37 schrieb Rowland Penny via samba: >

Am 21.03.19 um 15:50 schrieb John McMonagle via samba: > That's sounds promising > How did you migrate your data? We did the "classicupgrade" as discribed in the wiki. > Did you need to add any schema to samba4 ad? No. But this depends of what you have in ldap now. Do you have dhcp-data in there? > > Were in 5 cities and some of the Internet is not 100% reliable.

Am 11.04.19 um 23:37 schrieb Vex Mage via samba: > The problem is that there is no apparent upgrade path for the old system. > The corner stone of this deployment is that there's an existing centralized > authentication server however; Samba4 seems wants a paradigm shift so that > it becomes the princess of its own castle. It seems to me that it has > become the very thing that

Hai, I suggest for your monitoring, setup an caching name server. https://www.digitalocean.com/community/tutorials/how-to-configure-bind-as-a-private-network-dns-server-on-debian-9 A desent base to start ready. This speeds up your resolving a lot and that helps you monitoring also. Optional you can make this dns server also a slave dns and caching dns. This would be my preffered setup.