@Gary-Kulovics said in Fog Client won't join Domain:

9560

Invalid character in name.

@Gary-Kulovics said in Amount Fog can image:

Any answer on how to change at the main fog menu boot to hard drive from 5 seconds to a different time

Web Interface -> FOG Configuration -> iPXE Boot Menu -> Menu timeout

And, You never responded to me from your Multicast problem thread:
https://forums.fogproject.org/topic/8106/multicast

@larosejm I’d like you to start a new thread with this issue. This thread started with an older version of FOG. We need to capture your specific details as how you have fog setup and under what host OS (i.e. things that are specific to your setup).

@Gary-Kulovics at the end of the day, you have a much better environment with 1.3.0-rcX series FOG.

I always booted our Mac Minis with ipxe.efi. Just try different ones and see which one is working for you…

@Wayne-Workman I’ll try that out. As far as the browser thing. I tried this post on safari then firefox. neither let me post. only Chrome…

Thanks Guys got it up and running needed to turn on the boot stack in the bios.

@george1421 This is also true for Windows 8 and 8.1.

Thanks Fog is up and running again.

@Gary-Kulovics @cpattersonit

Sorry for not responding sooner.

Please turn off any firewall you have on the fog server (sudo ufw stop or systemctl stop firewalld) and try again. Clear the multicast tables per the troubleshooting guide and then restart FOGMulticastManager with either service restart FOGMulticastService or systemctl restart FOGMulticastManager and try again.

If you haven’t, please go through the troubleshooting guide posted earlier. If you’re still having problems, I can help around 4:30 PM CST via Team Viewer, please send me a message via the forums here.

@Tom-Elliott Thanks Tom You guys rock Love FOG and Thanks for getting back to me so fast Its all up and running

Update. It will all be fixed.

@Wayne-Workman Thanks that setting was already done But I had to change it at the host level and now it work Thanks everybody for there help Now have a bigger problem will open a new tread Again Thanks

@Gary-Kulovics

sudo mount 10.39.xxx.xxx:/images/ /images

The reason for the fstab error is because it didn’t have a place to be mounted to. (the /images part with out the colon)

If the argument isn’t setup properly, it scans for fstab to try automating mount point for you. If it can’t find it you get that error.

You can click on Fog Configuration icon across the top, it will, by default, show your version information when it loads. It will also tell you whether you are up to date.

Thanks ccmiens for link I now know the difference between the 2

Thanks
Gary🆒

I’m having the same problem on Ubuntu 12.04