Posts made by Jarett LeBlang

I don’t advocate defeat but for situations like that i’d normally put a PCI nic in and flash it anyway, i have a Intel Pro 1000 GT just for situations like that.

I just ended up deleting the Startup Icon in my batchscript, thanks!

Bleh nevermind, this works but not terribly well for imaging, i get a Security Error after I attempt to log in to the imaged PC. Seems like that the domain join is done before the computer name change in the unattend.xml. Messing with this has gotten more complicated.

Just a quick post, i’m not knocking the Fog service but i don’t use any other function but the domain join and don’t need a needless systray icon, so i did a bit of digging and found a way to join the domain using unattend.xml while building my deployment images. The method is in this link:

[url]http://blog.unidesk.com/joining-windows-7-domain-using-unattendxml-and-mini-setup[/url]

The one thing i did differently is drop the MachineOU, it’s optional and after adding this to my image, it booted joined to the domain. I hope this helps people.

Edit: Just a quick edit, MachineOU is needed, although unattend.xml documentation says it’s optional, go figure.

I’m having the same issue with one of our computers onboard LAN, i’m just leaving the details just in case it helps. I’m going to throw a PCI NIC in it and Fog it anyway. Same 040ee119 error on iPxe, it does get an address at the start of the PXE boot. I’ve attempted to use the last undionly.kpxe which you posted four posts back but that just PXE boots, gets an address and when iPXE tries to run, it times out, i’m guessing and reboots the machine. I don’t get the 040ee119 error. The NIC is a Realtek PCIe GBE Famiily Controller on an Asus P8H61-M LXZ R2.0 Motherboard.

Ah i thought Global Settings were a general setting for newly registered hosts, so you didn’t have to manually go in and turn settings on. So basically Global Settings turns the module on and then you check what’s needed per host. You might want to think about putting a mechanism in place that lets you turn on the flags when the server is registered by pxe, rather than having to register the machine and then go into the GUI to turn on flags.

Nevermind, did a quick thread search.

I have a similar issue when trying to join a domain:

HostnameChanger Domain Error! (“unknown error” Code: 2202)

Have been trying to get my Fog server to do the domain join but i noticed that anything that got grandfathered over from .33 doesn’t seem to follow the Global Service settings. I had to go in and check services that are already in the Global Service settings area on a per-machine basis. I’m assuming this isn’t intentional?

Yes… yes… i’m dumb. Thanks. I didn’t realize that the config file got overwritten again.

[quote=“Tom Elliott, post: 27507, member: 7271”]Try updating to the latest on SVN. I’ve found a few bugs and have corrected them. The core of 1.0.1 is the same, but there were new tweaks and changes.

All you should have to do, as root on your system, is:
[code]svn co https://svn.code.sf.net/p/freeghost/code/trunk
cd trunk/bin
./installfog.sh[/code][/quote]

Ok i did the update to 1.0.1 and then attempted to do this to update to the newest SVN, Fog now wants to update the database again and is failing.

I love fog, no idea what we’d do without it. Did you mention the depreciation of pxelinux.0 in the wiki or documentation somewhere? I noticed it is renamed to .old and had to change my DHCP scope options to reflect the new undionly.kpxe.

This is fixed, built my own kernel using kitchensink and adding Atheros NIC to it. I’m able to add the host manually and flash.

That’s so funny. Got tired of my new Asus desktops with the Atheros chipset not flashing and built my kernel yesterday. Have yet to try it on the Pro desktops i have but the one laptop flashed fine.

Edit: The newly compiled kernel also allows flashing of the Asus Pro BP6320, which would kernel panic on the newest Fog kernel.

What a POS, it’s a nice tower but sadly, FOG freezes regardless of what bios setting i change. Turning on CSM, Legacy OProm, changing SATA from AHCI to IDE. I’ve even switched to UEFI, deleted all the keys and turned back to Legacy. I’ve tried everything but Fog starts the image and freezes at 3% every single time. I’m guessing it’s kernel related but every other tower on my bench has been able to flash. I’ve had two of these now and each are the same problem.

Not sure where this goes so here goes. I’m new to FOG… been figuring things out on Ubuntu 11.04 and pretty much have it down (i think). I can successfully image and deploy but i’ve noticed that some MAC addresses when i put in new hosts are invalid. I don’t know how this part of FOG works but i’m fairly sure they’re valid, just not on some list somewhere so Fog doesn’t know of them. Is this something that gets updated? I’ve found the Other Information -> Mac Address Listing - > Update Current Listing button and have used it to no avail. Is this just a stagnant old list that needs updating?