search for: classisupgrade

On Thu, 6 Jun 2024 13:33:04 +0200 Havany via samba <samba at lists.samba.org> wrote: > - Classisupgrade is destructive for the NT4 Domain, but we can keep > data of the old NT4 Domain and we can rollback to this with ours > Ansible playbooks. We will loose all change between migration and > rollback and we will improve a possible long downtime. > > - With "Big Bang" approach...

...ng is > going to most certainly backfire. It sounds like a fail forward vs fail > backward. When something goes wrong you need to be able to go back to a > working configuration. So I suppose the best option is to do a slow > migration with the ability to quickly do and undo changes. - Classisupgrade is destructive for the NT4 Domain, but we can keep data of the old NT4 Domain and we can rollback to this with ours Ansible playbooks. We will loose all change between migration and rollback and we will improve a possible long downtime. - With "Big Bang" approach we are able to keep o...

Hello, Le 06/06/2024 ? 15:40, Rowland Penny via samba a ?crit?: > On Thu, 6 Jun 2024 13:33:04 +0200 > Havany via samba <samba at lists.samba.org> wrote: > > >> - Classisupgrade is destructive for the NT4 Domain, but we can keep >> data of the old NT4 Domain and we can rollback to this with ours >> Ansible playbooks. We will loose all change between migration and >> rollback and we will improve a possible long downtime. >> >> - With "Big...

Hello Havany, I am just going to jump into this discussion. > We try 2 scenarios : - A "Big bang" migration to an new domain made from scratch : but we need to migrate all users, computers, laptops, filers without loosing profiles, files server access... In a short time (1-2 weeks maximum) - A "classicupgrade" migration, but it need several steps to improve security. And at