I really feel awkward asking this but I would like to know if there would be any anticipated issues when using rescuezilla to create a backup from my HP Z4 Windows 10 SSD and later restore this backup on my other 10 HP Z4 identical systems... same HD configuration. I am hoping you would say ... well that is obviously one purpose for rescuezilla and yes that would work fine but if you could comment, I would appreciate it. Thanks... NEWBE
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The HP Z4 is a very recent machine which apparently contains a recent Nvidia graphics card: the Quadro RTX4000. Rescuezilla v2.0 will likely not boot to the graphical session on such a machine (task #115). Rescuezilla v2.1 (still a few weeks away) will provide improved support for such recent hardware. If your HP Z4 has onboard graphics, you might be able to boot into Rescuezilla v2.0's standard mode (and if that fails try the 'Graphical fallback mode' menu option).
If you are able to boot into Rescuezilla, you should be able to successfully make a backup of your Windows 10 SSD. This backup image should be able to be restored onto your other machines leaving their hard drives in identical state as your first disk.
The question is how Windows 10 activation reacts to this. Microsoft's OEM product key is inside your computer's BIOS. When Windows 10 reads this product key and contacts the Windows activation servers I am pretty sure it detects that all hardware is identical except for the hard drive and not subtract a license. Creating a single master backup image and deploying it to a large fleet of machines is a very common operation for IT system administrators.
(By the way, it might be useful to know that it's actually possible to broadcast a single backup image to a fleet of computers simultaneously. That means you can painstakingly configure just one of your computers and install all the applications you need, then broadcast that image to all your machines. I believe some IT system administrators choose the FOG Project to do this, but others use Clonezilla + DBRL. Rescuezilla v2.0 is fully compatible with the Clonezilla backup images format, but does not yet support restoring an image to a fleet of computers simultaneously using DBRL)
Last edit: Rescuezilla 2020-11-15
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
Anonymous
-
2020-11-15
Thank you Rescuezilla, thanks for the BTW however these other workstations wont be on the network .. essentially replacing workstations one at a time or as space allows. was thinking of using minitool partition with usb to sata connector as well but like rescuezilla option as well. anyhow the z4 comes with amd radeon pro graphics card but i suspect you indicated that as long as you can see the rescuezilla interface then the disk image should work fine. Thank you very much and will see about giving it a go.
👍
1
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I really feel awkward asking this but I would like to know if there would be any anticipated issues when using rescuezilla to create a backup from my HP Z4 Windows 10 SSD and later restore this backup on my other 10 HP Z4 identical systems... same HD configuration. I am hoping you would say ... well that is obviously one purpose for rescuezilla and yes that would work fine but if you could comment, I would appreciate it. Thanks... NEWBE
Hi Anonymous,
The HP Z4 is a very recent machine which apparently contains a recent Nvidia graphics card: the Quadro RTX4000. Rescuezilla v2.0 will likely not boot to the graphical session on such a machine (task #115). Rescuezilla v2.1 (still a few weeks away) will provide improved support for such recent hardware. If your HP Z4 has onboard graphics, you might be able to boot into Rescuezilla v2.0's standard mode (and if that fails try the 'Graphical fallback mode' menu option).
If you are able to boot into Rescuezilla, you should be able to successfully make a backup of your Windows 10 SSD. This backup image should be able to be restored onto your other machines leaving their hard drives in identical state as your first disk.
The question is how Windows 10 activation reacts to this. Microsoft's OEM product key is inside your computer's BIOS. When Windows 10 reads this product key and contacts the Windows activation servers I am pretty sure it detects that all hardware is identical except for the hard drive and not subtract a license. Creating a single master backup image and deploying it to a large fleet of machines is a very common operation for IT system administrators.
(By the way, it might be useful to know that it's actually possible to broadcast a single backup image to a fleet of computers simultaneously. That means you can painstakingly configure just one of your computers and install all the applications you need, then broadcast that image to all your machines. I believe some IT system administrators choose the FOG Project to do this, but others use Clonezilla + DBRL. Rescuezilla v2.0 is fully compatible with the Clonezilla backup images format, but does not yet support restoring an image to a fleet of computers simultaneously using DBRL)
Last edit: Rescuezilla 2020-11-15
Thank you Rescuezilla, thanks for the BTW however these other workstations wont be on the network .. essentially replacing workstations one at a time or as space allows. was thinking of using minitool partition with usb to sata connector as well but like rescuezilla option as well. anyhow the z4 comes with amd radeon pro graphics card but i suspect you indicated that as long as you can see the rescuezilla interface then the disk image should work fine. Thank you very much and will see about giving it a go.