I can say I have both the Extreme 12 (7204) and Extreme 14 (7404) on my campus and I’m running the 1.3.0-rcX series of FOG and both image properly. I have mine setup in legacy (bios) mode. They imaged with our standard Win7 build. You will need the newer kernels to support the intel nics as well as the NVMe disk (if that is in your model).
Posts made by george1421
-
RE: Rugged 5414
-
RE: Will it blend?
@wanderbread I agree the network route is probably the best solution as long as you have pxe booting capabilities on those network cards. Do check into see if veeam is XP compatible. It does work really well. It also has the ability to create a DR boot disk. So that if the harddisk dies, you replace the hard drive boot from the CD and then restore from the network. This will let you do a bare metal restore as long as you have the boot drive and network access to the backup repository.
-
RE: Invalid promptTime (Grace Period)
While I don’t use this function so I can only guess what it does (like a software install or a forced reboot?). I can suggest that the user be prompted to do what ever, the user should have the option to delay it up to the maximum the admin has set for the job. I.E. your computer must be rebooted. The user is notified every 10 minutes up to the 4 hours max the admin has set. When that time is reached the action is carried out and the user can’t stop it. That is typically how managed deployments work with the commercial applications. With most commercial applications the user is allowed to adjust when the nag messages appear up to the max dwell time then the job is forced.
-
RE: Invalid promptTime (Grace Period)
While I don’t have an answer for you, please post what version of fog you are running that will help set the scope of the issue correctly.
-
RE: PXE boot launches GRUB window if a usb flash drive is installed on the computer.
@JLE I can say I have almost 100% dells in my environment and I have sanboot as the global exit mode for bios. I do one offs in the host definition.
-
RE: PXE boot launches GRUB window if a usb flash drive is installed on the computer.
@JLE Sorry swamped with meeting today. But I have to ask the question, why are you using grub as a global exit mode? Typically you would pick sanboot or exit for bios systems.
-
RE: Will it blend?
If you are only concerned about a handful of systems and your only intention is to back them up, I might be inclined to use something like clonezilla running of a boot drive and then backup to a usb hard drive. That way you don’t need a fog server, or pxe booting to speak of. We use clonezilla (here) to make point in time backups of specific industrial computers, some have network adapters and some don’t. The clonezilla approach works well for this.
As for some kind of DR purposes, you can check to see if Veeam end point backup (free) will run on XP. If it does that is a great tool for making DR backups and then incremental backups on a timed interval. The Veeam endpoint can backup to a Veeam B&R server or just a network NAS.
Is FOG safe to use on your network, yes. Might I look for a different tool to do what you want, maybe yes. But with that said, fog will work for what you need.
-
RE: IPXE boot issue - Realtek RTL8153 - DELL VENUE - Resolved
@owlz89 If your dhcp server is a windows 2012 server then you have some options to make both bios (legacy) and uefi systems happy so you don’t need to mess with dhcp option 67 all the time: https://forums.fogproject.org/topic/4859/fog-bios-and-efi-coexistence
-
RE: FOG menu not showing up on some machines after DHCP server rebuild
@Jay-Bosworth for some reason your upload didn’t work as expected. Could you try again?
-
RE: IPXE boot issue - Realtek RTL8153 - DELL VENUE - Resolved
@owlz89 just to be clear when you say you have two vms (1.2.0, 1.3.0) you are only running one at a time?
OK so the venue is in legacy mode and it is booting into the FOG iPXE menu. That tells me that iPXE is having an issue with that nic. As a test instead of using undionly.kpxe, test to see how undionly.kkpxe or ipxe.kpxe responds to the boot attempt? There is also a specific realtek kernel realtek.kpxe. Sorry I can’t give you a definitive answer, but your system should just work in legacy mode.
-
RE: FOG menu not showing up on some machines after DHCP server rebuild
@Jay-Bosworth said in FOG menu not showing up on some machines after DHCP server rebuild:
…I freed up some pace on my boot partition, it didn’t make a difference.
Please reboot the fog server once the space is available, just to be sure.
-
RE: FOG menu not showing up on some machines after DHCP server rebuild
@Jay-Bosworth really the answer is to setup wireshark to capture the dhcp communications (for dhcp a mirrored port is not required as long as the dhcp server, target computer, and the wireshark computer are on the same subnet). The process is pretty simple start wireshark capturing, pxe boot the target computer, at the target computer error, stop wireshark recording. Then review the dhcp process in wireshark. If you get lost post the pcap here and we can take a look at it.
-
RE: FOG menu not showing up on some machines after DHCP server rebuild
@Jay-Bosworth said in FOG menu not showing up on some machines after DHCP server rebuild:
Let me add… FOG is on an Ubuntu 14.04.2 server. My boot partition is 235MB and 99.6% of it is being used. Is it possible that is causing the issue?
Thanks,
IF that is causing mysql to die then yes.
-
RE: Checksum kernel failed
I started to reply this (early AM for me) and discarded what I had once I saw the mountain of work ahead of you.
As for the yum repository stuff, you can follow these instructions to mount the centos dvd as a local repository: https://access.redhat.com/solutions/1355683
As Sebastian said, if you create a local web server to mimic the fogproject.org web site then you can maybe install FOG.
You will need these files in this local path
https://fogproject.org/inits/init.xz
https://fogproject.org/inits/init_32.xz
https://fogproject.org/inits/index.php
https://fogproject.org/kernels/bzImage
https://fogproject.org/kernels/bzImage32
https://fogproject.org/kernels/index.phpThe unknown is if the fog installer adds in any additional repos that you will need to install.
[edit] crud I just found that the fog installer is accessing files from the remi repo too. The mountain just got a bit higher. [/ edit]
-
RE: Hostname changing with Windows 10
FOG 1.2.0 and the legacy fog client does not support windows 10. You need the newer version of fog (1.3.0-rcX at the time of this post) and the new fog client (0.9.X or newer) for win10 support.
For sure you will need the 1.3.0 series for native FOG server support for uefi firmware, gpt disk format, NVMe disks, and Win10 support running on current hardware (i.e. latests FOS engine running linux 4.7).
-
RE: PXE boot launches GRUB window if a usb flash drive is installed on the computer.
For these computers, what is your FOG exit mode?
FOG does not use GRUB for booting at all. It uses iPXE to manage network booting. But I can understand that once the iPXE menu exits (because the default menu item in the iPXE menu is exit to hard drive), that if your default exit mode is grub first device then it might try to grub boot off the usb drive. Can you confirm this? FWIW: There is a default exit mode for both bios (legacy) and uefi systems. Lets make sure we know which exit mode is doing this.
Also can you confirm that you have the latest firmware update on those Dell systems?
-
RE: FOG menu not showing up on some machines after DHCP server rebuild
Well I would have to ask is there a reason why you don’t upgrade to FOG 1.3.0-rc8 (at the time of this post)?
The current version of FOG will give you access to the latest linux kernels for FOS, better support for uefi firmware, gpt and NVMe disks, and windows 10 support.
I understand there are certain reasons for not wanting to upgrade too.
It would be interesting to know if undionly.kpxe from 1.3.0-rc8 would give you different results. You can pick it up from here: https://github.com/FOGProject/fogproject/tree/dev-branch/packages/tftp Make sure you rename your original file. This file goes into /tftpboot on your FOG server.
If you are still running to stock kernel for 1.2.0 you might want to upgrade your kernel to 4.1.2 (the last version that worked with FOG 1.2.0) from here: https://sourceforge.net/projects/freeghost/files/KernelList/ Understand that 4.1.2 is over a year old here. So you won’t have access to the latest hardware. The current FOS engine kernel is 4.7.1 (as of today)
One last bit of detail since your dhcp server is running on a windows 2012 server. You can configure your dhcp server to post both undionly.kpxe for bios (legacy) system as well as ipxe.efi to uefi systems automatically. The instructions are given here: https://wiki.fogproject.org/wiki/index.php?title=BIOS_and_UEFI_Co-Existence
-
RE: Booting MDT 2013 LiteTouch with FOG
@kinger37 Thank you for reporting this.
To be honest it was only written and tested with bios (legacy) mode in mind. I’m going to suspect this is a uefi/memdisk issue. UEFI is a different critter so I suspect there might have some issues. Also I’d have to circle back to see if the MDT image supports uefi booting. Either way I should update the article to only indicate that legacy mode is required.
-
RE: IPXE boot issue - Realtek RTL8153 - DELL VENUE - Resolved
For now lets only consider the version of fog you updated to trunk. What version of fog did you upgrade to. The trunk version is a moving target. Currently the trunk is 1.3.0-rc8. Once you did that did you remember to change dhcp options 66 and 67 to point to your new fog server?
From there since you cloned your 1.2.0 vm, please confirm that the IP address in the file /tftpboot/defauly.ipxe points to your new FOG server. (It should but this is just a safety check. You an use the command
cat /tftpboot/default.ipxe
to view its content).What precisely do you have listed for dhcp option 67?
Is your Venue setup for bios (legacy) mode or uefi?
I can tell you those realtek nics are a PITA at times.
-
RE: Checksum kernel failed
@welcomyou Not at this time, the installer must connect to the internet to download the kernel, inits, fog client…
You have a bigger issue, the installer script also installs any needed system packages too. Its a bit more complete than copying all of the bits and then just running the installer and pointing it at a cache directory (something I discussed last week). If certain php modules are not installed the fog installer will reach out to your distribution’s package servers and download them.
What host OS are you installing FOG on?
@Developers can you think of any way to install FOG on a system that absolutely doesn’t have internet access?