similar to: Migrating SAMBA 3 NT4 domain to SAMBA 4 AD

On 2020-08-24 02:21, Rowland penny via samba wrote: > On 24/08/2020 03:59, K. R. Foley via samba wrote: >> Hi, >> >> We have an older Samba3 NT4 domain, which uses a TDB backend. We have >> a variety of different versions of Windows clients. We need to migrate >> to a Samba 4 AD domain. I have successfully tested the classic upgrade >> on a new server in

On 24/08/2020 03:59, K. R. Foley via samba wrote: > Hi, > > We have an older Samba3 NT4 domain, which uses a TDB backend. We have > a variety of different versions of Windows clients. We need to migrate > to a Samba 4 AD domain. I have successfully tested the classic upgrade > on a new server in an isolated network, but I had to work through some > issues along the way. My

On 2020-08-24 08:45, Rowland penny via samba wrote: > On 24/08/2020 14:09, K.R. Foley wrote: >> Regarding the statement "they will ignore the PDC" above, is there >> really no way to undo that? > > Only by not letting your clients contact the AD DC. > > One of the first things that the migration to AD script does is to > obtain the SID from the NT4-style

Rowland penny via samba ha scritto il 24/08/20 alle 16:36: > On 24/08/2020 15:25, K.R. Foley wrote: >> Let me rephrase the question. Just for my understanding. If a client >> has communicated with an AD DC, but we now want to roll back. If we >> remove the AD DC from the network, is it possible to get the client to >> communicate with the NT4-style PDC again? >

As you may remember I went through a classic-upgrade a few months ago. I have a second domain to migrate and I am again/still scared to attack that ;-) As I prepare my test VM and try to remember all those details the customer has purchase 2 new Windows 10 PCs and I was asked to take them into production. Is there a way to join them to the existing NT4-based Samba-domain or not? I find various

On 05/15/17 08:06, Rowland Penny via samba wrote: > On Mon, 15 May 2017 13:25:03 +0200 > "Stefan G. Weichinger via samba" <samba at lists.samba.org> wrote: > >> As you may remember I went through a classic-upgrade a few months ago. >> >> I have a second domain to migrate and I am again/still scared to >> attack that ;-) >> >> As I

Hi, We have an upcoming project to migrate Samba first into a new Hardware then the AD migration. Our hardware is old and we need to migrate. Please allow me to explain the current setup - Server : Physical - OS: Ubuntu 14.04 running Samba 4.0.0. Even though it is running Samba 4, we are using configs from Samba3. - Roles: DC, DNS , DHCP and Shares - Database: TDB - DNS: BIND9 - Clients: Mix of

Am 2017-05-15 um 14:06 schrieb Rowland Penny via samba: > Windows doesn't support joining Windows 7 to an NT4-style domain, so > they definitely won't support windows 10. Well, I joined Win7 to NT4-domain back then ... (reg-hack, but anyway) > You may find a way around this lack of Microsoft support, you may also > find that a subsequent Windows update stops it working

Hi Rowland, I did that initially and that came with Failed to connect to ldap URL 'ldap://lin-pdc.lin - LDAP client internal error: NT_STATUS_BAD_NETWORK_NAME Hence I removed the whole ldap:// bit After your email I tried again but using ldap://localhost and it seems to have worked. Not sure what the issue is with the fqdn. I could run ldap queries when using fqdn. Regards, Praveen

Hi, today I tried to migrate an old NT4 PDC to Samba 3 as described in http://samba.org/samba/docs/man/Samba-HOWTO-Collection/NT4Migration.html but with the Samba databases on LDAP: Whenever I tried that net rpc vampire -S NT4PDC -U administrator%passwd I received error messages that the users cannot be created. When I set debugging to level 2, it told me about Found bogus group

Hi, I'm trying to prepare migration from NT4 server to samba with ldap backend. For testing and simulating I have prepared one NT4 server, one Centos 5.5 samba server and now I have almost working setup for vampiring users and groups. Using following packages: samba3.i386 3.5.7-43.el5 samba3-cifsmount.i386 3.5.7-43.el5 samba3-client.i386 3.5.7-43.el5 samba3-doc.i386 3.5.7-43.el5

On Tue, 2018-02-20 at 18:11 +1000, Rob Thoman via samba wrote: > Hi Guys, > Have not had any feedback on this. I found the following article but not > sure if it is valid > > Here is what we are planning, high level > Phase1: > > - Add a new Samba 4 server (VM in a new hardware). Join it to the existing > domain > - Promote this server as DC in the Samba 3

Hi, We currently have this setup (inherited from my predecessor): Samba 3.2.x domain with custom (mysql) passdb backend. This means the passdb *.tdb files are not being updated and all is retrieved & stored in MySQL. I would like to migrate this to a 'regular' Samba 4.x setup with AD Since the *.tdb files are not updated, I cannot copy the *.tdb files and go the classicupgrade

On 11/12/15 15:41, Bob Thomas wrote: >/First, Thank you all for this forum, as I am fairly new at both Ubuntu />/and Samba I have found most the answers to my issues here. />//>/Now correct me if I am wrong but Samba 4.3.2 should be able to support />/Domain Trusts. If so maybe you can help me, here is what I have: />//>/NT4 Domain: adc.com (Holds are production servers and

On 12/09/2019 20:37, Bart?omiej Solarz-Nies?uchowski via samba-technical wrote: > Dear List, Sorry but this is the wrong list, it should have been the samba mailing list, not samba-technical, I have cc'ed the samba list, please reply there. > > I need to migrate my Samba NT4 domain (5000+ users, 600+ workstation, > 50+ printers) urgently. > > > Backend for samba is on

Am 2016-11-25 um 12:10 schrieb Stefan Kania via samba: > Am 25.11.2016 um 10:12 schrieb Stefan G. Weichinger via samba: >> >> Just a general question ahead: >> >> I have various issues with Samba-4.2.10 on Debian 8.6 (in combination >> with NT4-based domain and Win10pro-clients). >> > Windows 20 is NOT supporting NT-style Domains anymore, no matter which

Have a need to support one NT4 server in one environment and trying to escape the past a bit by upgrading the PDC which currently runs Samba-3.6.24. So far my testing has shown that Samba4-4.5 as a PDC appears to work just fine. I can even install Exchange 5.5 on the test NT4 server in this environment. However attempting the same Exchange 5.5 installation when running Samba4 in AD mode it

John, We previously corresponded on our testing of Samba 3.0.0 RC4. Since then, we have downloaded the Samba 3.0.0 Release version for testing with some interesting results. The Setup Major Networks: Solaris (NIS), Windows Native NT4 Domain Our Test Plan We are testing Samba 3.0 as a candidate for replacing the old NT4 Domain. Being a complex production networking environment, we replicated

Rowland Penny via samba писал 2018-09-03 17:12: > On Mon, 03 Sep 2018 04:27:07 +0000 > "Konstantin Boyandin \(lists\) via samba" <samba at lists.samba.org> > wrote: > >> Hello, >> >> Going further with migrating NT4 domain (Samba 3) to Samba 4. Thanks >> for the previous suggestions. >> >> When doing >> >> #

Hello. For may years we're running a classic (NT-style) domain with many machines (mostly windows7 these days). Initially it was set up using samba3, and now we upgraded samba to samba4 (4.1.11), without introducing AD functionality (it is not needed). I especially asked in several places whenever samba4 supports NT-style domains, and got several positive answers. Now, we're trying to