Perfect. That’s exactly what I needed! Pretty sure I missed the step to change the framework to 2.0. Everything else I’ve done, so that makes sense. Thanks again Chad!

[quote=“astrouga, post: 4790, member: 907”]I’ve updated the link again. This is the original 3.4 kernel I created a month or so back:

[url]http://www.filedropper.com/bzimage34[/url]

click on the “Download This File” image link after the “URL:” and “Embed:” text boxes.

astrouga[/quote]

Hey,

I don’t suppose you could upload the 3.4 Kitchen Sink Kernel to a filehost that doesn’t charge you to download could you?

Thanks
Dan

try compatibility check option or debug mode. See if you can get more info on where it’s failing.

Yeah. I didn’t realize choakem had resurrected a 7 month old thread. Thanks for updating the WIKI though!

Yeah, I’ve technically got my kernel edited to include the SCSI drivers, but I agree - it would’ve been easier to just switch to IDE before loading the OS.

don’t delete image. just upload over the old one

monkey see, monkey do.

Follow the instructions for modifying the init and the pxe menu. It’s basically a copy + paste, change the mode to whatever you want to call the new mode. Then go into the init file, modify the fog script to recognize your new mode, do what you need it to do, which is basically hard code the answers for OS/Image and removed all questions except for the name.

If you are afraid of tanking your production fog server, then use virtualbox/vmware to setup a new fog server and client and you can do that there.

The great thing about open source and free software is you paid nothing to get it and can modify it to meet your unique needs.

I don’t really understand the question. Were you multicasting with Ghost and looking for similar with FOG?

We have found that with the d4 mac address it never finishes but replacing the motherboard that had the 18 mac addresses it finished with 5-15 minutes. So no issues have d4 mac addresses.

Man I hate batch script some days. I actually got it working with my .bat file.

I had to use set vmvar=VMWare%% (double for the escape)
and then use SELECT * FROM inventory WHERE iSysman NOT LIKE ‘%vmvar%’;

Batch must’ve been trying to do something with the % originally, but once I had it placed in a variable it knew not to touch it. What a headache. >_<

Thanks for the help! I’ll have to look into php sometime when I’m not on a bit of a time crunch.

I don’t think there is, but I can’t answer for sure. I guess you can browse/download and scan the svn repository on sourceforge looking for malicious code. FOG is developed by mainly by 3 or 4 people working together remotely and usually on different parts of the project.

Since it’s open source and freely available via svn on sourceforge, it’s up to the user. Besides, fog is mainly a bunch of scripts and web pages that just use existing application packages available to multiple distributions of Linux (dhcpd, tftpd-hpa, vsftp, mysql, php, apache2, and others).

I’ve got a working set of steps for Windows 7 in VMWare as of just a few days ago. I’ll work on updating the wiki when I get a chance (first I’ll have to figure out how to edit a wiki… haha)

Sounds like you got this locked down to a problem that only happens to the HP 6000 sff when multicasting right? You’re unicast seems slow also. I average 3.5 GiB/min and you are only seeing 800-900 MiB/min.

Post a spec sheet of the HW and maybe we can compile a custom kernel to try.

this was indeed the culprit! thank you very very much, saved me a big headache! 😄

For the life of me, I cannot figure out why these image drops keeping timing out on the second partition. I’ve even tried a single partition Win7 that I created, still no go. Too many days trying to sort this all out, has to be a better way…

It should only show N/A or hide the column if its not a single partition. Just a suggestion.

If you have recovery partitions which were created by the OEM, then they can cause problems. If you are imaging computers with FOG, you don’t want the recovery partition in most cases. You can’t easily remove it because they try to make it idiot proof and allowing users to delete the recovery partition makes it useless.

I have a bunch of Fujitsu laptops that shipped with the recovery partition and rather than reload Windows 7 from scratch, I used a USB flash drive with GParted to remove the recovery partition and resize/rearrange the rest.

The hostnamechanger performs double duty. It renames the client and joins it to the domain if requested. Also, if a host is a member of the domain and you change the host record, the hostnamechange has to deal with AD to change the host name.