Posts made by michaeloberg

@george1421 @Sebastian-Roth

Gentleman, with my OS - Ubuntu 16.04 having an End Of Life in April 2021, it may be best to build a new VM. My question to you is what is the best version to use when starting fresh? Debian 8? I want to start with the best foundation and also give me the best possible futureproofing of the OS as possible.

My second question is - After I build the new server, how do I export my old Hosts, Images and other information from the old FOG server onto the new one? When I build the new server, should I give it a new IP Address and change it after I power the old VM off or just point my 066 Boot Server Host Name to the new IP of the New Server?

Looking for best practices and to prevent leasons learned the hard way.

TIA,

Michael

@george1421 So not knowing much about Linux, can you update the current version of the OS, or is it a new server installation? This is a very large VM, 500 GB repository for image files. I am not against building a new one, but must admit it would be like walking a passenger through landing an airplane

TIA,

Michael

@sebastian-roth @george1421 I am sending the same reply to both, the version of the OS on my FOG server is Ubuntu 16.04.6 LTS

Sebastian - You mentioned “Something seems to be wrong with your git stuff on this FOG server” and I truly don’t know what that means. Is there something I can try to fix this, something to test this theory?

George - You asked about the version, which I provided above, regarding the debian variant, I am not sure what that means and building a command - don’t know how to do that either.

I apologize, I simply don’t know Linux well enough to intelligently respond to your questions. If you give me an exact command I can do that much to report the information back, that is about the extent of my abilities.

Thank you in advance!

Michael

@george1421 When I tried doing that, here is the error message that I get:

