I would very much like to join the discussion on this. Please remember though that I am just simply a computer tech for a school district. I don’t have the background or knowledge on software development or programming or anything like that. My main goal is simply trying to install printers that are already created on our print server in our district. Previously we had Novell Zenworks, the printer management in that was pretty great. I don’t know how familiar you are with Zenworks, but we simply made a printer policy which basically made a policy that linked a printer on our print server to a machine. Everytime a user logged in it would install the printer if it was not already created for the user, since we made the printer policy for the device and not the user.

As mentioned in this thread, the printer is created in FOG and the printer is pushed out to the machine, but we also need it to remove the printer. In my case it is not removing. I would need to manually remove it. I have not had time to try on different models to see if it’s a model specific problem, but this is where I am at now. In the future I plan to try other models, but since this is not high priority right now, I have pushed printer management to the side.

On the bottom right corner on the dashboard it says Version 1.5.6.

Great point on flexibility @george1421, any idea on how to get the ipxe jumpstarters working? I have been using the USB to capture and deploy but I think I may need them eventually and it would be nice to use all features available if needed.

Thanks @Sebastian-Roth, changing those settings worked. The FOS USB works now. I was able to register and capture a test image from a laptop that does not have ethernet ports. I tested 3 different USB Ethernet dongles and they were all recognized. Saves me headaches of working on two different models of laptops numbering into the 200’s without ethernet ports.

Concerning the iPXE jumpstarters, I have the machines I tested on set to Legacy BIOS. Unless I am missing something, I do not see the reason why to use those now that the USB is working. As long as I can register a machine and capture/deploy now, I think that’s all I need. Right?

I created a FOS USB using a CentOS7 server running FOG 1.5.7 following the instructions provided here. I followed the steps specifically for CentOS7.

I can boot into the menu and upon selection it starts the process and then it errors out.


I also get these errors when I choose FOG iPXE Jumpstart BIOS or FOG iPXE Jumpstart EFI

Some guidance would be appreciated.

Thank you.

Very true. I submitted a request for a few more hdd. I wanted ssd but people in charge dont think they’re worth it for old machines.

Thanks again.

Just an update.

I did get another laptop and created an image with no issues. I also imaged the one that was giving me problems, and that seems to be working fine. No idea it was giving me problems on creating the image but if it works, it works.

Thank you for the reply. I am thinking it might be a bad hard drive. These laptops have been used and abused over the years, but I installed windows and software with no problems. I will have to grab another and see what happens.

I have an HP Probook 655 G2 Laptop that has data not being compressed when imaging. The original problem was that it was not PXE booting and was getting a no “No configuration methods succeeded” error. Researched this a bit and decided to try a USB BIOS boot. I got the usb boot working after some trial and error and can boot into FOG imaging.

The problem is when FOG is doing its preimage processes, I noticed that it is not shrinking partitions saying that the disk is a fixed size. FOG continues through the imaging process and gets to 100% then it errors out eventually ending with a message saying there’s not enough space on on server.

I used the same usb boot on another laptop and it created an image successfully. I have created multiple images from different models before, using PXE boot, and this is the first time I have had this issue.

Any help would be great. Thanks.

FOG version 1.5.7

Thanks for the information. Relieves some of my worries.

Just a general question, but has anyone ever had any problems imaging to or from SSDs using FOG? Also, is it possible to make an image from a standard spinning disk drive and then image to an SSD? And vice-versa? I have mini PCs from last year that have the spinning disk drives and we ordered same model machines for this coming year, but they have SSDs. Just wanted to know what the experience was like for someone who has gone through this.

Thanks

Yes, I’ll try to get to those. I am under a time crunch right now so I can not get to that right away.

I deployed the image that gave me the error after it was created, and it deployed successfully.