Images not deploying to computers
-
This is a new FOG install that I created at the end of July, and these are the first systems to use it.
The original golden image is on a VM on the same Proxmox system, and that is what I have been able to deploy to all of the computers without issue.
I wasn’t using sysprep, because it’s on a VM, so I didn’t think it would matter.
However, all of that is currently a much smaller issue compared to the server not being able to boot properly. I’ve been getting the below image for quite some time now, and even had to rollback to a snapshot from 7/14 to get it working again last month.
I recaptured the golden image from the VM using the shutdown /s /t 0 command and left it to deploy to one of the Lenovo laptops. When I came in about an hour ago, it was giving me this message:
, which prompted me to check the site only to find out I couldn’t get to it. I got in via SSH and rebooted it, which resulted in this: 
which resulted in this: 
.And I’m sure all of this should go into a new thread, so just let me know if I should move it or not.
-
@gadams Looks like you found the corruption, it is in your fog server’s disk structure. Sounds like its time to start over.
-
So best to just delete the entire CentOS VM and start a new one?
-
@gadams I would say yes, since it will take less time to reinstall centos, update it and then install FOG than trying to fix what is broken and then repair the image files.
When you recreate your FOG server. Change your disk allocations manually because the centos installer will put all of the extra disk space in /home where you don’t need it. Instead change the mapping from /home to /images that way your images directory will be not on the same partition as the OS as well as giving it the most space on the disk. You will see what I mean if you option to manually partition the disk.
-
Thanks. This is what I followed to set everything up (making minor adjustments for my environment, of course) https://docs.google.com/presentation/d/1jaP_4r10OiILnNuIwe6uklsx7kcP4sEbnFz1H3eLH2o/edit#slide=id.p1. Is there something better I should look at?
-
@gadams Ok that is good, it is as I said to take away from home and give to /images. That guild will help you well.
-
From the latest pics in the post… The Fog server…
Seems hard drive related for sure. Problems mounting the file system and other issues related to the file system. -
Alright, now that I’m back in the office we can continue this madness. After doing a bit of searching online and prepping some computers at home for sale, I do see why I should use Sysprep on my base image so the SID isn’t duplicated to all of the computers it’s deployed to.
However I need to retain the admin and local user accounts that I’ve set up and I don’t want the computer to boot into OOBE or Audit Mode after the image is deployed. It might be outside the scope of this thread and/or forum, but is that possible?
-
@gadams Look into unattended installations (unattend.xml)
-
I had tried that originally when I started working with all of this. Either I wasn’t doing something correctly, or it’s not built that way, because I never could get it to enable the build-in administrator account. I still have the files if you want to take a look at them.
