System Image Disappearing/Reappearing
-
I have an External HDD I use to capture and deploy system images for different computer builds throughout our facility.
One image I have is called STAFF. It's a Windows 7 (I know, we're working on it) image set up for GPT/UEFI build.
Anyhow, I recently added one more image for a Lenovo Laptop (Win 10). Let's call it LENOVOLAP. Not entirely sure of the boot config, but assume GPT/EUFI.
After I did this, the only image that would show while trying a new build from the repair disk associated with that STAFF image was another image that was setup with BIOS/MBR boot config, let's call that one LABS. I ended up deleting the new LENOVOLAP from the external and bam, the STAFF image showed again.
What causes this?
-
What imaging system are you using?
-
@DustinB3403 Backup and Restore>Create a System Image/Create a Repair Disk
-
So the windows built in solution? If so I've never looked at it so I can't tell you.
-
The only thing I can think of, which is most likely not correct, is that Windows reads the WindowsImageBackup folder alphabetically. That is to say since LABS comes before LENOVOLAP alphabetically, it hits the Windows 10 image in LENOVOLAP and then says "nope, everything else after this is null" and then doesn't even get to STAFF? I dunno man, it's weird.
-
@G-I-Jones said in System Image Disappearing/Reappearing:
The only thing I can think of, which is most likely not correct, is that Windows reads the WindowsImageBackup folder alphabetically. That is to say since LABS comes before LENOVOLAP alphabetically, it hits the Windows 10 image in LENOVOLAP and then says "nope, everything else after this is null" and then doesn't even get to STAFF? I dunno man, it's weird.
Yeah, it's a super basic tool, it's probably not expecting more than a single backup in the directory.
-
@Dashrender said in System Image Disappearing/Reappearing:
@G-I-Jones said in System Image Disappearing/Reappearing:
The only thing I can think of, which is most likely not correct, is that Windows reads the WindowsImageBackup folder alphabetically. That is to say since LABS comes before LENOVOLAP alphabetically, it hits the Windows 10 image in LENOVOLAP and then says "nope, everything else after this is null" and then doesn't even get to STAFF? I dunno man, it's weird.
Yeah, it's a super basic tool, it's probably not expecting more than a single backup in the directory.
^^ This sounds like what's happening.
If you're tied down to using an external drive and $0 tools, maybe consider using clonezilla or the Veeam's free windows agent. If you've got an afternoon and space for a linux VM (or even just a decommissioned desktop / server for a Proof of Concept test) take a look at FOG (https://fogproject.org/).
