@seppim said in Ubuntu 20.04 Desktop live:

http://archive.ubuntu.com/ubuntu/dists/eoan/main/installer-amd64/current/images/netboot/netboot.tar.gz

Thank you Ubuntu… Try this link: http://archive.ubuntu.com/ubuntu/dists/focal/main/installer-amd64/current/legacy-images/netboot/

Ubuntu 19.10 has been removed from existence so the previous links are now broken.

@sebastian-roth Hi Sebastian,

thank you!

Well, the 3 partitions are because of the Ubuntu software Raid.

I need the Raid to prevent system halt, because the server is not local monitoring. so no one will check if the HDD goes failed.

I finish my setup and try to capture … as long he copy 1:1 the HDD for the backup its fine

@sebastian-roth

I wish you and your familie a happy and healthy new year.

I wanted to say thank you for your time.

best regards

Enrico

@tom-elliott Thanks very much!! That fixed it!

I found the path to the password to that user from another post I’ll copy here in case someone else runs into this problem.

Find the database information in /var/www/html/fog/lib/fog/config.class.php - with FOG 1.5.9 the database user is called fogmaster instead of root that was used in earlier versions.

@matthew73 This is a unique condition. I can understand what is going on because we use NAC and VLAN switching on my campus. I can say that I have not seen this issue (anywhere) on my campus.

I think I understand what needs to happen. Basically iPXE needs to say something and then wait XX seconds for your NAC system to identify the hardware and to switch it to the right vlan. The network link light winking happens 2 times during a normal pxe booting. The first time is when the PXE turns over control of the network adapter to iPXE and then when iPXE turns over control of the network adapter to FOS Linux. We see a similar issue when the network switches are using standard spanning tree and not one of the fast protocols (RSTP,MSTP, port-fast).

The developers have created a specific group of iPXE boot loaders that have an embedded 10 second delay before iPXE tries to request an IP address. This gives STP and powersaver functions on the switch a chance to react before iPXE starts to talk. These files are in the 10secdelay folder. So to use these update dhcp option from ipxe.efi to 10secdelay/ipxe.efi This will call in the 10 second delay boot loader. See if that makes things better or not.

I’ve added some more steps that should avoid those errors.

I’ve updated the chown command in the wiki. The user fogproject is something that came about after this article was written. The user used to be just fog

@george1421

Hi George,

That’s exactly what im looking for! Thanks, this would work for me. When we get hardware on our departmend i connect always mostley one kind of machine, so that works for me.

thank you for your great help and quik respons. Im gonna build further with this in a few weeks, and now it is a lot easier.

gr

Paul

@kdmiller45 The fog-client software will do the activation for you if it’s all setup correctly.

@george1421 Great, thank you for the quick response.

@emreonder Please post the contents of the fog-client log file here.

Hostname changing on Linux systems is not as straight forward as it is on Windows. The fog-client will try to change different config files (code reference) though this might not always work.

On Linux you can usually take another route and set hostname via DHCP. Search the forums and the web in how to do this.

@emreonder I thought you have Windows DHCP server in your network. Well if the FOG server is actually providing IPs as the main DHCP server in your network you should not shutdown the server/service as clients would not get an IP via DHCP even when booting Windows.

If this is really true (you don’t have another DHCP server) then I would suggest you comment the line “next-server 10.1.11.4;” by putting a # at the start of this line, like this:

... # next-server 10.1.11.4; ...

Save the config and restart the server.

@emreonder said in Need to install Fog Server. Urgent remote support needed.:

nomater all the options i try with the Host Bios Exit Type or Host EFI Exit Type ( i guess i tried all the combinations) but never passes this step.

Ok the first thing we need to know is the gigabyte mobo in bios or uefi mode. Knowing that then you can focus on the right Host Exit type.

The default for bios exit type is SANBOOT. That works 95% of the time. For the UEFI exit type that is typically rEFInd.

So if you have a uefi type firmware and rEFInd hangs on exit there are a few things you can try with refind to make it work. The first thing I think I would have you do is update a few settings in the refind.conf file to see if adjust refind to locate your boot media.

@Oleg I hope you can read patch/diff information. Here are the changes you need to make to /var/www/html/fog/lib/pages/hostmanagementpage.class.php to add the “System Product” column to the host list output - this is for FOG 1.5.9 and would probably work in 1.5.8 just as well:

