So,? I have a MS Windows 2016 AD DC. I've setup samba as a second AD DC running on a low power ARM device and all looks good. If I shut down the Windows DC all looks good then too, initially. However, should the Windows DC be down for any length of time I will encounter DHCP issues. My thoughts on this are two fold. One is running a DHCP server on the ARM box permanently and splitting the scope, the other is configuring up the DHCP server on the ARM device and running it only when it detects the Windows DC is down. Anybody care to comment on the above or anything else related? -- Michael Howard
On 17/06/2020 10:37, Michael Howard via samba wrote:> So, I have a MS Windows 2016 AD DC. I've setup samba as a second AD DC > running on a low power ARM device and all looks good.How did you mange that, Samba supposedly doesn't support the Win2016 schema yet.> > If I shut down the Windows DC all looks good then too, initially. > However, should the Windows DC be down for any length of time I will > encounter DHCP issues. > > My thoughts on this are two fold. One is running a DHCP server on the > ARM box permanently and splitting the scope, the other is configuring > up the DHCP server on the ARM device and running it only when it > detects the Windows DC is down.Why not just run the DHCP server on the ARM device and stop your Windows clients from updating their own records. Rowland
On 17/06/2020 14:43, Michael Howard wrote:> > You are of course correct. Typo. Should read 2012.Damn, I was hopeing you had come up with the magic incantation to allow the join :-D> > I need to resolve various internal host names and would rather not > manage that manually. Or have I misunderstood what you mean?Sort of depends on what you mean by 'internal host names' Rowland