similar to: Upgrade Samba versions on the domain

>On Tuesday, October 29, 2019, 03:41:35 PM CDT, Andrew Bartlett via samba <samba at lists.samba.org> wrote: >>On Tue, 2019-10-29 at 19:23 +0000, Mircea Husz via samba wrote: >> We're adding a new datacenter and am taking the opportunity to >> upgrade Samba version to 4.11. We have three AD servers currently on >> version 4.7.9. >> I plan to add a new AD

Hi Roland, Thank you for the explanation. Allow me to press the point, I'd like to understand what I'm doing. Is there value in me remapping them from their 3000000 - range default as I see it on the AD server? What is the reason for specifying a lower range such as 3000-7999 ? Thank you, -Mike On Friday, January 27, 2017 3:42 PM, Rowland Penny via samba <samba at

Hi, In order to work around a known upstream bug I needed to add a udev rule to pxeboot initrd.img on CentOS 7. The process is straightforward: 1 - extract the pxeboot initrd.img to a new directory 2 - add the udev rule needed to fix the bug 3 - pack and compress it back in initrd.img format The resulting updated image works, it fixes the upstream bug and life is good. But although it works,

On Sat, 2017-03-11 at 13:39 +1300, Andrew Bartlett via samba wrote: > On Fri, 2017-03-10 at 16:17 -0600, Mircea Husz via samba wrote: > > > > Hello, > > > > I just configured a three-site DCs setup with Samba 4.6.0, and > > replication worked great. > > But then I added a custom cert to one of the DCs to authenticate > > various apps against it. I

That makes sense. I didn't realize that IDs for BUILTIN accounts are not identical between DCs. Since they are not identical they need to be mapped to a consistent set. Thank you for the explanation. On Friday, January 27, 2017 4:57 PM, Rowland Penny via samba <samba at lists.samba.org> wrote: On Fri, 27 Jan 2017 22:00:11 +0000 (UTC) Mircea Husz <mirceahusz at yahoo.com> wrote:

