Cloning disk to bigger one and auto-unjoin / join to domain

Hi
I know that after changing for example motherboard it's required to activate Windows again. While smaller changes like adding RAM - it's not required. But what about: In company's domain computer old SSD was too small (120GB) and was cloned to newer one (250GB) to give user more space for his stuff. Disk was cloned using hardware 2-bay cloning station (cheap one ca. 80$ but works great) My question - after cloning this are there any additional steps required or only put freshly-cloned 250 GB disk into case and start machine ? I'm asking because not sure if this computer will automatically unjoin from my domain into regular Workgroup. What are the rule about it ?

The disk is an exact copy so won't need activating and should have no effect on being in the domain

As Samuria mentioned, a cloned disk is exactly the same as the source disk.
Some cloning software won't resize the C: partition so you will need to do it manually using Disk Manager (C:\Windows\System32\diskmgmt.msc)

hi all. cloning 1:1 is my forte. i have been doing it for almost a decade. the first thing i do after installing any windows is to completely destroy system restore/shadow copying etc. because to me those MS features are just pure bs. when u r talking about 1:1 cloning, that is bit-by-bit transfer of data regardles of type, then both Samuria & Megahertz are both correct : source + target are = exactly the same.

However once in maybe 10 clones every day, if u r observant enough, you appear to start seeing desrepancies.

Then, go to big cloner forums like Acronis, and see why ppl still encounter so many complications, offset settings, driver errors, etc. well most of them don't do 1:1 cloning, they could be using other utilities like backing & restore, imaging, scheduled back up etc. Now some of them do 1:1 and stil suffer stuff like 'help my audio driver is missing' (escpecially IDT VERY VERY COMMON), i left the synaptics swicth on but strangely my clone had the switch OFF the first time i log in.

The secret is....exactly this - the cloning (unless one of the counterparts source + target are physically faulty to begin with) is truuly not in error- they r indeed an exact match - Discrpancies may arises the FIRST TIME U SLOT THE NEW CLONE INTO WINDOWS ENVIRONMENT, windows runs driver checks/preliminary hardware diagnostics, AND IT SOMETIMES MAKE FALSE POSITIVES. Eg. Forces an old obsolete generic driver to clash with your branded new version IDT driver and causing the audio controller under device manager not to operate. with a yellow triangle.

in fact ther'es nothing worng with the clone. it's some of the steps windows does during that first integration between itself and your newly cloned disk. so my advice just uninstall/reinstall device manager drivers that are flagged, run an sfc /scannow, advanced disk cleaner option, u sould be ok.