Posts made by Jaymes Driver

[quote=“holzfisch, post: 36898, member: 26225”]ubuntu[/quote]

what version -.-

You may also try Tom’s suggestions above.

what operating system did you install FOG on?

I’m willing to bet it is a setting in a switch, are you using wired connections to transfer? Is there a possibility to use a GIG switch to image, say 7 of them at a time? If that works you can daisy chain another hub to give you more space.

Right now, if I was in your shoes, I would isolate FOG and do some further testing to make sure that is it not my network, or networking equipment.

Also the compression listed on the GUI of the FOG dashboard. If you adjust the PIGZ compression to a lower number (less compression) the image will take less time to upload, it will take longer to deploy though.

What speeds are you seeing with Unicast that makes you feel as if FOG could be faster?

It’s VERY dependent on network gear too, are you using managed or unmanaged switches?

Have you followed the Cisco programming guide in the tutorials section if you have Cisco switches to see if your settings match that which are recommended?

We can’t make a recommendation for EVERY network set up in the world but we sure will try!

try this [url]http://fogproject.org/forum/threads/quick-format-to-ntfs-with-fog-for-noobs.10349/[/url]
it will guide you through removing the partitions and adding new ones. I believe this could be the cause of the “flyby” you are seeing.

[quote=“seekerbeta, post: 36864, member: 26173”]I only did the initial upload, have not had to run another upload since then, we just keep working of the same image.

Ive noticed another issue this morning where the “boot to HDD” option actually just loops back to the beginning, it never boots to the HDD[/quote]

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=“axel12, post: 36839, member: 24592”]I know the “donate” feature when imaging … and yes, it is nice … but I also have a rig or two and willing to throw coins … however …

There is no clearly identifiable donation address for BTC / LTC / DODGE … something like what thepiratebay is doing at the bottom of their page - very passive, yet also clearly visible.

… you know … for those people who would rather NOT user school resources to do hashing in order to contribute to this great project.[/quote]

Agreed, my boss would pull the FOG plug if he knew of the coin feature But I don’t mind donating my own machines to do bidding

I would recommend Debian.

I know Ubuntu looks the same but there have been changes behind the scenes where files are stored and this causes problems with the installation and the scripts because it doesn’t know where to find the information.

a LOT of the bugs we were facing have been squashed, but this is NOT the first time that Ubuntu has broken the debian mold it is built from.

We only recommend Ubuntu because Ubuntu was built to be easy to use for those that have never used linux before, and since they have made it difficult to drop FOG in place, we no longer recommend Ubuntu version 14.04 or higher.

I don’t have any of this equipment, I would be happy to offer expertise if I had it.

In theory yes, you can. It comes down to how much time you want to spend getting it working if it’s not a drop in replacement (if linux doesn’t have drivers for your machines.

In the past, I have used old server equipment for FOG Servers and NAS, but I had difficulty with the Raid controllers and wound up removing them and using the system that way.

You might need to give it a try by installing a Debian flavor (Ubuntu works) on the machine and working from there. If you find there are drivers missing, or you have error because the hardware is not behaving properly, I would move on the RedHat/ SuSE and see what it has to offer (being enterprise based it may support hardware that Debian does not).

The only way to find out is to try, and of course document it and share with the rest of us

I should further note, the machines I was working with were IBM Netfinity and eServers.

Personally, I would use the DNSMasq and stop messing with the scope and dns settings. DNSMasq works in such a way it only issues ips to machines looking to PXE boot so it won’t work like a DHCP server. And best of all, when you pull the fog server, nothing else in your network is affected.

DNSMasq is made so that users that don’t have the ability or the know how to edit the scope and DNS settings can still use some of the services.

I’m not saying your settings are wrong in any way. I had all my settings correct and STILL met proxy boot issues, particularly the Error you are experiencing.

I work in a Novell environment, Novell Netware 6.5 to be exact, which has strict limitations on a boot file name. In order to use the undionly.kpxe in fog I had to set up and enable DNSMasq to get my network to resolve my boot file and server. I had to do this for a number of reasons other than just Novell’s limit too. I have other technicians in my network that use WDS to image. Except their settings override mine. I also have IP helpers in my network, that override my boot settings that are set up for the WDS. DNSMasq has proven to be a wonderful solution many times worth it’s weight in gold. I know you want to save it for the last ditch effort, personally, I would be using it FIRST before I tried anything else (after of course adding my boot file and server to the scope and dhcp settings.)

Either way, Good luck and I hope you solve your issue.

Thank you Tom this line was the one i was looking for
[code]
Have you tried linking the tftpboot to /var/lib/tftp? (For some reason, some distro’s are really pushing to put the files here now.)[/code]

LordRaptor333 I have been able to alleviate this issue in my environment by using DNSMasq to help to resolve to my boot file and server.

My recommendation is in the link below:
[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]

This helps to solve issues when you can get the boot files on the client but they fail to load the boot file during pxe booting. Hope this helps!

however, there are some threads on this forum that are tailored towards the error you are experiencing and Ubuntu 14 because they decided to change where some core files are stored. You may want to search for those threads (sorry I don’t know what they are off the top of my head.)

Did you verify that Mysql was running?

try this:
[code]
sudo service mysql restart[/code]

id the name change service enabled? It sounds to me like the computer name doesn’t match what FOG thinks it should be and is attempting to set it, and rebooting to complete the change.

I know you are trying to get it to join to the domain, but lets test pieces at a time. Disable the name change service and see if that helps with the reboots.

Okay in that case, I would build the image on a virtual and a physical machine. You need to enter audit mode and then sysprep your image and upload.

I recommend using a physical and virtual environment, as my machines I had to build the image on the physical machine (it has something to do with the hardware in the computer.) After doing so and uploading the image, I was able to image my problematic machines without errors.

it downloaded to what ever folder you were in when you ran the sudo wget command.

Normally that would be a home folder unless you changed the directory and then ran the command.

check your home folder, type ls to see a list of current folders and files.

Do you use Unattend.xml to answer your installation questions?

I have had this error before but normally it was related to the hardware on the machin e(not sure why) but making a new unattend.xml file solved this issue for a particular model.

Is there a possibility that your image you created became corrupt? Have you tried upload the image again after resetting your VirtualBox image to a previous save state? Try running the chkdsk utility a few times and upload again, if the same issue occurs, try a different (or no unattend.xml) to troubleshoot unattend issues.

[quote=“prince xyryl, post: 36350, member: 25316”]up…

[B][COLOR=#ff0000]how? Where?[/COLOR][/B]

I cant see this on my FOG management page ([B] Download the FOG Client Service)[/B][/quote]

[url]http://youripaddressofyourfogserverhere/fog/client[/url]

Alternatively you can use the links at the bottom of the management page to get to the client.

Always willing to help! As long as it’s not after 3:30pm on a Thursday… I have to mow the grass on Thursday <.<

Glad you got is sorted, sometimes, a fresh install isn’t such a bad idea (even if you JUST installed fog)