All, I configured two DCs (Samba version 4.5.5) replicating ad.corp.com in two sites ( https://wiki.samba.org/index.php/Active_Directory_Sites) Following 'DNS configuration on Domain Controllers' section from this wiki https://wiki.samba.org/index.php/Joining_a_Samba_DC_to_an_Existing_Active_Directory If I configure nameserver DC1 to be the first resolver for DC2, samba_dnsupdate

Hello, I just configured a three-site DCs setup with Samba 4.6.0, and replication worked great. But then I added a custom cert to one of the DCs to authenticate various apps against it. I used this wiki https://wiki.samba.org/index. php/Configuring_LDAP_over_SSL_(LDAPS)_on_a_Samba_AD_DC Now I can authenticate my apps over LDAPS against my DC, but broke replication. How do I need to configure

-------------------------------------------- On Mon, 3/6/17, lingpanda101 via samba <samba at lists.samba.org> wrote: Subject: Re: [Samba] DC site replication issue ? To: samba at lists.samba.org Date: Monday, March 6, 2017, 9:20 AM On 3/6/2017 9:56 AM, Mircea Husz via samba wrote: > All, > > I'm migrating a samba3 domain to a new samba4 AD version 4.5.5. Did a fair

On Tue, 2017-05-30 at 12:18 +0100, Rowland Penny via samba wrote: > On Tue, 30 May 2017 13:09:38 +0200 (CEST) > > Sébastien QUESSON via samba <samba at lists.samba.org> wrote: > > > > > > All I can think of is, you have a user with > > > > > > > > > > 'sAMAccountName=username' and another with 'CN=username', this >

I scripted the creation of snapshots and it works fine. Now I'd like to run the script as non-root. virsh snapshot-create-as --domain hq-live-v01 \      --name snappy \      --diskspec vda,file=/var/lib/libvirt/images/hq-live-v01.snappy,snapshot=external \      --diskspec vdb,file=/var/lib/libvirt/images/hq-live-storage.snappy,snapshot=external \      --disk-only --quiesce --atomic This

All, I'm migrating a samba3 domain to a new samba4 AD implementation. The samba3 domain is at the top level corp.com, and after having read the naming FAQ we decided to create ad.corp.com for Samba4. We're doing a test migration and so far things are going well. Part of test is migration of old samba servers, which involves joining them to AD, which creates a DNS record under

All, We have a samba3 domain which provides logon services for Windows clients, and several cifs shares, some for Windows clients and some for linux servers to mount. I am testing samba 4.5.4 in a lab to understand all that needs to happen for a migration to AD on samba4. During testing we bumped up against winbind config for linux member servers. Since we want users to authenticate against AD,

On Wed, Mar 20, 2019 at 15:48:43 -0500, Eric Blake wrote: > On 3/20/19 1:50 PM, Mircea Husz wrote: > > I scripted the creation of snapshots and it works fine. Now I'd like to run the script as non-root. > > > > virsh snapshot-create-as --domain hq-live-v01 \ > >      --name snappy \ > >      --diskspec

On Mon, 2017-03-06 at 15:48 -0500, lingpanda101 via samba wrote: > On 3/6/2017 12:53 PM, Mircea Husz wrote: > > > > -------------------------------------------- > > On Mon, 3/6/17, lingpanda101 via samba <samba at lists.samba.org> > > wrote: > > > >   Subject: Re: [Samba] DC site replication issue ? > >   To: samba at lists.samba.org > >  

Hi everyone, I searched previous postings and I couldn't find a definitive answer on this.. I run a small lab of RHEL/Centos Based servers on which there's VMWare Workstation running on a non-standard port but still manageable by tools like VMrun (and the Fusion of Workstation GUI, of course). I'm trying to use virsh with this setup and getting the following error from both

For direct upload, a suitable host must be in status 'Up' and belong to the same datacenter as the created disk. Added these criteria to the host search query. --- v2v/rhv-upload-plugin.py | 28 ++++++++++++++++++++++++---- 1 file changed, 24 insertions(+), 4 deletions(-) diff --git a/v2v/rhv-upload-plugin.py b/v2v/rhv-upload-plugin.py index da309e288..931fcfaa2 100644 ---

- wrap a too long line - join strings in multiple lines using + (plus) instead of \ (backslash) --- v2v/rhv-upload-plugin.py | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/v2v/rhv-upload-plugin.py b/v2v/rhv-upload-plugin.py index 4fad27fb8..bdc1e104a 100644 --- a/v2v/rhv-upload-plugin.py +++ b/v2v/rhv-upload-plugin.py @@ -86,7 +86,8 @@ def find_host(connection):

From: root <root@localhost.localdomain> For direct upload, a suitable host must be in status 'Up' and belong to the same datacenter as the created disk. Added these criteria to the host search query. --- v2v/rhv-upload-plugin.py | 18 +++++++++++++++--- 1 file changed, 15 insertions(+), 3 deletions(-) diff --git a/v2v/rhv-upload-plugin.py b/v2v/rhv-upload-plugin.py index

All, I'm migrating a samba3 domain to a new samba4 AD version 4.5.5. Did a fair amount of testing on isolated vlans including two sites and replication between two domain controllers. I'm now rolling out DCs intended to become production shortly. One is in Chicago, the other in NY, and each is configured in its own timezone with NTP synching up. I am looking at a potential replication

After upgrading my puppet master to 2.6.8 from 2.6.2, I intermittently get things like: puppet-master[29789]: (Scope(Class[Auth::Kerberos_ldap])) Could not look up qualified variable ''common::datacenter::ldap::ldapservers''; class common::datacenter::ldap has not been evaluated puppet-master[29789]: Failed to parse template auth/rhel5/ ldap.conf.erb: undefined method