Hello, I have couple of samba 4.5.10 AD DC running that I've been planning to upgrade to 4.7.latest I"ve done upgrades previously (from 4.3), so I know the procedure, but I've been checking on samba list regularly, and I see some people having issues after update, mainly with replication. So how safe is it now? Are there still known issues? Should i upgrade 4.5 -> 4.6 -> 4.7 or directly go to 4.7.latest? Samba I'm running is compiled from source on Centos 7. Regards, Kacper
Dear Kacper, For us the upgrade is currently blocked by this bug: https://bugzilla.samba.org/show_bug.cgi?id=13123 It blocks our automated deployment of Windows clients. Best, Tim On 01.12.2017 13:46, k.wirski via samba wrote:> Hello, > I have couple of samba 4.5.10 AD DC running that I've been planning to upgrade to 4.7.latest > > I"ve done upgrades previously (from 4.3), so I know the procedure, but I've been checking on samba list regularly, and I see some people having issues after update, mainly with replication. So how safe is it now? Are there still known issues? Should i upgrade 4.5 -> 4.6 -> 4.7 or directly go to 4.7.latest? > > Samba I'm running is compiled from source on Centos 7. > > Regards, > Kacper
On 12/01/2017 01:46 PM, k.wirski via samba wrote:> I"ve done upgrades previously (from 4.3), so I know the procedure, but I've been checking on samba list regularly, and I see some people having issues after update, mainly with replication. So how safe is it now? Are there still known issues? Should i upgrade 4.5 -> 4.6 -> 4.7 or directly go to 4.7.latest?We upgraded straight from 4.5 to 4.7.2. Since we had some corruption, we upgraded by: = bringing the 4.5 DCs online in a seperated environment - adding a new temporary 4.7.2 DC - make absolutely sure everything replicated successfully to that new DC - power off the old DCs - reize fsmo roles, cleanup the database, etc - add new 4.7.2 DCs using their old names/ips - remove the temporary DC After this, we swapped the 4.5 production DCs for the new 4.7.2 DCs in the production network, and nobody noticed the change. Except for one or two users and computers that had changed their passwords during the above procedure. The above procedure took some testing and multiple tries, but now, on 4.7.3, everything is running absolutely beautifully. We are specially happy with the new auth audit logging. MJ
02.12.2017 2:16, mj via samba пишет:> - power off the old DCs > - reize fsmo roles, cleanup the database, etcwhy not to transfer roles while old DC are online?> - add new 4.7.2 DCs using their old names/ips > - remove the temporary DCwhy not simply add new DCs to current production domain? I'm thinking about way to upgrade too, but using "separated environment" and restore current production servers from backups seems too complicated for me. I don't know what changes was made in prodiction domain while doing procedure above, if it will take day or two (and it wiil be lost)> The above procedure took some testing and multiple tries,hmm :) _ Mike