@roseward Ok so we are going between models of computers. Also when you removed the network adapter and rediscovered it it still fails. So at this point I’m thinking windows driver. Because the same driver would be reinstalled. The network adapter is functional because you were able to image with FOG, so the hardware and network infrastructure probably can be ruled out on this issue.

So on this computer what network adapter is installed (version reported by windows)? Also get the vendor and hardware ID from the driver applet.

Also note the driver author and version (i.e. GigaByte Brix i7 LOM driver).

You may need to load a model specific driver because the one that windows detected may be close but not exact.

@blacksmile said in Failed to get an IP via DHCP:

I’m using FOG 1.4.4 on an isolated lan.
Any idea?

While I also recommend that you update fog to 1.5.7, if you can’t for whatever reason then at least update the FOS Linux kernel to 4.12.3 if your target computer has an Intel i219 style network adapter. You can get them from here: https://fogproject.org/kernels/

@tech49 said in Full Registration glitch, cannot type hostname for this computer.:

When I try to do a quick host registration and then select the host and prenamed image to be captured.

Registration allows deployment of an image, not capture.

For capture, issue a capture task for the now registered host in the WebUI.

@tech49 Please make a new thread for the new issue so we can help you there. (since it’s unrelated to the thread)

@Sebastian-Roth said in Fog installation and cofiguration on ubuntu 18.04:

You are welcome to open new topics for each question you have. It’s way easier for others having similar or same problems to find the right answer in a short topic instead of half a dozen questions being packed in one thread.

thanks,

I agree, i will start a seperate thread to update on any progress on this topic.

@processor In this case I’d ask you to update to the latest development version. There is a minor issue with 1.5.7 on Ubuntu and it’s better you use the latest version in case we still need to work on fixing the multicast issue.

sudo -i apt-get update apt-get install git git clone https://github.com/FOGProject/fogproject cd fogproject git checkout dev-branch cd bin ./installfog.sh

@lperoma The grep error can be ignored.

@EduardoTSeoane said in Common WebUI pages takes minutes to load.:

Ok, I’m ready to start the test, plz explain me how do you want the, bugs/problems report?

Just report here in the forums as you did before. Or if you are keen you could also post an issue on github. Whichever suites you best.

Knowing that my FOG server is in place, I mounted a drive to a nas in the / etc / fstab file.

8f9204b0-dd57-4792-ac3d-9ba399365321-image.png

it does not work … how to deport my storage without reinstalling FOG
thanks

@Pablo For your FOG server to get to the internet is a web proxy server required or does the fog server have direct internet access?

You can also use a windows computer and download these two files:
https://fogproject.org/kernels/Kernel.TomElliott.4.9.4.64
https://fogproject.org/kernels/Kernel.TomElliott.4.9.4.32

After download rename Kernel.TomElliott.4.9.4.64 to bzImage and Kernel.TomElliott.4.9.4.32 to bzImage32 Make sure you use the exact capitalization I used. Then move these files to the FOG server into the /var/www/html/fog/service/ipxe directory.

@Quazz
Thank you for your answer, I did not know that deployed partitions were prorated to captured partitions.
It’s clear for me now

@boomtown said in Interactive PXE Boot setting?:

Is it possible to require a key be pressed before the PXE image will boot so that if nothing is pressed the computer will go to the next device in the boot priority?

Unless I’m missing something here, this is the default. In the iPXE menu the default menu item is boot to the hard drive. If you don’t touch the keyboard during the timeout period the system will select the default menu item and boot the hard drive. You can change what the default iPXE menu item is, but as shipped from the developers, its the boot to hard drive menu.

Now if your target systems are Dells (only system I have) you can use the command and configure utility (i.e. CCTK) to change firmware settings. So you can from a running windows system change the boot order by calling cctk with the proper command line parameters.

@TBuzaTechnician Just a quick update here. I finally found the time to work on this. Currently we have a major set of changes regarding database security in a testing stage. Looks pretty good so far and it will all be part of the next release.

Just in case anyone finds this later, ended up using dnsmasq to make my configuration work using @george1421 's tutorial here: https://forums.fogproject.org/topic/12796/installing-dnsmasq-on-your-fog-server

Mine was a bit more complicated because I’m running an older version on ubuntu, but @george1421 's tutorial is spot once I got all the other weird things I had to do done lol.

Hello

This is a problem of config switch.
It’s a swtich Level3.

On one AC port works and not on the other.

I send you the config of its ports for info

Thank you for your help

@EricZ said in "Database connection unavailable":

I navigated to /Home/fogproject and ran the “git checkout dev-branch” and got “not a git repository” error message.

Then you are not using git source code but downloaded tar.gz/ZIP I suppose. While this isn’t wrong it’s just that you cannot switch between development and master branch as mentioned.

As well I am wondering if you are using the fogproject user to login? Don’t do that! It’s intended to be a service account and should not be used!

@Tom-Elliott Please ignore my previous post about this. I gave up on my current installation and reinstalled CentOS 8 and then tried to reinstall FOG again. I found a very useful Wiki article for CentOS7 and followed that. I posted a new issue elsewere in the forum so this particular problem no longer exists after a system re-install. I would post a new thread but I don’t know how. I don’t use forms much so I don’t know enough about them. To be honest, I wasn’t expecting folks to be so responsive on here (based on my previous experience with message boards) and I thank you for taking the time to reply.

@Tom-Elliott Thank you! I can confirm this fixed the issue. Snap-ins are deploying successfully and the tasks are clearing.

@Tom-Elliott said in Failure in Capturing an image:

@ismith-hpu But the machine, indeed, does have an OS on the disk? I can only assume the -a0 is a part of the problem. I don’t know what the argument is doing for the 0.3.12 version of partclone.

It’s to ensure compatibility with 0.2.89 images, allowing them to be deployed with 0.3.12.

0.2.89 had a broken checksum system, so we force it disabled on 0.3.12 in order to allow those images a normal deployment. It’s also faster and slightly smaller images, certainly not complaining about that part.

It is curious that 0.3.12 doesn’t seem to work in this instance, though I wonder if a non-resizable (not raw) capture has been tried?

@Daniel-Miller Thanks Daniel. They use puppet. I’ll shoot them an email.

Thanks again everyone for all the help.