root@fog-server:~# ls
fogproject
root@fog-server:~# cd fogproject
root@fog-server:~/fogproject# ls
authors.txt lib packages rpttmp src utils
bin LICENSE README.md SELinux tmp
root@fog-server:~/fogproject# cd utils
root@fog-server:~/fogproject/utils# ls
FOGBackup FOGiPXE FOGUpdater
root@fog-server:~/fogproject/utils# cd FOGiPXE
root@fog-server:~/fogproject/utils/FOGiPXE# ls
buildipxe.sh ipxescript ipxescript10sec
root@fog-server:~/fogproject/utils/FOGiPXE# ./buildipxe.sh
Cloning into ‘/root/ipxe’…
fatal: unable to access ‘https://git.ipxe.org/ipxe.git/’: server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
./buildipxe.sh: line 22: cd: /root/ipxe/src/: No such file or directory
Copy (overwrite) iPXE headers and scripts…
cp: cannot create regular file ‘config/’: Not a directory
cp: cannot create regular file ‘config/’: Not a directory
cp: cannot create regular file ‘config/’: Not a directory
make: *** No rule to make target ‘bin/ipxe.iso’. Stop.
cp: cannot stat ‘bin/ipxe.iso’: No such file or directory
cp: cannot stat ‘bin/undionly.pxe’: No such file or directory
cp: cannot stat ‘bin/undionly.kpxe’: No such file or directory
cp: cannot stat ‘bin/undionly.kkpxe’: No such file or directory
cp: cannot stat ‘bin/ipxe.pxe’: No such file or directory
cp: cannot stat ‘bin/ipxe.kpxe’: No such file or directory
cp: cannot stat ‘bin/ipxe.kkpxe’: No such file or directory
cp: cannot stat ‘bin/intel.pxe’: No such file or directory
cp: cannot stat ‘bin/intel.kpxe’: No such file or directory
cp: cannot stat ‘bin/intel.kkpxe’: No such file or directory
cp: cannot stat ‘bin/realtek.pxe’: No such file or directory
cp: cannot stat ‘bin/realtek.kpxe’: No such file or directory
cp: cannot stat ‘bin/realtek.kkpxe’: No such file or directory
cp: cannot stat ‘bin/ipxe.lkrn’: No such file or directory
cp: cannot stat ‘bin/ipxe.usb’: No such file or directory
cp: cannot stat ‘bin/ipxe.lkrn’: No such file or directory
make: *** No rule to make target ‘bin/ipxe.iso’. Stop.
cp: cannot stat ‘bin/ipxe.iso’: No such file or directory
cp: cannot stat ‘bin/undionly.pxe’: No such file or directory
cp: cannot stat ‘bin/undionly.kpxe’: No such file or directory
cp: cannot stat ‘bin/undionly.kkpxe’: No such file or directory
cp: cannot stat ‘bin/ipxe.pxe’: No such file or directory
cp: cannot stat ‘bin/ipxe.kpxe’: No such file or directory
cp: cannot stat ‘bin/ipxe.kkpxe’: No such file or directory
cp: cannot stat ‘bin/intel.pxe’: No such file or directory
cp: cannot stat ‘bin/intel.kpxe’: No such file or directory
cp: cannot stat ‘bin/intel.kkpxe’: No such file or directory
cp: cannot stat ‘bin/realtek.pxe’: No such file or directory
cp: cannot stat ‘bin/realtek.kpxe’: No such file or directory
cp: cannot stat ‘bin/realtek.kkpxe’: No such file or directory
cp: cannot stat ‘bin/ipxe.lkrn’: No such file or directory
cp: cannot stat ‘bin/ipxe.usb’: No such file or directory
cp: cannot stat ‘bin/ipxe.lkrn’: No such file or directory
Cloning into ‘/root/ipxe-efi’…
fatal: unable to access ‘https://git.ipxe.org/ipxe.git/’: server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
./buildipxe.sh: line 59: cd: /root/ipxe-efi/src/: No such file or directory
Copy (overwrite) iPXE headers and scripts…
cp: cannot create regular file ‘config/’: Not a directory
cp: cannot create regular file ‘config/’: Not a directory
cp: cannot create regular file ‘config/’: Not a directory
make: *** No rule to make target ‘bin-i386-efi/snp.efi’. Stop.
cp: cannot stat ‘bin-i386-efi/snp.efi’: No such file or directory
cp: cannot stat ‘bin-i386-efi/snponly.efi’: No such file or directory
cp: cannot stat ‘bin-i386-efi/ipxe.efi’: No such file or directory
cp: cannot stat ‘bin-i386-efi/intel.efi’: No such file or directory
cp: cannot stat ‘bin-i386-efi/realtek.efi’: No such file or directory
cp: cannot stat ‘bin-x86_64-efi/snp.efi’: No such file or directory
cp: cannot stat ‘bin-x86_64-efi/snponly.efi’: No such file or directory
cp: cannot stat ‘bin-x86_64-efi/ipxe.efi’: No such file or directory
cp: cannot stat ‘bin-x86_64-efi/intel.efi’: No such file or directory
cp: cannot stat ‘bin-x86_64-efi/realtek.efi’: No such file or directory
make: *** No rule to make target ‘bin-i386-efi/snp.efi’. Stop.
cp: cannot stat ‘bin-i386-efi/snp.efi’: No such file or directory
cp: cannot stat ‘bin-i386-efi/snponly.efi’: No such file or directory
cp: cannot stat ‘bin-i386-efi/ipxe.efi’: No such file or directory
cp: cannot stat ‘bin-i386-efi/intel.efi’: No such file or directory
cp: cannot stat ‘bin-i386-efi/realtek.efi’: No such file or directory
cp: cannot stat ‘bin-x86_64-efi/snp.efi’: No such file or directory
cp: cannot stat ‘bin-x86_64-efi/snponly.efi’: No such file or directory
cp: cannot stat ‘bin-x86_64-efi/ipxe.efi’: No such file or directory
cp: cannot stat ‘bin-x86_64-efi/intel.efi’: No such file or directory
cp: cannot stat ‘bin-x86_64-efi/realtek.efi’: No such file or directory
root@fog-server:~/fogproject/utils/FOGiPXE#

@sebastian-roth Missed that - my bad…

@sebastian-roth I I missed the reference to the GUI interface, I can tell you this works on our new Dell 7420s, I don’t know if that helps but can tell you I am not sure how to do what you asked? - Check apache error???

@sebastian-roth Yes and I have that option enabled in the BIOS. The passthrough option is working in Windows as an Ipconfig /all show the system MAC and not the dongle MAC. The issue is only happening in the pre-boot environment.

@george1421 Thank you for the reply, I find myself in these situations nearly every time we get new hardware. I’m not a Linux person, I struggle with the most simple tasks and reading your reply leaves me, well like this:

