@lcshelite said in Dell Latitude 5510 Won't Boot from Hard Drive After Imagine through UEFI:

WDS for so long I didn’t even think of that!

Yes that is really the difference between WDS/MDT and FOG. Where MDT does (dynamic) file based cloning and FOG does block layer cloning. MDT takes about 1.5 hours to image a single computer and FOG takes about 4 minutes to image a computer. There is no better technology over the other, it all depends on what the right fit is for the company.

If you are trying to image as many computers as fast as you can then use FOG. If you need a dynamically built image (i.e. able to change the image structure based on external variables) use MDS/WDS.

@george1421 tested with Hyper V 2. everything you said is correct and that is exactly whats happening.

We are assuming this is limitations on the host. Going to try to test with a physical machine.

@wertor I know it’s been a long time but have not found enough time to work on this earlier. We now have a first version of init.xz capable of capturing and deploying a Windows 10 2004 UEFI/GPT install with recovery partition at the end. Would you give that a try.

Please be aware this is still in kind of a pre-release phase. Make sure you have a backup of your original image as well as the machine you pull the master from, just in case!!

@scosta I know it’s been a long time but have not found enough time to work on this earlier. We now have a first version of init.xz capable of capturing and deploying a Windows 10 2004 UEFI/GPT install with recovery partition at the end. Would you give that a try.

Please be aware this is still in kind of a pre-release phase. Make sure you have a backup of your original image as well as the machine you pull the master from, just in case!!

@sebastian-roth I would be happy to give you a feedback if I have the opportunity to test your new init (I am an intern so opportunities do not arise all the time :))

@smoblikat If you get something worked out that might help others, please do tell.

Secondly for the apple computers that use the T2 chip I have a one off kernel that will boot on them so you can access the hard drives behind the T2 chip. Let me know and I will send you a link.

@infrapeya The quickest way is via the linux command prompt on the master FOG server.

If you are using a rhel based linux distribution then.

scp /var/www/html/fog/service/ipxe/bzImage* root@SN_IP:/var/www/html/fog/service/ipxe

i.e. scp /var/www/html/fog/service/ipxe/bzImage* root@192.168.20.40:/var/www/html/fog/service/ipxe

The debian/ubuntu versions are a bit more difficult.
Remote connect to the storage node using ssh (or putty from windows)

On the linux command prompt key in the following.

sudo su - scp <linux_user_on_master_fog>@<master_fog_ip>:/var/www/html/fog/service/ipxe/bzImage* /var/www/html/fog/service/ipxe

i.e. scp daffy@192.168.11.53:/var/www/html/fog/service/ipxe/bzImage* /var/www/html/fog/service/ipxe

@eseelke Are you still around?

I just updated the code to add the ${storage-ip} variable. Update to the latest dev-branch to be able to use it.

@djslimd1k Are you running into performance issues with this system?

If you look at top and sort by Processor what is your top task? mssql? Is it above 40%

How many fog clients do you have in your environment?

Lastly if you have the ram, you can increase the number of maximum handlers to 50 from 35. You may need to allocate 6GB of ram to the target computer. If you start dipping into swap space, then add more vRAM to the FOG server.

MOD Note: Topic of @DJslimD1k has been forked here: https://forums.fogproject.org/topic/14918/listing-all-hosts-gives-me-an-http-error-500

@tom-elliott Hello Tom,

Thank you for your quick response, I will try what you suggested and post my progress.

kind regards,

VlanFlex

@dadkins said in Can't perform Host Registration:

I have installed fog 1.5.9 on Ubuntu 16.04.

As you seem to be starting with a new installation I am wondering why you use such an old Ubuntu version. 16.04 is end of life kind of soon and newer versions work pretty much the same. I suggest you re-install before going ahead using Ubuntu 20.04.

@sebastian-roth That took care of the problem.

Thank you all.

@JJ-Fullmer We provide the PrinterManagerHelper with ever release of the fog-client, e.g. https://github.com/FOGProject/fog-client/releases/tag/0.12.0

I know it’s not perfect and sometimes doesn’t provide all the information correctly. Though I don’t have real printers in my test setup and can’t work on this part much.

@huecuva That is an interesting update for sure. I believe graphics cards have a bios of some sort and sometimes there’s some option rom boot option related to the gpu in the computer’s bios setting. It would make some sense for the graphics drivers to also update the bios or boot option roms on gpus.
What GPU’s do you have? GPU’s of the gtx 10xx series and newer have a ‘studio’ driver option that’s supposed to be the sort of ‘stable’ branch option. If your cards can use that, maybe using that as a standard could help if it’s not something you’re already doing?

@kdmiller45 Sounds as if the database update at the end of the capture task failed. Please run ls -al /images/dev/ on your FOG server and post output here.

Ok, let’s call it quits. I just pushed a commit to the fos repo to add this patch to our build of partclone and add the ignore_crc parameter back to the scripts.

Marking as solved.

@kdmiller45
https://wiki.fogproject.org/wiki/index.php?title=FOG_Client#Installing_-_Linux

@KenM I am sure it’s the fog-client trying to update but fails in every loop because of the run out code signing cert. Re-installing the new version should fix that.

@Pingolin It’s probably a good idea to follow the things George lined out. Just want to add one question: Did you say yes or no to the installer question “Would you like to use the FOG server for DHCP service”?

If yes was selected then we better take this DHCP offline again as it might mess with your home setup.