Hello this is my first post because I am at completely out of my depth and this is driving me crazy. We have a computer running as a FOG server running Ubuntu. As far as I know the FOG server is running fine, but it is running version 1.5.7 and the kernel is 4.19.48. I know that the FOG server is out of date, but I don’t know if that is causing the issue or if it something I am doing. So the issue is that I have these Nexlink computers. They are old and not many left and the image that we have for them is over a year old now. I would like to update the image on the FOG server for them. I have free time and tired of wasting a bunch of time when I have to image one and apply a ton of Windows Updates. So I have 3 times now fully updated a NexLink computer and done a capture.
The steps I take to fully update the computer are:
- Fully update Windows 10
- Fully update Smart Notebook and drivers
- Update Java
- Disk cleanup delivery optimization files, Windows Update Cleanup, Windows upgrade log files, recycle bin, and system restore and shadow copies
- Remove any user profiles
- Add some specific shortcuts to the desktop: Word, This PC, and VLC player
For my capture I have the same options as the old image. They are:
- Operating System Windows 10
- Image Type Single Disk Resizable
- Partition Everything
- Image Enabled Checked
- Replicate? Checked
- Compression 6
- Partclone Gzip
I schedule the capture and restart the client Nexlink and the capture starts. The captures finishes and the container in the fog server shows that it is taking up this much storage and the date/time captured. The client Nexlink restarts and then it stops telling me to press DEL or F2 to enter BIOS and I can no longer use the machine with that hard drive plugged in. I can’t even access the BIOS by pressing DEL or F2. I can’t access the BIOS again, unless I replace the hard drive with a different one. This has happened to 4 different hard drives.
Lastly, here is what is driving me nuts. After the third try, I swapped out for another hard drive that had an older image on it. I did nothing to it and did the same steps to capture it. It captured just fine and I could still boot up the client Nexlink hard drive after the capture.
So its got to be what I am doing that is causing this, but what? Also are these hard drives completely unusable now?