Well, the time has come that I have to give up on v1.0.1.

Is it possible to downgrade back to v0.32? I REALLY need to fix these PXE boot issues since a LOT our computers are set to boot off the NIC as first boot priority.

-=Lon=-

I also got the repeating 0x040ee119 error after applying this fix. I assumed it would just keep repeating indefinitely, so I left it just to see. About 5 minutes later I walked over to the computer and luckly saw it just loading into the FOG menu, where I told it to do full inventory and registration. Then, I got the following errors:

[url=“/_imported_xf_attachments/0/772_FOG errors.JPG?:”]FOG errors.JPG[/url]

[quote=“marquinhoxd, post: 26788, member: 24088”]Hi! I am brazilian and my english is not very good. …
I’m with FOG 1.0.1 xenserver vm installed on CentOS 6.5 and PXE menu does not work, displays the following error: Error 0x040ee119
What should I do?

[IMG]http://i.imgur.com/M86eDsd.jpg[/IMG][/quote]

I am getting the exact same error Marquin. I have been running FOG for a long time now, but v1.0.1 has broken.

I have checked my DHCP settings to make sure everything was ok, and it is. Nothing changed on the settings and the DHCP logs show that the DHCP server is being contacted:

10,05/14/14,16:09:32,Assign,10.28.0.32,5C260A57E7D4,3571930892,0,

I am also still looking for the solution.

-=Lon=-

[quote=“Tom Elliott, post: 27067, member: 7271”]Good post, except he’s using FOG 1.0.0 rather than 0.32 or earlier. So the pxelinux.0 file is not accurate. Option 67 should be pointing at: undionly.kpxe, as it is.[/quote]

undionly.kpxe is the new filename that DHCP option 67 should point to now?

-=Lon=-

Thanks Tom, that got my Apache back online, but now I’ve gotta search for why I am getting an error on the Fog web management page now. “Unable to connect to database.”

-Lon=-

Hello,
I was running the Fog server update from 0.32 to 1.0.1 and everything seemed to be going ok. However, when it got to the section of the install where it was performing the Apache upgrade/install, it gave me an error saying that the Apache server failed to start with the following error:

“Setting up and starting Apache Web Server…Failed!”

I am very much a Linux n00b, so I really don’t have much of a clue how to troubleshoot Apache. Everything was working ok on v0.32, but now since the Apache web service is not started, I cannot hit the web interface of the Fog server any more.

I am running Ubuntu 12.04 LTS.

-=Lon=-

[quote=“chad-bisd, post: 7830, member: 18”]Are able to join computers to the domain and into the default “computers” container? If so, did you make sure the user account has been delegated rights to add/remove/manage computer accounts in the PISD Computers container?

I think you can put the OU in double quotes or escaped double quotes, such as “OU=PISD Computers”,DC=pisd,DC=us OR “OU=PISD Computers,DC=pisd,DC=us”[/quote]

Yes, FOG has been working fine for a while now, I was just changing the default OU for it to add new computers. FOG server would not save and text in that field that contained quotation marks, so I was thinking of trying \OU=PISD Computers,DC=pisd,DC=us and see what happens.

Did not work, but I supposed that could be related to the fact that the OU has a space in the name…

OU=PISD Computers,DC=pisd,DC=us

[quote=“chad-bisd, post: 5781, member: 18”]I believe so. Try it and report back. If it doesn’t work, have you checked the wiki yet?[/quote]

Yes, I looked through all the docs I could find online and could not find any reference to it. I will have to just try it and see if it works.

Hey y’all,

I want to try to change the default OU that computers join after imaging, but I can’t find a sample of what form the text needs to be in, in the box labeled AD_DEFAULT_OU in the FOG setup.

Do I use Active Directory notation such as OU=Sample,DC=domain,DC=com?

-=Lon=-