That should do just fine… this is an old guide and this is the one I used when creating my kernels.

[url]http://fogproject.org/forum/threads/request-for-kernel-compiling-info-please-read.4045/#post-12320[/url]

[quote=“NDNtech, post: 33256, member: 23658”]:( I’ve tried to avoid this for as long as I can. lol Can this only be done on a Linux machine?[/quote]
yes, it’s fairly simple to do, it just takes some time figuring out which drivers need to be included, Tom’s kernels tend to be all inclusive, and this can cause some load time issues.

I’ve built a kernel or two in the past, just make sure you keep back ups of the working kernels… don’t ask why <.<

[quote=“NDNtech, post: 33253, member: 23658”]But this doesn’t solve my long withstanding problem of why bzimage takes forever to load up on the client I’m trying to image.[/quote]

This could be due to the drivers that are included in the bzImage, if you are feeling up to the task, you can always create your own bzImage that includes ONLY the drivers you need, this will increase the speed in which bzimage is loaded.

[quote=“Der Baron, post: 33245, member: 25074”]Having the same issue, have you figured anything out Chris?[/quote]

Did you try the reported fix by updating to the latest SVN?

Change the settings in your FOG web GUI.

You will want to change the Exit type listed under the FOG Configuration->FOG Settings->FOG Boot Settings->FOG_BOOT_EXIT_TYPE.

[quote=“fre2709, post: 33240, member: 24947”]Thanks X23,

i had already discovered this on another forum entry.

One thing to note, and I dont know if this normal. After applying the SVN the version number in the “FOG cloud” symbol changes. Mine now says 2052. This breaks the latest version reporter because it now says my version is out of dat and I need to install 1.1.2!![/quote]

This is okay, the SVN is considered “bleeding edge” it’s where all the new fixes are worked on, you can consider it an “active beta” for a lack of better way to describe it.

FOG Is set up so that it will check to see what the latest reported version is so it can determine if there is an upgrade for you, however, it doesn’t have the ability to distinguish being “up-to-date” and being on the “bleeding edge”. So this error is only a minor cosmetic detail. When we make a major revision and update to FOG 1.1.3 or 1.2.0, then changes will be made to look for that version.

[B];TLDR SVN versions will always report this, but it is not an error so long as you did in fact install the SVN and not the current supported version.[/B]

If you don’t need the fixes that have been added to the SVN, you don’t have to use it, you can use the latest stable version if you would like.

Well, is tftpd-hpa service running when you reboot the machine?

If so then the fix won’t help you. If the service is not starting there is a way to make the service wait until the machine is booted and then it starts the service.

Incase it is the later of the two, the resolve is:

Change the line
[code]
start on runlevel [2345][/code]
in /etc/init/tftpd-hpa.conf to

[code]
start on (local-filesystems and net-device-up IFACE!=lo)
[/code]
And it is not a fault of FOG, this is a known issue with Ubuntu 12.04, and 14.04

You could try re-installing the tftpd-hpa service and see if that solves the issue:

[code]
sudo apt-get remove --purge tftpd-hpa
sudo apt-get update
sudo apt-get install tftpd-hpa
[/code]

This is probably not a FOG issue, this is an issue with your image set up.

I have had many images that I have built that have not liked some hardware and I had to create an entirely different unattend.xml file for those machines.

It sounds to me like there may be a driver included that is causing an issue. If you pull the plug and let the computer finish it’s OOBE process, plug the cable back in and boot, does the machine boot up as expected? Or after the completion of the OOBE process does the machine still hang on boot if the network cable is plugged in?

Is this issue related or the same as the one listed here [url]http://fogproject.org/forum/threads/image-troubles.11145[/url] ?

[quote=“Junkhacker, post: 33130, member: 21583”]it’s rare for me to beat Jaymes to the punch with this recommendation, but I recommend DNSMASQ
[url]http://fogproject.org/wiki/index.php/Using_FOG_with_an_unmodifiable_DHCP_server/_Using_FOG_with_no_DHCP_server#DNSMASQ_settings_for_iPXE[/url][/quote]

hahaha too true, sorry tearing out some old labs and technology, wasn’t at my machine, I see I’m slacking

Use the DNSMASQ solution to circumvent the need to edit your DHCP server. It looks for machines using tftpboot and issues the boot server and file name to the machine so it can resolve correctly to your fog server. I use this in multiple environments!

[quote=“purpleturtle99, post: 33118, member: 23775”]Thanks Jaymes, I wasn’t recommending any version of Ubuntu as such merely asking a question. OK All I need to know is what OS
does work with what version of fog. I have tried Ubuntu 12.04 with 0.32 what worked for a bit but then a had to image a newer laptop and it stopped working. I then upgraded to 1.0.1 and couldn’t get that to work due to booting the client pc’s.

Like I said I don’t really care what OS I use I just need to start making image ASAP… Debian or Ubuntu[/quote]

Naa I didn’t think you were, I just wanted to leave a tid bit of info

I use Debian, Debian at home, Debian at work. I use to be a HUGE Ubuntu nut, until they broke out of the typical mold that they set, now I recommend pure Debian.

I used Ubuntu when it launched, and I stopped recommending anyone use it at revision 10.04. I still use Ubuntu 12.04 and 10.04 to this day. 13.04/13.10 was also a good build of Ubuntu, and fixed some of the issues presented in 12.04, but I would still recommend Debian 7.5

Note that when you upgrade from a network set up for 0.32 to any 1.x.x version of FOG, that the boot file name has change from pxelinux.0 to undionly.kpxe and this needs to be fixed at your DHCP server.

And as always if you run into issues, please let us know!

There is a method used when creating apps and software UI for users called “The user is drunk” in which case you build the UI and the application/software to have enough guesses and checks that even an inebriated user will have no issues using. I think we can benefit here

I like this Idea, but I just spent the week explaining to my co-workers that FOG wasn’t the reason that our windows image wouldn’t activate because FOG doesn’t work with activation…

You can see where this is going to be a problem if using the FOG server to activate, it adds another place to point the blame.

I use the scripts that x23piracy posted, along with a

set KMS server:
[I]slmgr.vbs /kms kms.of.corporation.com[/I]

and haven’t had issues up to this point (other than network issues, or authentication problems none of which has to deal with FOG.)

I hope others use this tool, I for one don’t want that headache from my boss man -.-

(Usually I add these scripts to the setupcomplete.cmd but lately the models of tangents we have been receiving require the network drivers to be manually installed after OS installation, so it is a bat script I use to activate after I have connectivity to the network )

[quote=“purpleturtle99, post: 33082, member: 23775”]From the fog wiki:
[SIZE=6][B]Ubuntu 14.04[/B][/SIZE]

Jump to: [URL=‘http://www.fogproject.org/wiki/index.php/Ubuntu_14.04#column-one’]navigation[/URL], [URL=‘http://www.fogproject.org/wiki/index.php/Ubuntu_14.04#searchInput’]search[/URL]
[B]DO NOT USE THIS VERSION OF LINUX, IT IS TOO NEW AND THERE ARE ISSUES WITH TFTP UPSTART AGAIN, WHEN TIME ALLOWS AND MAJOR ISSUES WITH FOG HAVE BEEN RESOLVED, WE WILL TACKLE FIXES FOR THE UBUNTU 14.04 OPERATING SYSTEM![/B]

Is this still valid[B]??? I need to make images, please advice on best OS to install and best working version of fog[/B][/quote]

[quote=“NDNtech, post: 33083, member: 23658”]I was just about to post that when I saw that combo of fog and Ubuntu versions pop up in the queue. As far as I know it’s still valid, I think I saw Tom post that the other day in a thread. I’ve been wanting to jump to 14.04 since 12.04 support end soon. But I’m waiting on FOG.[/quote]

[quote=“purpleturtle99, post: 33089, member: 23775”]Thanks NDNtech. At work I have a Ubuntu 14.04 physical (Optiplex 380)machine to which I am going to install fog ver 1.1.2 today and try to make images. I will let you know how I get on with this combo.[/quote]

This is still very much the case, while we have made head way with the installer and curbing some issues of 14.04, it is not currently a supported operating system, we never gave the green light for installations. If you like Ubuntu, its look and feel, and how easy it is to use, install a pure Debian, it is what Ubuntu is built from. It is solid and in most cases works better than Ubuntu has.

While Ubuntu 14.04 does work and fog can be installed on it, we spend more time trying to troubleshoot the issues and fix what breaks than running the server, if you MUST use Ubuntu, stick with 13.04.

Yes the Ubuntu 12.04 OS is soon to fall off the supported list, please don’t let this scare you. This is NOTHING like when Microsoft decides an OS is on the out. Matter of a fact, you can still, to this day, install a Ubuntu 6. 7. 10 or whatever you want so long as you can find the iso and you can append the correct repositories to continue to receive software and updates for that software (not the core OS).

If you run a 14.04 Server, that is great, I’m glad you made the change; as a developer I am asking you, please don’t recommend this OS (Ubuntu 14.04) for a starting point! If you want to make documentation on the changes or what you have to do to fix them, that would be more beneficial.

I don’t think that you are doing anything wrong, I think the disk may just be blank and doesn’t have a partition so fog doesn’t know what to do with it.

So lets add a partition and see how the imaging goes. Please follow the directions listed here ->[url]http://fogproject.org/forum/threads/quick-format-to-ntfs-with-fog-for-noobs.10349/[/url]

Alternatively you can use a Windows install disk and let it format the drive, cancel installation and let it run through fog again, either way there needs to be a partition on the disk before you attempt to push to the disk.

You will need to recreate the download task on the fog server for the host in question.

[quote=“Jared, post: 32861, member: 25032”]I am having this issue as well. What is MPS? Lenovo ThinkpadT420[/quote]

Multi Partition Single Disk Its part of the disk type assignment for the image.

try this
[code]
sudo apt-get purge apache2
sudo apt-get update [/code]

then run your fog isntaller

You may want to free a little more space than that… But is your mysql service running? Try this command:

[code]
sudo service mysql restart[/code]

[quote=“RLane, post: 32598, member: 23505”]In previous versions of FOG, there was a limit (10 by default) where when you multicast for active PCs. Now, using 1.1.2, is that setting or default changed? I had a group with 32 computers in a lab and started them today assuming only specified number (figured 10 as default) would start, but all of them started. Sadly I have 10/100 switches to the class rooms and a Gb backbone. Has this changed or am I just missing the setting?

I figured something like this would be displayed when I started my multicast:

[url]http://www.fogproject.org/wiki/images/3/3d/Queue.jpg[/url]

Edit: I guess reading the wiki further states this was only for [I]ten[/I] unicast tasks, but multicast is considered one task itself. Is there a way to break the multicast down into parts other than making a separate group? I don’t know why 32 multicasts would be significantly slower than 8.[/quote]

Sounds like you figured it out there towards the end, Unicast has a limit to how many machines can be imaged at once, it can be increased or decreased by modifying the configuration settings.

As far as Multicast goes, your best bet is to start a group and name is Session1, Session2, etc. and put 10 or 12 machines in there and run the multicast for the group.

Unfortunately at the moment there are no ways to break down a multitask imaging task any further, but it may be something we will look into in the future.

Personally, I prefer to unicast to multiple machines at once, as you stated there is already a 10 client limit, and you can set up multiple machines to image and when a space opens in the queue it will fill it otherwise it will wait. This may be a little more beneficial to you than multicasting since you seem to want your machines to wait their turn so not to bog down the network, I’ve had multicast hurt me more times than it has helped.

If you want to use the Queue you need to use Unicast. Multicast makes sure all hosts are on the same “checkpoint” before proceeding and does not rely on the Queue.

Woo hoo! Good News Everyone! (Professor Farnsworth flash backs)

What version of Fog did you upgrade from?