samba - Jul 2020 - strategy to migrate dc from one pc to another.

>> Yes, you can run the internal dns server on one DC and Bind9 on 
>> another, I also know that you should upgrade jessie as soon as 
>> possible, it is now EOL.
>> Rowland
which lead me to my second question:

I have a AD primary DC who is under debian Jessie as previously said. 
When i have try to update it to stretch all sort of weird bug have 
appears
on the ad (authentication not working anymore with the ip of the 
computer when trying to connect with remote desktop, but working with 
full computer name MOST of the time but not always etc...).
I have googled a bit but not seeing too much people having to confront 
this, and the people who have have just abandoned the migration.

So does this situation ring any bells to someone ?

At this time i have revert to a former backup and back to my jessie.

What i want to do is to create a new dc on stretch or buster, make it 
secondary, wait it to synchronise, declare the second one as dead and 
make the second the primary one. Am i wrong somewhere ?

Any advice ?

best regards.

> What i want to do is to create a new dc on stretch or buster, make
> it secondary, wait it to synchronise, declare the second one as dead
> and make the second the primary one. Am i wrong somewhere ?
There isn't a "secondary" with AD,  every DC is a peer.

Join the new server as a DC.
Transfer the FSMO roles from the to the new DC.
Demote the old DC.

-- 
Adam Tauno Williams <mailto:awilliam at whitemice.org> GPG D95ED383
Systems Administrator, Python Developer, LPI / NCLA

Hai,  
> -----Oorspronkelijk bericht-----
> Van: samba [mailto:samba-bounces at lists.samba.org] Namens 
> karel de macil via samba
> Verzonden: dinsdag 14 juli 2020 21:55
> Aan: samba at lists.samba.org
> Onderwerp: [Samba] strategy to migrate dc from one pc to another.
> 
> >> Yes, you can run the internal dns server on one DC and Bind9 on 
> >> another, I also know that you should upgrade jessie as soon as 
> >> possible, it is now EOL.
> 
> >> Rowland
> 
> which lead me to my second question:
> 
> I have a AD primary DC who is under debian Jessie as previously said. 
> When i have try to update it to stretch all sort of weird bug have 
> appears
> on the ad (authentication not working anymore with the ip of the 
> computer when trying to connect with remote desktop, but working with 
> full computer name MOST of the time but not always etc...).
> I have googled a bit but not seeing too much people having to 
> confront this, and the people who have have just abandoned the migration.
> 
> So does this situation ring any bells to someone ?
Yes. It does. 
This is due the "big" change made in 2016 by Microsoft.
> 
> At this time i have revert to a former backup and back to my jessie.
More important and not known, where u used RDP, which Client OS+version is used.
> 
> What i want to do is to create a new dc on stretch or buster, make it 
> secondary, wait it to synchronise, declare the second one as dead and 
> make the second the primary one. Am i wrong somewhere ?
Nope and this is also the best option.

I could assist in a Jessie to stretch to buster upgrade. 
Only thing is, i know whats coming and i recommend setup a new server setup
straight on buster.
Sieze the FSMO, and remove the old server. 


> 
> Any advice ?
See up ;-) 
> 
> best regards.
Greetz, 

Louis

Hi i have been able to install samba on a buster and transfer the fmo to 
it.
All is working like a charm.
Your help have been very hhumm helpfull...

thanks you and all who have tried to help me :)

Le 16/07/2020 10:13, L.P.H. van Belle via samba a
?crit?:
> Hai,
> 
>> -----Oorspronkelijk bericht-----
>> Van: samba [mailto:samba-bounces at lists.samba.org] Namens
>> karel de macil via samba
>> Verzonden: dinsdag 14 juli 2020 21:55
>> Aan: samba at lists.samba.org
>> Onderwerp: [Samba] strategy to migrate dc from one pc to another.
>> 
>> >> Yes, you can run the internal dns server on one DC and Bind9
on
>> >> another, I also know that you should upgrade jessie as soon as
>> >> possible, it is now EOL.
>> 
>> >> Rowland
>> 
>> which lead me to my second question:
>> 
>> I have a AD primary DC who is under debian Jessie as previously said.
>> When i have try to update it to stretch all sort of weird bug have
>> appears
>> on the ad (authentication not working anymore with the ip of the
>> computer when trying to connect with remote desktop, but working with
>> full computer name MOST of the time but not always etc...).
>> I have googled a bit but not seeing too much people having to
>> confront this, and the people who have have just abandoned the 
>> migration.
>> 
>> So does this situation ring any bells to someone ?
> Yes. It does.
> This is due the "big" change made in 2016 by Microsoft.
> 
>> 
>> At this time i have revert to a former backup and back to my jessie.
> More important and not known, where u used RDP, which Client OS+version 
> is used.
> 
>> 
>> What i want to do is to create a new dc on stretch or buster, make it
>> secondary, wait it to synchronise, declare the second one as dead and
>> make the second the primary one. Am i wrong somewhere ?
> 
> Nope and this is also the best option.
> 
> I could assist in a Jessie to stretch to buster upgrade.
> Only thing is, i know whats coming and i recommend setup a new server
> setup straight on buster.
> Sieze the FSMO, and remove the old server.
> 
> 
> 
>> 
>> Any advice ?
> See up ;-)
> 
>> 
>> best regards.
> 
> Greetz,
> 
> Louis