This seems to be happening more often lately than in the past. If you post the same or very similar question in multiple forums, it doesn’t increase your chances of getting help. It just increase the chance of annoying those that are most likely able to help.

Most of the forum community that regularly respond to help requests use the “What’s New?” link near the top of the forums. We see your post no matter what forum you put it in.

TL DR: Don’t cross post, or [B]kittens[/B] will die. Save the kittens.

If you can still log into mysql, you probably need to fix the password record for the fog user. I think it’s a simple update statement:
[CODE]
use fog;
update users set uPass = MD5(“password”) where uName = “fog”;
[/CODE]

then you can login to the webUI again using username = fog and password = password

[CODE]6/27/2013 11:17 AM FOG::HostnameChanger Domain Error! (‘Unknown Error’ Code: 87)[/CODE]

Always use the code tags when posting logs or code to keep the board from eating it and pooping out smilies.

Double check the information used for AD joining that is stored in the global FOG settings against the information that is stored in the Active Directory page for the particular host. Make sure they match, with the global FOG settings winning out over the host Active Directory settings if there is a difference.

Also, you might look through the Wikipedia/Wikimedia tutorial on editing articles and using Transclusion to reduce data duplication. I think that’s still what they call it. We really need a wikipedia team of super documenting super heroes!

One of the things we need to do in the wiki is figure out which versions of FOG each article applies to and include that in the information, maybe as a category. Many times people get to looking through the wiki for info, and get confused or frustrated because the procedure is not valid for their version.

I you are using host specific kernel settings, that will work for any tasks you setup through the WebUI in FOG, but will not work for tasks selected from the PXE boot menu. If you have a gmail account, I can share my kernel with you. Just PM me your email.

I have been really busy with back-to-school. Haven’t had a chance to create wiki accounts. I believe I am the only mod that does it right now. I’ll get them hammered out and PM you the info as I create them.

Megabyte, go ahead and start your own thread and post your question including what version of windows and FOG you are using. I’ll be happy to help you get it working with AD if I can.

DNSMasq is the package. It requires you to change a few pathways in the FOG setup and add an IP helper/relay to your router config if you have FOG clients on different subnets/vlans than your FOG server.

I have no experience with FOG above 0.32 right now. So I can’t really help but with general knowledge and suggestions.

Mine always looks like this
[ATTACH=full]1205[/ATTACH]

[url=“/_imported_xf_attachments/1/1205_Screen Shot 2014-07-24 at 9.34.33 AM.png?:”]Screen Shot 2014-07-24 at 9.34.33 AM.png[/url]

What is running in VMWare? the FOG server or the client or both? Maybe a VMware hardware version upgrade/change could have affected this. Sometimes VM’s are set to upgrade HW on the next boot cycle.

I have 2 models of machines (out of about 20 different models) that will not PXE boot if the DHCP server is not the same machine as the PXE server. When we used Windows DHCP and FOG for PXE, these machines would not PXE boot. Research with WireShark showed that they failed to receive blocks 2 through N of the pxelinux.0 file.

My solution was to implement a ProxyDHCP server on FOG, wherein FOG now listens for DHCP requests as well, and lets Windows DHCP give IP info, but responds to the clients with the PXE boot information. I modified my FOG server slightly and added an additional DHCP relay/DHCP helper to my main switch that handles VLAN traffic routing.

If any of this sounds like what you need, I’ll be glad to help you as much as I can.

You can try to use the WEB ui to upgrade the kernel. Or you can download a new bzImage to another folder. backup your original, and then overwrite the bzImage file in /tftpboot/fog/kernel with the new one. You may have to chown/chmod.