similar to: move domain member server to new hardware

I?d get the new server ready, sync all data including xattrs & ACLs with rsync -AXav You probably use AD or RID. Just use the same idmapping on the new server. Probably just copy old smb.conf to new machine. When all is rsynced just remove the old server from the AD, turn off, assign name and IP address to new server. Join domain. That should do. If all goes very wrong you can just power on

Am 06.06.24 um 19:51 schrieb Stefan G. Weichinger via samba: > Am 31.05.24 um 14:38 schrieb Luis Peromarta via samba: >> I?d get the new server ready, sync all data including xattrs & ACLs >> with rsync -AXav >> >> You probably use AD or RID. Just use the same idmapping on the new >> server. Probably just copy old smb.conf to new machine. will do more or

Am 31.05.24 um 14:38 schrieb Luis Peromarta via samba: > I?d get the new server ready, sync all data including xattrs & ACLs with rsync -AXav > > You probably use AD or RID. Just use the same idmapping on the new server. Probably just copy old smb.conf to new machine. > > When all is rsynced just remove the old server from the AD, turn off, assign name and IP address to new

On Fri, 7 Jun 2024 15:35:07 +0200 "Stefan G. Weichinger via samba" <samba at lists.samba.org> wrote: > Am 06.06.24 um 19:51 schrieb Stefan G. Weichinger via samba: > > Am 31.05.24 um 14:38 schrieb Luis Peromarta via samba: > >> I?d get the new server ready, sync all data including xattrs & > >> ACLs with rsync -AXav > >> > >> You

Am 07.06.24 um 15:56 schrieb Rowland Penny via samba: >> Could I join the domain with another name and IP now ... to be able >> to test things (introducing btrfs snaphots this time) with all >> AD-features, but on a "test name"? And then leave the domain, change >> FQDN/IP and rejoin? > > I would create a 'test' machine and join that, once you are

I run 2 DCs at a site, Debian 12.5, so far samba-4.19.6 from backports. Today I upgraded one of them, this brought samba-4.20.1 Now on this one DC stuff like "wbinfo -g" fails: # wbinfo -g could not obtain winbind interface details: WBC_ERR_WINBIND_NOT_AVAILABLE could not obtain winbind domain name! failed to call wbcListGroups: WBC_ERR_WINBIND_NOT_AVAILABLE Error looking up domain

Am 2017-07-11 um 14:57 schrieb Rowland Penny: > On Tue, 11 Jul 2017 14:47:50 +0200 > "Stefan G. Weichinger" <lists at xunil.at> wrote: > >> Am 2017-07-11 um 14:40 schrieb Rowland Penny: >> >>>> Restarted winbind, did "killall -HUP" on smbd and nmbd. >>>> >>>> still can't login to DM via smbclient and that

Am 2017-07-11 um 14:40 schrieb Rowland Penny: >> Restarted winbind, did "killall -HUP" on smbd and nmbd. >> >> still can't login to DM via smbclient and that mentioned user. >> >> I assume I need to restart all the smbd daemons ... ? > > Well, you wouldn't be able to, would you, what with having this in > smb.conf: > > template

On 27/11/2019 10:12, Stefan G. Weichinger via samba wrote: > (resend 2 ... blocked again) > > Am 27.11.19 um 11:02 schrieb Rowland penny via samba: > >>> I now have the name of the domain and the IPs of the DCs etc ... so I >>> could theoretically start from scratch more or less and *maybe* switch >>> to backend AD here. >>> >> Do you use the

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Due to a hardware move (machines needing to be powered off, moved in another rack) , some CentOS.org services will be unreachable for a short period of time. Impacted services : * cbs/Community Build System (aka http://cbs.centos.org) Koji web/hub and builders will be down Migration is scheduled for Thursday January 8th, 3:00 pm UTC time. You can

I have an FAQ, I assume I know the answer but want to be sure before I run into issues: At one customer they get new network cabling and switching this week. This means that the connection between the 2 floors will have to be offline as well for some time, while the upper floor should stay active. I have 2 samba DCs there and plan to move one of them to the upper floor for that time ... and

Aah.. Sorry typo. systemctl unmask samba-ad-dc (umask / unmask ) systemctl enable samba-ad-dc systemctl start samba-ad-dc Im very buzy, so slow in responce atm, but if a service fails to upgrade and starts it gets masked. Unmasking is needed then. To make sure its all enable i also run extra enable. > -----Oorspronkelijk bericht----- > Van: Stefan G. Weichinger [mailto:lists at

Am 2017-07-11 um 11:43 schrieb Rowland Penny: > On Tue, 11 Jul 2017 10:21:37 +0200 > "Stefan G. Weichinger via samba" <samba at lists.samba.org> wrote: > >> Am 2017-07-11 um 09:34 schrieb Stefan G. Weichinger via samba: >> >>> [2017/07/11 09:31:17.790046, 2] >>> ../source4/dns_server/dns_query.c:1019(dns_server_process_query_send)

----- "Ben M." <centos at rivint.com> wrote: > Does this appear to be a sound procedure? I have one inline question. I read your version of the procedure and it looks like you want to skip the pvmove. That's fine, but it means more downtime (an unreliable estimate is one minuted per GB). In that case, you don't even need the snapshot. You won't need a point in time

Am 2017-07-11 um 13:37 schrieb Stefan G. Weichinger: >> Having everything in AD, gives you the possibility of using different >> Unix home dirs etc per person. > > Not needed. I am the only UNIX user there. > > I only need separate [home] dirs for a group of users: > > some customers of my customer come by to do some work with a specific > software and I want

Greets, samba-users, I am forced to accept the fact that the migration to some new software leads my customer to introduce a windows-based DC ... degrading my samba/ldap-setup to domain-members ... *sigh* Now I am asked what windows server to prefer (in terms of how samba will interact): ms windows server 2003 or 2008 ? I googled a bit but haven't yet found a clear answer so I choose to

Hi all, We currently have a Fedora 11 machine (about to be upgraded to Fedora 15 though) running Samba 3.4.7 as our PDC and multiple BDC "home servers" running various versions of samba and OS. What I am needing is a fail proof way to migrate the PDC function off the current machine and onto another new fresh install. Currently our PDC is also the home server for one of our

On August 4th (~9AM PDT, exact time TBD), all LLVM related mailing lists will move to a new mailing list server and will change to listname at lists.llvm.org. LLVMDev will probably change to LLVM-Dev to preserve consistency. This means a couple of things: 1) All mailing lists will be down on August 4th. We anticipated at least the full day of downtime (hopefully less if things go well). 2) SVN

On Mon, Nov 16, 2020 at 10:52 AM Luke Barone via samba < samba at lists.samba.org> wrote: > It'll be fine > > On Mon., Nov. 16, 2020, 1:32 a.m. Stefan G. Weichinger via samba, < > samba at lists.samba.org> wrote: > > > > > > > I have an FAQ, I assume I know the answer but want to be sure before I > > run into issues: > > > > At

Am 2017-07-11 um 14:57 schrieb Rowland Penny: >> # smbclient \\\\server\\daten -Usgw%PW >> session setup failed: NT_STATUS_UNSUCCESSFUL > > Restart all the Samba binaries on the DM > > Then check that the OS knows your user with: > > getent passwd sgw libnss_winbind was missing! Now both results are the same user-names in /etc/passwd ... rmed now I was 100%