@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:
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:
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).
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.
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!
@sjensen Just as a precaution - make sure you have a backup copy of all your important data from this system. I won’t be made liable for any steps you take!
So let’s take a look at the whole process of resizing which involves several “layers” - see below.
In the output of pvscan we see that the physical volume on /dev/sda3 is 400 GB in size and has 100 GB free/not in use. So gparted has extended the partition but not the physical volume (in LVM terms). To do that run:
The next step is to tell the logical volume (LV) to use that new space:
lvextend -l+100%FREE /dev/FOGServer-vg/root
As a final step you need to extend the filesystem.
Finally check the partition size in the output of df -h.
As far as I know, if you use Big Sur Beta to create a machine, you don’t need to do any other specific settings.
If you don’t know much about it, you can take a look at this tutorial.
It will tell you what you need to do .
I did what it said before,the methods it provides are all helpful,i use method one, which is fast and simple, without me doing too many useless things.