[quote=“ID10Tea, post: 4034, member: 1040”]@BryceZ… If I recreate the task then they hang at “please wait”
Thanks Chris, I guess It may be time to rebuild it. This is the 3rd time.[/quote]
I know the pain, this is my 4th build 🙂

That worked.

Thanks

yeah give 10.04.04 LTS Server a go, spin one up in Virtualbox.

Install Webmin 1.580 to manage it

Do you have any error messages?

I believe the FOG Linux user password and the FTFP password have to be the same. upgrading FOG might have changed the TFTP one, but not the Linux FOG as the user was already created.

To test, get the TFTP password from the .cfg and try to use it to login to the Linux FOG user account.

[LIST=1]
[]Storage Management --> All Storage Nodes and click on the storage node that doesn’t display in the landing page
[]Make sure the IP address matches the address of wherever it is being stored
[/LIST]

Had this same issue today and that is how i fixed mine

yes you can have multiple kernels, if that field is blank the host will default to the kernel you have set as bzImage

here is a quote from another thread [url]http://fogproject.org/forum/threads/fog_0-32-on-ubuntu-12-04.831/#post-3877[/url]

[quote=“falko, post: 3837, member: 48”]nope, you need to add it like this… Host Kernel: fog/kernel/<name_of_kernel>
all those with blank fields will default to the kernel you have set as bzImage

Note: In the screenshot below the kernel is called acer-aspire

[IMG]http://community.spiceworks.com/images/how_to_steps/0000/6034/hostview.png[/IMG]

check links
[url]http://community.spiceworks.com/how_to/show/2338[/url]

[url]http://fogproject.org/forum/threads/deployment-freezing.356/#post-1506[/url][/quote]

I Updated the kernel by putting the bzImage in the right place /tftboo/fog/kernel when what happend with the 3.4 and the 3.3 is that it causes computer to restart when try to go for inventory.

I have the same issue on a Dell Optiplex 790; I noticed the bios supports Dell Imaging… You can input the Image Host IP in the BIOS.
I am trying to disable all of this in an effort to get it fogged.
I will post my trials and errors soon.

Not sure if I understood your problem, but you did not install DHCP server on the FOG server and you have a windows server that acts as DHCP server. Then you changed your scopes on your windows DHCP server and PXE stopped working?
If so you just need to make sure your new DHCP scopes are configured on the Windows DHCP server, see this for more help on that:
[url]http://www.fogproject.org/wiki/index.php/Modifying_existing_DHCP_server_to_work_with_FOG[/url]

If you dont have dhcp server installed on your FOG server there shoudent be any dhcp config files on it.

anyone able to help?

can anyone help me?

Hi A[URL=‘http://fogproject.org/forum/members/astrouga.907/’]astrouga[/URL],
Thanks for the info
The blank screen happen while i am trying to full register option with FOG, during the initial boot registration phase its not getting even to write computer name.

I will try 3.4 , but DL360 G5 its old server model at least 4 years so 3.3 should be working ?

yes. That is (after all) what PXE boot is for. I have set my menu time to be 1 second (therefore on the machines I want I need to hammer the down key to pause the countdown) and passworded all the options available for those who are curious.

This also has the byproduct of being able to force imaging simply by rebooting the system.

The “Change NFS Location” link was what I used and it worked perfectly for me FWIW. I’d double check that you followed the directions completely, used the correct paths and set all the permissions correctly. It sounds like, at minimum, you’re really close.

I assume “media/98…AA08/images/fog/Win7.64.PRO” exist and FOG has permissions for the Win7.64.PRO folder?

thought it might, that kernel and 3.2.4 works for all laptops/desktops i have