IF you are using SVN it is located in your svn repository
trunk/FOGCrypt

As of revision 1556 it can be downloaded via the client page
<FOGSERVERIP>/fog/client/

Mitigation for vulnerabilities, includes Windows XP.

[url]http://steve.grc.com/2014/04/28/a-quick-mitigation-for-internet-explorers-new-0-day-vulnerability/[/url]

Thanks. I may try that. I just found out dnsmasq (which is already running on another box) has pxe support built in, I’m trying that right now since I’m having trouble installing fog.

[quote=“Tom Elliott, post: 26277, member: 7271”]This is correct. If you’re having issues with image uploads, the only place to worry about is the Storage Management Page->All Storage Nodes-><YOUR STORAGE NODE>->Management Username and Passowrd. These should be set to the fog user’s information on the FOG Server’s linux user data.[/quote]

I know this is a very common source of frustration among FOG users. Could it be an idea to have this explained somewhere on screen after installation/upgrade?

Set the fog user password in GUI Change unix fog user password (passwd fog in linux terminal) Set password (same as point 2) in Storage Management Set ftp password (same as point 2 and 3) in FOG settings

I guess some frustration is solved with such a reminder.

btsync Secret for read only access is: B7AGQ6JVIP4MF5LCRL3XURQBYC53UIS25

[quote=“TechieDJ, post: 25970, member: 23829”]Must be something on my end with the schools web filtering or something. Just pasting in the direct link you gave in the browser ( [url]https://mastacontrola.com/fogboot/kernel/Kernel.CentOSBase.3.14.1.64[/url] ) worked fine. The old published kernels work on the fog configuration page but the new ones get download failed erros filesize=0. And if I just browse straight to [url]https://mastacontrola.com/fogboot/kernel/[/url] I see the same unpublished list but the download icons are ‘pagebreaks’ like they didnt load and cliking them ( [url]https://mastacontrola.com/fogboot/kernel/?node=about&sub=kernel&file=aHR0cHM6Ly9tYXN0YWNvbnRyb2xhLmNvbS9mb2dib290L2tlcm5lbC9LZXJuZWwuQ2VudE9TQmFzZS4zLjE0LjEuNjQ=[/url] )loads the same list but no file. All is good though, thanks for the quick reply! Much appreciated![/quote]

The reason for the “PAGE Breaks” is going to the link directly will present the index.php I’ve created to do the checking of what files. However, it’s only relevant to the FOG GUi, so the …/images/kernel.png file doesn’t exist at the direct link

Tom’s latest install instructions, with a few options on how to do it: [url]http://fogproject.org/forum/threads/fog-0-33b-now-considered-release-candidate.10331/#post-25806[/url]

fog is designed around deployment. it’s not really made to be a backup solution.

My current setup is that each snapin is actually a batch file that calls a generically named installer package. That way I can copy over new packages to the server without having to rebuild snapins inside of FOG.

wow soooo many people/companies are reporting this is in their stuff. Nice job keeping up-to-date James

mastacontrola should be back up. I don’t know what caused it to go down.

There are multiple methods to “deploy” an image to.

The first, and most notorious method to deploy the image is to schedule the task through the FOG Web GUI. Simple login to the FOG GUI and choose the Host management page. Locate your host either by searching or from the list of hosts, select basic task and choose deploy, confirm and you’re set.

The second method is to perform, more or less, the same thing from the Task Page. On the task page, choose list of all hosts, or search for your host and click the down arrow to schedule the task.

The third method is to use a group to deploy the tasks. Using basically the same steps from the host management page, make sure your host is within the relevant group and deploy the task.

The last method, from the top of my head, is as you would like. From the PXE Menu, choose Quick Image. It will load into the the init file and request a username and password. Use the username and password you use to login to the FOG Web GUI. It should schedule the task and reboot the system. Once rebooted your task should begin.

Hope this helps.

Depending on the systems manufacturer, there may be a utility that you can run on the machines to change the BIOS boot settings from within windows.

I was wondering when I would be able to pull this out again:

[URL=‘http://www.albinoblacksheep.com/flash/posting’]An Educational Video on Forum Posting[/URL]

Yep just switched to:
[FONT=Ubuntu][COLOR=#555555]FOG_TFTP_PXE_KERNEL == [/COLOR][/FONT]bzImage32
[FONT=Ubuntu][COLOR=#555555]FOG_PXE_BOOT_IMAGE == [/COLOR][/FONT]init_32.xz

and worked without issue.

Update:
crap looks like r1439 has fixed this. With this update you no longer need to select the 32bit or 64bit image.

[quote=“buckITall, post: 25106, member: 101”]I am very much interested in this,
Is there a way to create subfolders in the pxe menu?
Such as:

System100-
W7x86
W7x64
W8x86
System 101-
Vista86x
Vista64x
W8.1x86[/quote]

[url]http://www.fogproject.org/wiki/index.php/Edit_PXE_menu_to_create_sub_menus[/url]

[quote=“Jaymes Driver, post: 25101, member: 3582”]Thanks for letting us know which option numbers to use on this hardware![/quote]
You’re very welcome!

Thank you for your help!!

sorry for not replying right away!

this is exactly what i’m looking for @afmrick