--- fogproject-master/packages/web/lib/pages/hostmanagementpage.class.php 2020-09-14 01:00:12.000000000 +0200 +++ /var/www/html/fog/lib/pages/hostmanagementpage.class.php 2020-12-19 17:03:24.225580767 +0100 @@ -175,7 +175,8 @@ _('Host'), _('Imaged'), _('Task'), - _('Assigned Image') + _('Assigned Image'), + _('System Product') ); $this->templates = array( '<i class="icon fa fa-question hand"></i>', @@ -223,7 +224,9 @@ _('Goto task list') ), '<small><a href="?node=image&sub=edit&id=${image_id}">' - . '${image_name}</a></small>' + . '${image_name}</a></small>', + '${inventory}' + ); unset($up, $down, $mc); $this->attributes = array( @@ -259,6 +262,9 @@ ), array( 'width' => 20 + ), + array( + 'width' => 120 ) ); /** @@ -281,6 +287,7 @@ 'image_id' => $Host->imageID, 'image_name' => $Host->imagename, 'pingstatus' => $Host->pingstatus, + 'inventory' => $Host->inventory->sysproduct, ); unset($Host); };

I suggest you keep a copy of this information somewhere so you can apply the changes whenever you update to a new version of FOG.

@sebastian-roth Yes resolved.

@DJslimD1k Yes there are two ways of achieving this. The first one is kind of static where you modify the init.xz file. You need to re-do the modification as soon as you update to a new version of FOG. Find instructions on how to do that in the wiki: https://wiki.fogproject.org/wiki/index.php?title=Modifying_the_Init_Image

But as you seem to use the latest dev-branch version (great!) I would suggest you use the more dynamic way of “patching” the inits on the fly while it boots up. George posted instructions on this in the forums: https://forums.fogproject.org/topic/13500/dynamically-patching-fos-using-a-postinit-script

In your case you want to edit fog.reg.man.fix and delete lines 286-294 as well as 250-268 (note I am listing the lines numbers in reverse because when you start deleting in line 250 the later line numbers will change).

As well I suggest you keep an eye on the commit history of this particular file on github (https://github.com/FOGProject/fos/commits/master/Buildroot/board/FOG/FOS/rootfs_overlay/bin/fog.man.reg) - whenever we commit a change I suggest you re-download and modify your fog.reg.man.fix again. Last change was March 2018, so changes to this file are kind of rare but you never know.

@boriquaboy115 I would like to say yes for LUKS encryption. I created a one off kernel for that a while ago for a specific use case.

Part 2: LVM isn’t a problem for FOG, it just can’t resize the disk image, so you can only deploy it to the same size disk or larger if you have an LVM partition.

ref: https://forums.fogproject.org/topic/13845/error-decrypting-luks-partition-prior-to-capture-imaging/8

Found the answer:

The master server polls the storage node web server. (/fog/status/bandwidth.php?dev=eth-device-name)

If the master server is HTTPS enabled, the storage nodes must expose the APIs in HTTPS too.

Hi, I have solved the problem. I have followed an article which has helped me to solve the problem I had, right now FOG is able to answer both networks without any problem.

I leave the article here: https://jensd.be/468/linux/two-network-cards-rp_filter

Thanks for everything!

@bmick10 said in Deleting Hosts:

If I delete a device that is still in production on the network. It will not remove from domain or lose connection?

Correct. The only impact to the target computer is that if the fog client is installed on the target computer it will no longer get instructions from the FOG server. The FOG Client will be abandoned with no instructions.

If I have a machine named ittech20 and remove that from database when I restart in pxe will the computer still be named ittech20.

Yes the computer will remain untouched. The only thing you will notice is that in the fog iPXE menu the computer will appear as unregistered.

So if I delete all of them since the machine still has service running on will it talk back to server and sync to database?

If the FOG Client is installed on the machine but they are no longer in the database the FOG Client should reregister the computer. Now that I think about it. BUT they will be registered in a pending state and must be approved before you can work with them in the FOG Gui. Its been a while since I did this part so its not as clear in my mind. But they should go into the database again in a pending state.

@george1421 Thanks for your reply.

Out of all the replies on updating FOG all of them refer to the git method, and never a clear answer on the tarball/zip method. So thank you for that. Looks like my original install my boss did was from the tarball so I’ll stick to that for now. Thanks again!