I’m open to trying anything, our setup has been finicky in that what “should” happen for “normal” processes and commands - they don’t happen in our environment as they should.

What does rebuilding ipxe mean, how do I do that?

Again, full transparency, I know very little so please be patience and I thank you for your reply and future correspondence.

Michael

Hello,

I have 515 HP Probook 430 HP Laptops and they are not passing through the system MAC to FOG. I have the genuine HP dongles (part # 855474-001) and it passes the MAC through windows in a command prompt running an ipconfig /all but in FOG it pulls the MAC of the dongle. When I register the host, reboot it to image, it comes up saying that the host isn’t registered. Does anyone have experience with these units and the HP Dongles?

My Dell 7420s pass the MAC addresses through the docks fine and work fantastic, it’s just these HP Units.

Thank you,

Michael

@Sebastian-Roth Unknown, I should. I know in the past when I ran updates I had to download updates by typing in:
sudo apt-get update && apt-get install git

then something like

git checkout dev-branch

and it would download something from

https://github.com/FOGProject/fogproject.git/root/fogproject

This is from my notes when I updated the fog server in Feb. 2019. So these may not be entirely accurate but I know that it downloaded something??

I can also ping 8.8.8.8 from the FOG server. Lost I am

@Sebastian-Roth I was able to follow along until the line where I type the wget command, it comes back with “failed:Temporary failure in name resolution” Below is everything I had type in Putty:

root@fog-server:~# cd /var/www/html/fog/service/ipxe
root@fog-server:/var/www/html/fog/service/ipxe# mkdir backup_kernels
root@fog-server:/var/www/html/fog/service/ipxe# mv bzImage* backup_kernels
root@fog-server:/var/www/html/fog/service/ipxe# wget -O bzImage https://fogproject.org/kernels/Kernel.TomElliott.5.6.18.64
–2020-10-13 12:35:45-- https://fogproject.org/kernels/Kernel.TomElliott.5.6.18.64
Resolving fogproject.org (fogproject.org)… failed: Temporary failure in name resolution.
wget: unable to resolve host address ‘fogproject.org’

@george1421 I am such a novice at this I don’t know how/where to start. I downloaded the 2 files to my Windows 10 PC, and renamed them (watching the case) to my downloads folder. Then I putty into my FOG server, but am stuck. I am guessing I was supposed to download the files from my FOG server but don’t know how. Simple tasks like that - downloading files, moving, and renaming are difficult because I have no Linux knowledge. In the DOS world I can easily copy, rename, move, create, delete folders but the syntax is different and just a simple, type this “xyz” to download files, then type “abc” to navigate to your Kernel folder, then “qwe” to rename your old files, then whatever else would be helpful. I am sorry as this has to drive you mad working with people like me. I need to learn, I want to, but for lack of better excuses - I don’t have time.

Thanks,

Mike

@michaeloberg @george1421 My colleague figured out that we need to disable the MAC address pass through and now it is uploading I need to wait for this to finish then pull it down to have a valid test, but things are looking up for imaging at least. Still no progress on the Kernel update, is that needed?

@george1421 A bit puzzling this one is. I deleted the Host from FOG, then re-registered it using a different name: ST-3501. Then I created an image upload task for the Host, and rebooted - same thing “Host is not registered!”. So I rebooted and when I hit F12, Choose USB NIC (IPV4), then it states - "Start PXE over IPV4 on MAC: CC-48-3A-A9-6D-16. See attached:

But when I choose Client System Information from the FOG Boot menu it gives me a different MAC which matches the printed label on the WD19 Dock:

When I click on the Host name in the dashboard, the MAC it lists there is the MAC on both screens in the previous Pic.:

So I am not sure where that, I will call it “Booting MAC address of " CC-48-3A-A9-6D-16” is coming from and that might just be my problem?

Also regarding updating the Kernel, I don’t have an option to download anything. I don’t have proxy configured and not sure what to try next.

@george1421 said in Cannot find disk on system (getHardDisk) - Cannot reimage new hardware:

Also update your fos linux kernels. Be aware this has nothing to do with the FOG Host server but with FOS Linux. Goto FOG Configuration -> Kernel to update FOS Linux kernel.

Thank you kindly for the information regarding the HDD configuration in the system BIOS. After I changed the RAID setting to AHCI and reloaded Windows I was able to register the host - well sort of

I stepped through the process of “Perform Full Host Registration and Inventory” and can now find the host in my FOG Dashboard, but when I create a capture task for the image and reboot, F12, select IPV4 PXE, it comes back to the White screen and in RED states : Host is NOT registered! I don’t know if this makes a difference but I am using a Dell Thunderbolt dock with integrated NIC, the computer doesn’t have an RJ45 jack.

In addition to this, when I go to FOG Configuration-> Kernel Update
The right windows says “This section allows you to update the Linux kernel which is used to boot the client computers. In FOG, this kernel holds all the drivers for the client computer, so if you are unable to boot a client you may wish to update to a newer kernel which may have more drivers built in. This installation process may take a few minutes, as FOG will attempt to go out to the internet to get the requested Kernel, so if it seems like the process is hanging please be patient.”

I don’t see an option to update (button or instructions to fire off the process).

Attached is the screen capture of client screen where it states it is not registered, also a screen capture of the client in FOG, and finally a screen capture of the Kernel Update settings.

Hello,

I have some demo units that I am evaluating for new staff machines. They are Dell Lattitude 7410 2 in 1 computers. They don’t have a built in NIC, but I did purchase docking stations with them. I am able to change the DHCP Bootfile Name to ipxe.efi and get the machines to PXE to my FOG server. However, when I select “Perform Full Host Registration” it does it’s thing and reports back “Cannot find disk on system (getHardDisk)” then it reboots after 1 minute.

Some background, I know nothing about Linux and muck my way through this world with suggestions from this forum. I will try and include as much information as I can about what I am running:

In the GUI, under FOG Version Information it says (DefaultMember FOG Version: (1.5.7.2)

When I putty into my FOG server and run “uname --kernel-release --machine” I get “4.4.0-66-generic x86_64”

I seriously cannot tell you what that means, I believe when I set this up I installed Ubuntu and followed some regiment of commands to update the server during the time of installation.

I get new machines every 2nd and 3rd year on a rotation, meaning this is a year where I need to imagine new models. I need to get these units out for evaluation as soon as I can but need to make sure they work with FOG as I manage 1400 computers by myself, and yes that means reimaging them every year.

So please, call me a noob, novice, happy clicker or whatever it takes to get this user some help

Attached is the picture of my error message on the Dell Client machine.

@george1421 @Sebastian-Roth

Good morning gentleman,

Not sure if this helps but I did some experimenting this morning (Windows side of things).

After Sebastian installed dnsmasq onto my FOG server we disabled Option 66 Boot Server Host Name and Option 67 Bootfile Name on my Domain Controller that hands out DHCP. As Sebastian mentioned the legacy client fired right up and the UEFI boot client had the “Warning Boot Failure” error.

So below is the information I have and hopefully it makes sense.

When I disable option 66 & 67 on my DHCP server the Legacy client boots - UEFI client does not

When I leave option 66 & 67 on my DHCP server they both boot: Legacy boots off FOG - UEFI boots off my DHCP server with ipex.efi as my boot file in Option 67:

Beautiful - but not sure if this is how it is suppose to work (dnsmasq in conjunction with Windows DHCP)???

Again feedback appreciated and hopefully this didn’t add confusion. As of right now to the blind eye everything works - all computers, BIOS options, etc. Are further modifications needed or is it OK to run this way?

Thanks,

Michael

@Sebastian-Roth

@george1421 What a case of the Monday’s…

I found the section:
/* #define HAVE_LUASCRIPT /
/ #define HAVE_DBUS /
/ #define HAVE_IDN /
/ #define HAVE_CONNTRACK /
/ #define HAVE_DNSSEC */

And I put the cursor directly above the commented section but cannot figure out how to paste the following:

#define HAVE_DBUS
#define HAVE_IDN
#define HAVE_IDN_STATIC
#define HAVE_CONNTRACK
#define HAVE_DNSSEC

I tried to do a CTRL V and --INSERT-- showed up and I have no idea where it paste or even if it did. I am so lost…

Michael

@Sebastian-Roth OK did that, and get the following Error (I am assuming I choose Edit anyway, but want to be sure)