Two other things to check are the bios versions identical, and is secure boot on or off.

Fog was listed as DNS server. We figured out the problem. Someone had entered the address of the Fog machine as a DNS server in IPv4 properties on the workstation. User error, totally unrelated to Fog. Please close or delete this topic. Thanks!

@george1421 Thanks for the info, I’ll look into that. Our network is quite small and I’ve fogged dozens of machines here. This was the first time I’ve ever encountered this issue.

@Quazz

Permissions solved the issue. Fog had access to the folder, but when I pasted this new image in it, it needed the permissions for it.

Thanks for the help!

@PageTown I know it was a long path to get to this point, BUT know in your heart you are in a better place for the pain you went through. (just channeling Dr. Phil).

You are on a current and supported release of the your OS and for FOG. When 1.3.0 stable is finally released you will be on a solid platform that you can use for a few years.

@Sebastian-Roth Ours was quite a few firmware updates behind and we weren’t able to jump from our current strait to the newest, but stepping up just one version solved it.

So what is the actual error you see after this. From what I see on the picture everything seams fine. Don’t see an error here. We need the error to be able to help. Or a PCAP file! 😄

Some how I feel a bit unsatisfied, but solving thread.

@Wayne-Workman
The issue i was having with windows storage nodes is likely a permissions issue, but the first thing we tried was setting the permissions across the board to full control. Good luck figuring it out. It was so annoying, we swapped the storage node for a linux machine.

Your issue sound similar to one that I had and one that someone else posted on here. Is the hard drive size that you created the image on the exact same size? Also is the image type you are using one that is not resizable? If so, either try shrinking the partition and reupload the image so that way there is about 1-2gb of unallocated space on the drive or simply try imaging a computer with a hard drive that you for sure know is larger (not same, larger) than the one used to make the image. Hope this helps.

Well,

I’d strongly recommend figuring out why. Eventually the machine will go down, whether you want it to or not. A storm could knock power out for hours, some jack— could hit a power pole with a garbage truck or something… and I’m willing to bet that none of us have more than some server-grade backup batteries that can hold out for hours…

It’s better to fix it now on YOUR time, rather than fix it later on CHANCE’s time.

[quote=“PageTown, post: 46537, member: 29454”]Here’s what’s I got when I ran ls -laR /images. The image I am trying to deploy is AcerIntel:[/quote]

Permissions look good to me. Everything owned by root:root, everything 777. You’ve got .mntcheck in the right spots.

[quote=“SeqSupport@Edkey, post: 46330, member: 27616”]What TFTP boot file are you using on your DHCP server? Are you using dnsmasq? Does the upload truly finish all the way?(make sure to check the task management section to see if the upload is stuck.)[/quote]

Coming back to the TFTP thing that SeqSupport brought up, I think that’s the next place to look.

I believe you’re running your own DHCP, right? yes.

[quote=“PageTown, post: 46443, member: 29454”]
Here’s what’s in my etc/dhcp/dhcpd.conf file:

DHCP Server Configuration file. see /usr/share/doc/dhcp*/dhcpd.conf.sample This file was created by FOG

use-host-decl-names on;
ddns-update-style interim;
ignore client-updates;
next-server 10.1.0.185;

subnet 10.1.0.0 netmask 255.255.254.0 {
option subnet-mask 255.255.254.0;
range dynamic-bootp 10.1.0.10 10.1.0.254;
default-lease-time 21600;
max-lease-time 43200;
option domain-name-servers 127.0.0.1;
option routers 10.1.0.185;
filename “undionly.kpxe”;

}[/quote]

See where it says: [CODE]filename “undionly.kpxe”;[/CODE]

That’s how you’d change the boot file you’re using. Try using undionly.kkpxe
Any change you make to your DHCP configuration file requires a DHCP restart. Remember the command to do that? Also, if you’re wondering where these files are, they are in /tftpboot the ones with .efi extensions are for UEFI systems. the ones without it are for BIOS systems.

Indeed it did the second time I rebooted the machine it’s on. Thanks!

Should be.

You’ll need to re-install and just choose DHCP this time.

There is an answer file somewhere that the FOG install script uses, it’ll try to pull answers from that.
You might need to delete that file. You might want to try modifying it first.

To use DHCP, change that option from 0 to 1

Here’s an article saying where the answer file is: [url]http://fogproject.org/wiki/index.php/Upgrading_the_FOG_Server[/url]