Find a kernel that supports your video cards. Most of the kernels available through fog support multiple video chipsets. Sometimes the KitchenSink (KS) kernels work better. Use the Kernel updater portion of the WebUI to try different kernels until you find one that works best. If you are up to it, compile a custom kernel that supports your hardware. It’s a bit scary for a beginner, but after doing it once or twice, it gets a lot easier.

I’d search the forums for your particular problem(s). If don’t find anything, just post the particular issue here and someone will likely help. If it looks like a bug, or something you think the developers can help with, I’d post it in the bug section of the forum:

[url]http://fogproject.org/forum/forums/bug-reports.17/[/url]

I just put FOG onto a netbook that dual boots Ubuntu and Win7 and have the admin people at my small offices do reimaging.

As far as I know, there is currently nothing in Fog to set it up to have a structure like Active Directory. Fog cannot directly talk to active directory, but when the new UI comes out and allows easier creation of custom pages, it might be possible to add LDAP functionality to help achieve what you want, but it’s not in vanilla Fog.

I’m curious what you are trying to achieve overall by setting Fog up to mirror AD.

It’s just that the boot sequence is particularly verbose, it’s pretty normal to see a lot of warnings like that when you are using the default kernel from version 0.32.

Boooooo, I gotcha.

just done a quick test, after editing the MulticastTask.class.php my multicast speed was at 580-590/mb min. When set back to half duplex the multicast was at the normal (for this network) 670mb /min

Put clonezilla on a USB drive, and then make an image from your sysprepped image on FOG and store everything on the USB drive 🙂 Though, once FOG switches to Partclone, this should be easier.

I would use DNS to point the clients to the correct IP Address in that Network.

Not at this point in time.

Once 0.33 comes out, it will be much easier to add / modify / replace FOG code.

After this, i really want to encourge adding code to FOG. I more than willing to help.

[FONT=Tahoma][COLOR=#141414]My apologies to anyone trying to read this thread without having seen it first on the [URL=‘http://sourceforge.net/projects/freeghost/forums/forum/716418/topic/4719993’][COLOR=#555555]sourceforge forum[/COLOR][/URL], I was not aware how much the formatting was messed up.[/COLOR][/FONT]
[FONT=Tahoma][COLOR=#141414] [/COLOR][/FONT]
[FONT=Tahoma][COLOR=#141414]My first thought was something like “Great! Deeper AD integration will remove the hassle of setting everything up the first time, and might even be able to maintain things in an orderly fashion!” but I have a hard time believing anything like that would be easy to implement or work as smoothly as I would like.[/COLOR][/FONT]
[FONT=Tahoma][COLOR=#141414] [/COLOR][/FONT]
[FONT=Tahoma][COLOR=#141414]Some initial questions for this approach:[/COLOR][/FONT]
[LIST]
[]Would FOG do a scheduled pull from AD or would a manual import be simpler to maintain?
[]Would these groups be locked down in some way, or would users be able to add or remove hosts from a group built by AD?
[*]How would this play out in a host swap scenario since the new host wouldn’t be in the correct OU until it’s finished imaging?
[/LIST]

No. I haven’t thought about external authentication yet.

It’s something i want to support, but right now ive got other code to convert 🙂

I remember seeing that field and wondering why it wasn’t actually called anywhere… but my main focus was getting usernames listed under the Active Tasks page, and it seemed less terrible to just slap the currentUser onto the task name than to write a function to call a single field.

I cannot wait until this is up and working.

We need a documented kernel build process 🙂