Same experience here. On [B]Windows XP[/B] I used only the [B]username[/B] but on [B]Windows 7[/B] I had to use [B]domain\username[/B]

I’ve noticed that some changes I make under Group Management do go back to not configured as you describe BUT it does get applied to every host in that group if you look in the settings for each host in that group under Host Management. In those cases, it’s just mildly annoying or misleading but at least the settings do apply.

I think that it’s trying to create a partition the same size as the original even if the partition isn’t full.

That’s usually caused by setting a mysql password during FOG installation. See [url]http://fogproject.org/forum/threads/unable-to-connect-to-database.475/[/url] (or do a forum search)

To summarize, you need both [SIZE=4][B][FONT=monospace][COLOR=#003399]/opt/fog/service/etc/config.php[/COLOR][/FONT][/B][/SIZE]and [SIZE=4][B][FONT=monospace][COLOR=#003399]/var/www/fog/commons/config.php [/COLOR][/FONT][/B][/SIZE]to have the correct authentication information (see [SIZE=4][B][FONT=monospace][COLOR=#336600]MYSQL_USERNAME[/COLOR][/FONT][/B][/SIZE][SIZE=4][B][FONT=monospace][COLOR=#003399] [/COLOR][/FONT][/B][/SIZE]and [SIZE=4][B][FONT=monospace][COLOR=#336600]MYSQL_PASSWORD[/COLOR][/FONT][/B][/SIZE]) for your mysql server.

Dunno, but this might get you started:
[url]http://www.fogproject.org/wiki/index.php?title=Building_a_Custom_Kernel[/url]

You can download a bunch of different kernels from [url]http://sourceforge.net/projects/freeghost/files/Kernels/[/url] as well. Just save one to [SIZE=4][B][FONT=monospace][COLOR=#003399]/tftpboot/fog/kernel/bzImage[/COLOR][/FONT][/B][/SIZE] on your FOG server to give it a try.

You could go the easy/lame way and just install OCS on the FOG server and then modify the FOG gui to have links for each server into OCS …we did something like that at one job.

I’m pretty sure that you can save over existing images FWIW. I usually create a new one just so that the old one is still available at least until the upload is complete.

There’s hosts.hostCreateDate or inventory.iCreateDate to see creation dates but, I’m not seeing anything about the last time the FOG client checked in …maybe you could infer it from userTracking.utDateTime?

I’m sorry if I am misunderstanding your post but, you set the boot device and order in the BIOS not from windows.

Yeah, the FOG log on the client (C:/fog.log by default) would probably tell you why the client was rebooting the computer. You can also check if forcerestart=1 in C:\Program Files\FOG\etc\config.ini.

Reboot options can be set several ways in the FOG manager too:

[B]Auto logoff[/B]
[LIST]
[][B]FOG Configuration > Auto Log Out[/B] or
[][B]Other Information > FOG Settings > FOG Service - Auto Log Off[/B] or
[*][B]Group Management > [I]myGroup[/I] > Service Settings[/B]
[/LIST]
Remember that “Auto logoff” reboots the client computers after it times out.

[B]Task reboot[/B]
[LIST]
[][B]FOG Configuration > Task Reboot[/B] or
[][B]Other Information > FOG Settings > FOG_SERVICE_TASKREBOOT_ENABLED > 1[/B] or
[][B]Group Management > [I]myGroup[/I] > Service Settings[/B]
[/LIST]
[B]Shutdown/Reboot[/B]
[LIST]
[][B]FOG Configuration > Green FOG[/B] (Only if no user is logged in) or
[*][B]Group Management > [I]myGroup[/I] > Service Settings[/B]
[/LIST]

Just for fun, I cancelled a multicast deployment from FOG. Everything appeared to function as it should from the FOG manager but the clients kept pulling down the image until they were all done.

Clients also do this for unicast but, that doesn’t surprise me - the FOG manager is largely out of the picture at that point but, you’d think that the FOG server would stop spitting out multicast data when cancelled.

Any thoughts?

I think the default value for Config.php --> UPDSENDER_MAXWAIT was null. I assumed that meant, “wait forever”. We changed it to 600 seconds because we’d rather get most of them done instead of none.

There’s a couple threads on booting from ISO’s …here’s two:
[url]http://fogproject.org/forum/threads/integrating-iso-hirens-boot-cd-into-fog.219/[/url]
[url]http://fogproject.org/forum/threads/how-to-modify-the-pxe-boot-menu-to-allow-the-booting-of-iso-files.154/[/url]

I’ve read some ISO’s don’t play nice with this but, it’s relatively painless to give it a try. Remember that when using memdisk there has to be enough memory to load the whole ISO.

I haven’t tried this but, you can wipe the drive from the FOG Manager via [B]Task Manager -> [/B][I]myHost[/I][B] -> Advanced -> [Fast|Normal|Full] Wipe[/B] …but, that ain’t quite the same thing. You might be able to format by booting into Debug mode.

If you defined a mysql password add it to [SIZE=4][FONT=Times][COLOR=#000000][B][COLOR=#003399]/opt/fog/service/etc/config.php[/COLOR][/B] and [B][COLOR=#003399]/var/www/fog/commons/config.php[/COLOR][/B][/COLOR][/FONT][/SIZE]

Yahoo!

Sorry for all the posts - just trying to keep the thread updated.

Apparently, [B]Auto Log Out[/B] reboots the computer by design:
[QUOTE][COLOR=#000000][FONT=sans-serif]This module of the FOG Service will log a user off of a client pc after X minutes of inactivity. This module will display a screen saver-like GUI after 3/4 of the inactive time is up. So if the time out value is 40 minutes, the GUI will be displayed at 30 minutes of inactivity. [B]When the time is up, the client computer will reboot[/B].[/FONT][/COLOR][/QUOTE]
[url]http://www.fogproject.org/wiki/index.php?title=Managing_FOG#Functions_and_Operation[/url]

FWIW, they were pretty close based on my search criteria. FOG got the bump for the post-imaging support (FOG client, snap-ins, etc.) and the generally prettier/easier to use web interface (which is good for us for a variety of reasons).