@sbenson No, we don’t use Avahi/LLMNR in FOG. The FOG installer does not set this up so I suppose you installed/configured it on the server manually?!
Best posts made by Sebastian Roth
-
RE: Avahi/LLMNR required?
-
RE: How to shutdown the machine automatically when deployment is complete
@samuel You can set a kernel parameter in the iPXE menu options to make machines shut down on deploy (or other tasks). Go to the FOG web UI -> FOG Configuration -> FOG Settings -> General Settings and add
shutdown=1
to the field FOG_KERNEL_ARGS. -
RE: Slow UI response and cannot update kernel
@Scott-Adams Tom just pushed a fix a couple of minutes ago… Can you please update and see!
-
RE: Trying to capture Ubuntu 18.04.1 and I get this.
@salted_cashews Sorry for my late reply.
Is it possible this is the result of mounting everything on one partition?
I don’t think this can cause the issue. Trying to read up on this I found a bug report that kind of sounds like what you see: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1778140
Although I am still unsure if this can happen with the pre-resize test we do. But can you confirm you are installing on LVM? If unsure run
df -h
on your Ubuntu system and post output here.EDIT: Reading a bit more I found another hint on there being an issue with resize2fs. Again this is on LVM but maybe it can happen on plain partitioning as well. This points us to a second launchpad bug report.
Would you mind trying to install Ubuntu without LVM and see if that fixes it. Although the patch was added to the official e2progs source in October 2018 it has not made it into buildroot which we use for FOG yet (as of now, last e2fsprogs update was in early 2018).
Which install ISO did you use? Desktop or Alternative installer? Just asking so I would setup the same test scenario…
-
RE: No shortcut on desktop after spaning
@Fredorum We need more infos to be able to help. What software do you install? Have you tried installing this software manually (as well using the exact same parameters)? Do you get the desktop icon if doing it manually?
The fog-client runs as SYSTEM service account. This might cause the installer to act different to what you might expect. It might be easier to just create the desktop icon within a batch script that you run as snapin.
-
RE: kernel update problem github 7238 ubuntu 14.04
@MaMu Tom just pushed a fix a couple of minutes ago… Can you please update and see!
-
RE: Copy PXE files from FOG to NAS(QNAP TS-463U)
@sysadmin Just re-run the installer. We made it so you can run it over and over and it should fix all the things for you.
Sometimes when you run it a second time after it didn’t run through all the way it fails on
Backing up database
. If so, take a look at the other log file inerror_logs
and post the last 20 lines here. -
RE: MSI vs SmartInstaller
@Scott-B While Daniel’s answer is perfectly right I might just add that technically the SmartInstaller has the MSI packed into it and simply uses
msiexec
on Windows system to install. For Linux und MacOS it uses it’s own install routines. -
RE: PXE boot fails on fresh install - CentOS 7 (Build 7218)
@moses Tom just pushed a fix a couple of minutes ago… Can you please update and see!
-
RE: Resize only root partition
@docorange6 Easy way on deploy is to edit
d1.fixed_size_partitions
file in the/images/<IMAGENAME>
directory on your FOG server. Put in the partitions that you want to have fixed in size (and sector start position) separated by colon, e.g.1:2
Don’t think we ought to expand SWAP partitions but maybe there is an issue in the scripts. Can you please post the contents of
d1.partitions
,d1.minimum.partitions
andd1.fixed_size_partitions
of your Linux images. -
RE: FOG 1.5.7 - Join W10 Clients to Domain?
@JRA said in FOG 1.5.7 - Join W10 Clients to Domain?:
what I’m reading there doesn’t seem to correspond to what I’m seeing on the screen in the FOG Web UI.
Which guide? What do you see on the screen? You need to share more information for us to be able to help.
-
RE: Cannot enter fog management screen after localized install
@cemicolin Any errors in /var/log/apache2/error.log when you try the web interface URL…?
-
RE: Getting error: Either DHCP failed or we were unable to access...
@paravane Is the IP address of the FOG server 10.223.254.110? Just want to make sure.
Is the switch a managed one? Is spanning tree enabled? See if you can connect FOG server and client using an unmanaged dumb mini switch that doesn’t do spanning tree at all.
-
RE: FOG 1.5.7 - Join W10 Clients to Domain?
@JRA said in FOG 1.5.7 - Join W10 Clients to Domain?:
Is there any other guide or walkthrough for the process?
I don’t know of a full walk through on this. We keep asking people to help improve the FOG documentation but there seems to be very little enthusiasm from experienced users to work on this.
The AD stuff in the FOG settings page is just the global defaults. What you want to look at is the host’s settings directly. Use one of those as an example to try out and get to understand how it works. Install the fog-client software on this host and make sure communication to the FOG server works correctly (log file on the client host in
C:\fog.log
orC:\Program Files (x86)\FOG\fog.log
). Then add AD settings to this host and check the “Service Settings” tab on this host as well. The “Hostname Changer” needs to be enabled.Keep an eye on the log file on the client to see what’s going on.
-
RE: Fail to connect disk error
@Kaix Then please open the following URL in your browser and post the full output here: http://192.168.1.171/fog/service/ipxe/boot.php?mac=d0:50:99:95:90:86
-
RE: TFTP won't start at the installation
@Onirix Seems like I have missed the important bits last time. From the messages you posted I think you have disabled IPv6 in Debian completely. While this is totally fine if you don’t want to have it enabled it’s not standard and therefore we have not run into it with our tests yet.
Yes adding
-4
to theTFTP_OPTIONS
should fix this - see here. But as soon as you re-run the installer it will generate a new/etc/default/tftpd-hpa
for you and overwrite your change.Note that the default file the installer generates looks like this:
# FOG Modified version TFTP_USERNAME="root" TFTP_DIRECTORY="/tftpboot" TFTP_ADDRESS=":69" TFTP_OPTIONS="-s"
So if you want to keep IPv6 disabled I would suggest you run the installer like this:
./installfog.sh -X
- this way it should still go ahead even if it fails to start TFTP in the first place. Then when the installer is finished you can modify/etc/default/tftpd-hpa
, manually start TFTP and go ahead. -
RE: Client does not want to update from 11.6 to 12.0
@Jurgen-Goedbloed I had a look through the code and I am fairly sure this is caused by the old code signing cert has lost validity on the 7th of September 2020. This cert is only used to ensure the binaries are certified by the FOG project team. We updated the code signing cert in January 2020 and released FOG 1.5.8 together with fog-client 0.11.19.
Unfortunately I kind of lost sight of this “major” change that would affect auto-updating after 7th of September 2020 and never officially announced that people should update earlier for the auto-update to work.
So from the version number we see in your log file I am sure you updated from FOG 1.5.7 to 1.5.9 - skipping the fog-client update that introduced the new code signing cert. This would have worked perfectly fine while the old code signing cert was still valid but fails now.
You’ll need to update all your fog-client installations to 0.11.19 (auto-update to 0.12.0 will work from there) or 0.12.0 through some other kind of software deployment mechanism I am afraid.
For now you should manually edit
/var/www/html/fog/lib/fog/system.class.php
and setFOG_CLIENT_VERSION
back to0.11.16
or clients will keep downloading the SmartInstaller.exe binary over and over again and put load on your FOG server for no reason. The code is smart enough to handle a situation where you haveFOG_CLIENT_VERSION
set to0.11.16
version but the fog-client on some or all of your machines is on 0.12.0 already. So don’t worry about this. -
RE: DHCP failed booting to the PXE
@saif said:
…when i try to boot “some” of the Dell or HP computers…
Do I get this right? Some PCs work but others don’t with your PXE setup?? Please provide picture(s) of the error(s) you see on screen.
-
RE: TFTP error on server
@idiart33 As well please post the contents of your
/etc/default/tftpd-hpa
. I have a feeling that there is a miss-configuration in that. -
RE: Prevent Windows 10 to change itself UEFI BIOS boot order after deploying
@nockdown We have had a few reports of this behaviour in the past. FOG does not touch the UEFI entries nor the boot order. Seems like some UEFI firmware is trying to be smart - changing boot order and sometimes even adding of entries automatically. Not much we can to about this in FOG, I am afraid.