Thanks for the support.

Posts made by Tom Elliott
-
RE: Fog clients send inventory to wrong fog server
Usually the .php files are owned by apache or whatever the web service is owned by. If you gave root you can edit the files though.
-
RE: Looking for USB NIC that is known to work with PXE/Fog
Try this kernel:
[URL=‘https://mastacontrola.com/fogboot/kernel/bzImageALLNET’]https://mastacontrola.com/fogboot/kernel/[COLOR=#000000]bzImageALLNET[/COLOR][/URL]
[COLOR=#000000]It has all possible network drivers from USB and Network Drivers.[/COLOR]
[COLOR=#000000]Thank you,[/COLOR]
-
RE: PXE redirect via a menu.
If you know the kernel and the filesystem (init.gz) setup, it should be as easy as a menu entry that points to those areas. Other than that, it still uses 66 and/or 67 so the only way to use two pxe servers nicely is to keep redirecting that PXE systems when either or the other is needed.
-
RE: Looking for USB NIC that is known to work with PXE/Fog
I’m building a kernel will all networking devices enabled, including usb devices. I’ll post a link for it when it’s finished.
Thank you,
-
RE: Fog clients send inventory to wrong fog server
In redhat based systems:
/var/www/html/fogIn ubuntu based systems:
/var/www/fog -
RE: PXE redirect via a menu.
It just depends though. Why use two pxe servers? You already have the pxe server for FOG, and you know FOG already works, why not just insert the files/kernels that SCCM uses and create a menu entry? It would be a lot easier, and you’re not fighting for ports between two systems.
-
RE: Looking for USB NIC that is known to work with PXE/Fog
So it starts to try to do FOG stuff, but then fails out because the kernel has no driver for the NIC? What kind of driver does it require?
I’ll try to build a kernel for you that has it built in.
-
RE: Looking for USB NIC that is known to work with PXE/Fog
How do you mean it’s not working? Does using it get you to the PXE menu, or is it after that that FOG Cannot communicate with the network?
-
RE: PXE redirect via a menu.
You could chainload the system to point to the alternate PXE server, or you can just put the SCCM information onto your tftpboot folder and boot that way.
-
RE: Fog clients send inventory to wrong fog server
Okay,
I think, thru reading the title a little further, I figured out your saying it’s sending the inventory to the wrong server. Meaning you want the inventory to be kept on the local server not to your other server. Is this correct?
You’ll need to check the server there and make sure it’s SQL settings are pointing to the local system. This is done within the:
{fogwebdir}/commons/config.php file. You’ll also, possibly, need that change the /opt/fog/services/etc/config.php file as well.Make sure it points to the local server and has the credentials for that server.
Hopefully this helps.
Thanks,
-
RE: Fog clients send inventory to wrong fog server
I’m not sure this problem is worded properly?
You’re saying things aren’t working? If things aren’t what specifically is having a problem?
You state that things are sending inventory to your main office server, is this the expected operation or do you want your sister companies server to contain its inventory?
-
RE: Vostro 3500 Issues with new .32 version
If you need assistance with commands, let me know. I can be of assistance.
-
RE: Kernel Updates
As a caveat to the above, I’m going to make post here that gives all the selected options so others may see what they need added and/or removed for their setup’s.
-
Kernel Updates
All,
I just wanted everybody to know I’ve been trying to keep up with the kernel updates as they come out.
I thought it would be nice/good for everybody to know that they’re generally available at my website:
[url]https://mastacontrola.com/fogboot/kernel/bzImage[/url]
I’m also going to post my configuration file as it seems, to me, to work the best as it doesn’t try to operate around the video card. It’s based on Peter Sykes config file with a few inclusions for the proc system.
I’ll call this kernel (for lack of an original name) TomElliott.config
It can be download at:
[url]https://mastacontrola.com/fogboot/kernel/TomElliott.config[/url]
or from this forum.If you download from the forum, change the file name from TomElliott.txt to TomElliott.config
Or change the file directly in the kernel source directory to .config
Use it and please tell me how you feel about it. You can use the working copy by downloading or using the config to build your own.
I would like to know other’s mileage with it.
Thank you,
[url=“/_imported_xf_attachments/0/391_TomElliott.txt?:”]TomElliott.txt[/url]
-
RE: Custom init.gz
I’m posting my buildroot file to have others play, test, figure out, as well.
Hopefully it’s all good.
[URL=‘https://mastacontrola.com/buildroot2013.08_FOG.tar.bz2’]https://mastacontrola.com/buildroot-2013.08_FOG.tar.bz2[/URL]
-
RE: Computer Wont PXE-boot
It sounds like you installed the DHCP server on your fog server, and it’s not communicating properly because your router doesn’t know how to pass the information, to the tftp server. What kind of router are you using? Do you have the ability to setup something like:
dhcp-boot=pxelinux.0,fogstorage,192.168.XXX.XXX
or
next-server options,
or
DHCP 66/67 information?Could you try with a switch or hub connected directly to the fog server (bypassing the router) just to see if it can actually communicate with the FOG Server?
-
RE: Computer Wont PXE-boot
mlb2009,
Please provide more information in your posts.
So it never gives you a menu or is it like it can’t find a DHCP server?
-
RE: Computer Wont PXE-boot
So you’re trying to image the Macbook (Pro?) using PXE? You’re sure it’s already setup to boot from network and uses the PXE interface? Do you have any other machines (preferably not Apple) to test that the tftp server is working? FOG is not a service persay, it’s a suite of services. Part of the suite is tftp which gets installed. To make sure tftp service is restarted, the best method is to restart the entire server. All services on the server should should have been setup to be started on bootup so a restart is the best method to ensure the system is working properly.