Or you can move those you don’t use too often to an external drive. I do that because my deployment machine is a laptop with an SSD.
The image info remains on the FOG database, so if you need the image again, just copy it back.
Best posts made by andreiv
RE: Strange size error during restore task
Unfortunately I saw you message too late. I re-imaged my FOG server so I cannot copy the files (I have a dual boot laptop as deployment machine and had some issues with Windows, so I had to re-image).
But I’ll test again and send you the files.
The OS is Windows but I am going to set up a dual boot in the next few days, that is why I chose Linux in the image settings (I wanted to use the same image).
But I think I know who is to blame for the problem: AOMEI Backupper. I had a backup made with it and restored it, checking the feature that aligns the partitions on SSDs. And I believe that messed up the size of the partition.
I’m going to work on this issue on Monday and let you know how it goes.
RE: Win 10 Clones NOT Unique On Network
Something is wrong with your sysprep settings and/or answer file (if you use one).
I used this same process many times and never had this issue:
Install windows on one system. During install, I created a temp account (without a password), to use for the setup process. Installed all the apps.
Ran sysprep and rebooted in audit mode. Deleted the temp account and ran sysprep again with a custom unattend.xml file. The system shuts down.
Capture the entire drive with FOG.
Deploy to clients. Worked perfectly.
The strange thing in your case is the MAC address. That is something set in the network interface itself, so it should be different by default. Unless you explicitly changed it in Windows, before capture. But even if you did that, sysprep should remove that setting.
Review your steps carefully, something is wrong there. Outline your steps in detail here, maybe I can spot the issue.