[Fwd: Re: Upgrading AD DC 4.2.x to 4.3.0]

[Daniele Dario]

On ven, 2015-09-18 at 20:05 +1200, Andrew Bartlett wrote:
> On Fri, 2015-09-18 at 09:05 +0200, Daniele Dario wrote:
> > -------- Forwarded Message --------
> > > From: Daniele Dario <d.dario76 at gmail.com>
> > > Reply-to: d.dario76 at gmail.com
> > > To: Andrew Bartlett <abartlet at samba.org>
> > > Subject: Re: Upgrading AD DC 4.2.x to 4.3.0
> > > Date: Thu, 17 Sep 2015 13:15:28 +0200
> > > 
> > > 
> > > 
> > > On gio, 2015-09-17 at 22:34 +1200, Andrew Bartlett wrote:
> > > > On Thu, 2015-09-17 at 12:11 +0200, Daniele Dario wrote:
> > > > > Hi samba team,
> > > > > I'd like to update my DCs to 4.3.0 version and before start I
> > > > > have a
> > > > > couple of questions.
> > > > > 
> > > > > I have 2 DCs running 4.2.1 and they were affected by bug 11235
> > > > > and
> > > > > had
> > > > > to apply the workaround suggested by Rowland Penny
> > > > > 
> > > > > ...
> > > > >    server services = -winbindd + winbind
> > > > > ...
> > > > > 
> > > > > Now, do I need to stop all DCs to upgrade to 4.3.0 or is it
> > > > > safe to
> > > > > have
> > > > > one running 4.2.x while the other 4.3.0?
> > > > > 
> > > > > Second question, bug 11235 is still opened. Do I have to keep
> > > > > the
> > > > > above
> > > > > line in my smb.conf or can I remove it and enable winbindd?
> > > > > 
> > > > 
> > > > It won't help: in the smb.conf winbind has been left as a
> > > > compatibility
> > > > alias, the code that was the internal 'winbind' is now in the big
> > > > bit
> > > > -bucket in the sky...
> > > > 
> > > > Sorry,
> > > > 
> > > > Andrew Bartlett
> > > > 
> > > 
> > > Sorry Andrew, are you saying that the line is useless but I won't
> > > get in
> > > trouble upgrading to 4.3 and using winbindd or are you telling me
> > > to NOT
> > > update until the mentioned bud gets fixed?
> > > 
> > > Daniele.
> > 
> > Sorry, replied only to Andrew Bartlett: forwarding to all list.
> > 
> > FYI, I built the 4.3.0 on a new machine and joined it to the domain
> > as
> > an additional AD DC.
> > To do it I dumped the idmap.ldb from one of the working DCs with
> > 4.2.1
> > and copied the smb.conf without the line
> > 
> > ...
> > server services = -winbindd +winbind
> > ...
> > 
> > (and changing the host name) and everything seems to be ok. Users and
> > groups kept the same uids/gids so can I assume the bug is solved or
> > is
> > it just that I didn't hit it this time?
> 
> I'm not very clear on what the bug is exactly, so I can't say if it was
> fixed by ongoing development or just not appearing at the moment. 
> 
> > Would it be ok to update the other DCs to 4.3.0?
> 
> If one works fine, the rest should.  A downgrade is entirely possible
> if required (while not tested, the DB should keep working, we have not
> had any deliberate format changes).
> 
> Andrew Bartlett
> 

Ok. I'll try to update them.
Thanks for your time Andrew,
Daniele.