@vince-villarreal Two other points.

You can build a usb boot drive with iPXE, but again that still relies on dhcp having the right settings to instruct ipxe on how to find the fog server.

You can also build a FOS usb boot disk, that will boot you right into FOS bypassing PXE altogether. But there are some caveats with this approach. If you can overlook the caveats and just want to capture and deploy (no multicast, no direct imaging from iPXE menus, etc) it will work for you.

One last comment, fog doesn’t like it when/if you change the IP address of the fog server once the FOG management console is installed. There are work arounds, but its best to have it at its assigned (forever) address when you install FOG.

Thanks for everyones help. I decided to try it on an actual device and add the -Wait at the end and that worked. @jflippen your way worked as well. For what ever reason my VM was would both say complete right after the start of script. When I attempted to run it on a physical PC it worked without any issues and completed with the delays.

make sure clients have boot rom enabled in the BIOS - otherwise they won’t boot at all.

in my environment :-
066 points to fog /tftp server
067 bootfile = undionly.kpxe

@hancocza I totally missunderstood this whole topic right from the start. It would have helped a lot of you’d clearly mentioned that you are using a custom SSL certificate. Might be obvious but I did not get it.

So what you describe here has nothing to do with FOG as far as I understand it. The password input stuff is something Ubuntu is doing when you start the apache webserver and you have a password protected private key. We as in the FOG installer does not add anything to that. So my guess is that Ubuntu changed things with one of the latest updates.

Probably you just need to install the correct extra package to make this work again…

@kratkale Ok, I finally got the time to get into fog-client development again. I am trying to answer your questions step by step.

About port naming: The field Printer Port is what you see in the Windows printing dialog as “Port name”. So if you put in 9100 it will be named 9100 but if you put in an IP the port will be named exactly as you want it. On the other hand if you want to specify a different TCP port for printing you put in x.x.x.x:9111 in the Printer IP field. I will change the field labels in the FOG web UI to make this clear.

Changing the printer setup on FOG changes sometimes nothing. (e.g. the name of the inf file - the printer …) My solution was to deploy the computer again …

I am not exactly sure if I get what you mean. Let’s see… If you change any of the settings in the FOG web UI while the fog-client is running on the computer the changes won’t be sent out to the client immediately. This is something I hope to change in the future but that’s how it is right now. But if you change things and then reboot the client machine it should use the changed settings!

-) Group management with Printers: If I update a group with the option “only Assigned Printers” the clients are not updated. The are still in the mode “No Printer Management”

This is a known issue I just fixed a couple of days ago. It will be in the next release!

-) How to install a local pdf Printer, when I use the option: “Only Assigned Printers”

Find out the settings used in the PDF printer (using the fog-client PrinterManagerHelper.exe or manually from the printer properties…) and set it up in FOG as well?! Should work I suppose.

@george1421, @Sebastian-Roth the only thing I foresee and maybe missed. Selinux won’t automatically be disabled because you made the change to the config file, it would require a reboot of the machine first. I would also, suggest changing from disabled to permissive. Disabling forces the file system to be unsupported and require being reestablished should you turn selinux back on. Placing into permissive mode keeps the file system contexts active and does not hinder usage. Plus you enter the command setenforcing 0 to switch selinux into permissive mode for the current running session which doesn’t require immediate reboot.

DERP — Don’t mind me, I’m dumb. Looked again and see you do have it set to permissive and do run the setenforce command.

@martial said:

USB\VID_0BDA&PID_8153…

Ok, we definitely have that driver included in our kernel config (since a long time). So I was wondering if other people had issues with Linux on this device. But seems like people are happily installing Linux on it despite some video card issues - see here. But no one complaining about network issues.

So I went hunting for those USB messages and read about USB hubs or other faulty USB hardware here and there, e.g.:

It seems the hub in the monitor went bad and was screwing with all other USB ports on the system

Maybe just some faulty hardware? Have you tried different ones. Always getting the exact same error on every try?

Then again I ask you for the third time (and last!), have you tried adding the Kernel Parameter has_usb_nic=1 to the host settings?? If this device is still unregistered and the error happens on registration you might just add the host manually via the web UI, add the parameter and try a capture task to see if that helps.

@Tom-Elliott Thank you for pointing this out, I feel that this solution has an immense potential and I am only scratching the surface of it. Kudos to you and @Fernando-Gietz for working on such a thourough product!

@coop90 Any update on this?

Sorry about the long intervals between posts. Just finishing up internal product training…

SO… I did as @Sebastian-Roth suggested and was able to successfully take an image and push it down on a blank VM! I have not tried putting the image back on the source VM but thought I would report back that I am successful and appear to be all set.

The take away from this is having 2 storage nodes on the same machine is not a great idea. If you run out of space, add a HDD and mount it /Images to add space.

Thank you @Sebastian-Roth and @george1421 for your help and guidance!

@Sebastian-Roth
Thank you so much, I missed it when you originally said that, running it with --exitFail didn’t work, however running it with -X did work. After this I was able to update/install the schema and actually log into the server via the web interface.

Additionally I tested booting to the server via PXE and was able too!

@Sebastian-Roth Thank you so much. You found the solution. The new password had an underscore ( _ ) as a chracter. I changed it and all is well again. Now I’m planning the upgrade to the latest FOG. Thanks again for your help. Alex

@Les https://wiki.fogproject.org/wiki/index.php/Troubleshoot_FTP

Please start there. Mind you this thread is very old and while the message you’re seeing may be similar, hence my posting to the wiki article, chances are your circumstances, version, file, etc… are vastly different. It’d be recommended to open a new thread.

@lschnider FWIW: Some people “need” to have it enabled because of internal security policies. That is why the developers came up with a list of required ports.

@Sebastian-Roth okay, thanks. I’ll do some research and see which route seems best. I still have a lot to learn about linux and wasn’t sure if there was a “new” way of adding storage to a FOG server since the wiki didn’t mention LVM and I was am not familiar with that yet.

@Sebastian-Roth So I went ahead and switched to dev-branch and upgrade nodes along with fog server. Seems like it’s working fine and the storage group info is now displayed. Thank you again for your help in this.

I Fixed it thanks for your Help guys.
First yes i needed the UEFI.
Than we uesed a Network bond on centos wich didnt worked so we del it and now it works fine 🙂

Thanks for the prompt response Sebastian, you guys rock!

I was able to resolve this by installing FOG 1.5.5 again after I fixed the TFTPD-HPA issue. You woulda thought I’d tried that already, but you’d be wrong, ugh. Anyway, please mark this as solved and thanks again, Sebastian.