So is your fog setup now installed?
If it is, what did you end up having to do?
If it isn’t, I’ll take a look at the 0.32 Redhat install portion to find out why it didn’t install for you.
Yes it is possible. If you know the kernel and the initrd (or iso) you’ll need, you just open up the /tftpboot/pxelinux.cfg/default file and create a new menu entry.
I don’t know all your info needed for SCCM so I’m sorry I can’t break it down any easier for you.
[quote=“mlnancejr8808, post: 15414, member: 654”]Yes, when the PCs boot to PXE initially they will try to pull DHCP go about 4 dots whatever you want to call them then say PXE-E51- DHCP or proxyDHCP offered…other PCs we have (Dell Optiplex 740 and 755) have no issue. Just dealing with this on the HP Compaq 6300 Pro and I have 6 labs to image by next Wednesday when school starts.[/quote]
Found this on website:
This error is usually received when the client booting up via PXE is having difficulty communicating with the DHCP/PXE server. The common troubleshooting steps and/or causes of this problem are as follows:
1-The PXE client is connected to a managed switch that does not have portfast enabled and/or is running spanning-tree. Portfast will need to be enabled. To read more about what spanning-tree and portfast are, see article 3096, “What is Spanning Tree? What is PortFast?”
2-The DHCP/PXE servers reside on a different subnet than the PXE client. IP helpers need to be in place. See article 1331, “Configuring PXE to work across VLANs.”
3-Check the DHCP server and verify that the DHCP scope has free IP addresses to lease out (make sure they are not all used up).
4-If the above steps do not correct the issue, place the DHCP Server, PXE server and a client computer on a hub. Test PXE to see if the same message is received. If the same error message is not received, this is a good indication that there is some factor on the network not permitting the DHCP/PXE protocols to be passed down to the client computer.
Place a hub between the PXE client and the switch the client is connecting to. If at this point the PXE client works successfully, please review step 1 of this article.
5-Use TCPView to verify the DHCP ports 67 and 68 ([URL=‘http://www.microsoft.com/technet/sysinternals/utilities/TcpView.mspx’][SIZE=12px][COLOR=#72a826]http://www.microsoft.com/technet/sysinternals/utilities/TcpView.mspx[/COLOR][/SIZE][/URL]). MTFTP Port 69 are showing.
6-If this problem is still occurring after testing out the above, collect sniffer traces from the DHCP/PXE server(s) and contact Altiris Support Services.
7-If DHCP server is on the same box as PXE server follow the option to enable 060 scope option. Article ID: 17347 Creating and setting option 060 on a DHCP server
8-The NIC could be disabled on the Client machine.[/COLOR][/FONT][/SIZE]
The images are pigz’d as they’re uploaded. I don’t know of fog writing to /tmp, it’s to /tmp/pigz1 during the upload process, but that’s a pigz process which is writing to /images which is the mount of the nfs share.
It sounds like an issue with drivers. I’ve heard of some having success with different kernels. I have a very small kernel that might just fit the bill. It can be downloaded at: [url]https://mastacontrola.com/fogboot/kernel/bzImage[/url]
I don’t know if it has all the drivers for your particular system, and if it doesn’t just let me know and I’ll build a specialized kernel for you. Just tell me what hardware (driver types) you need and I’ll make it happen.
On the server, how much memory do you have? If the loads are taking that long, it seems that something is eating the RAM and php is taking forever. Are you running php thru fcgi?
Try manually installing mysql with yum -y install mysql-server, it should install the package. Check that mysql is installed then, and you should find /var/lib/mysql folder. Another way to find out if it’s installed is to run:
chkconfig mysqld on; service mysqld start
Then, try your install. I’ll need to check the install folder for redhat to see that it’s pointing to the right package for mysql.