Posts made by noelpd

Server

• FOG Version: 1.30 RC-11
• OS: CentOS 7

Client

• Service Version: N/A
• OS: Windows 7 Professional

Description

I am working on getting our new G3 HP Laptops inventoried. We are currently using the undionly.kpxe file for our DHCP Server. The G3 will get to the fog menu and let me select “Full Inventory”. However after that, I get a “No DHCP Response on interface eth0”. I read that switching to ipxe.kpxe is more compatible than undionly.kpxe. Anyone experience this or have a reccomended file to be using for the DHCP Boot? Thank you!!

Greetings Everyone!!

So the current issue I am having with 1.30 RC-8 is Sysprep is failing. I am currently troubleshooting to see if it is the sysprep package itself OR if its a FOG issue. Here is pretty much what happens…

1. Push our “pure” or “base” image down to a workstation. Everything works great.
2. Make changes (install programs, client, etc for particular site)
3. Upload New image
4. Push down customized image to new workstation
5. After deployment, the sysprep package stops running and needs to be manually continued.

I understand this may be hard to troubleshoot as everyone has their own environments and setups, but any help or suggestions would be greatly appreciated. Thank you.

Our Current Setup: CentOS 7 with FOG 1.30 RC-8

@Wayne-Workman Thank you!! That modification worked.

Greetings all,

I am running into an issue where I cannot access the web page interface for fog properly. I have a clean install of CentOS 7 and stable version 1.20. When attempting to access it via IP Only, I get the Index page. From there I can click on fog and the web interface will load.

However, If i type in the full address of “ip-address/fog/management” it works perfectly fine. Any ideas would be greatly appreciated. I have narrowed it down to being an issue with Apache or the naming or maybe a symbolic link issue somewhere, just not 100% sure where to make the changes at. Thank you!

In our district we have many fog servers. In some of our recent servers we deployed they are not working to schedule tasks. If we manually do it, it works fine. If we try to schedule the tasks at a particular time they do not work. I have dug through a few forums and including this one and the only outcome I can find that seems to be a strong difference between our working FOG servers and non-working is the OS they are on. The working FOG Servers are on Fedora 13 and the non working servers are on Fedora 15. Would that be the difference? Does FOG have issues in relation to that version of Fedora?

[quote=“madeyem, post: 13083, member: 797”]Just in case you don’t know this:

You can choose which kernel to use for every host separately. Just copy all the kernels (in your case that would be 2) you need to the FOG server (/tftfboot/fog/kernel). Under “Host Management” click on the hosts, that don’t work with the default kernel (in your case the Acer laptops). Under “Host Kernel” include the path to the alternative kernel (in your case 2.6.37).[/quote]

Yeah, I was aware of that but when the laptops are not registered yet it is just kind of a pain to switch the kernel, register all of them and then switch it back. But so far that seems to be the only way to do it. Has anyone came across away to build the Kernel so that it includes other drivers then whats already available to check within the menuconfig?

Greetings Everyone,

So at our school district we have been using fog for some time now. As time goes on we (as I am sure most are) are getting a greater amount of different hardware types involved in the mix. We can use the 3.10.1 kernel and everything works fine except for these new Acer laptops we got (Acer Aspire One 722). I noticed the 2.6.37 Core Kernel works but that Kernel kills the ability to register our desktops (Dell) with add on video cards.

Is there a way to have the 2.6.37 Core Kernel but add to that Kernel the ability to support the on board video card for our Dell Desktops so we can hope to avoid the switching back and forth method of Kernels? Any help would be greatly appreciated. Thank you.