@Wayne-Workman thanks for reporting, the issue has been fixed. It was caused by the anti-spam plugin being stale.

@stefan-hanke There’s some classes in France, plus a book written in French. Not helpful for most of us. There currently isn’t any ‘fogproject blessed’ training.

As far as documentation goes for distributed setups, we have these two articles:
https://wiki.fogproject.org/wiki/index.php?title=Replication
https://wiki.fogproject.org/wiki/index.php?title=Location_Plugin

I’ve been wanting to create some more videos on distributed fog setup, tried to do it a few months ago but ran into some problem.

Please use my ltsp.conf file here exactly.

# Don't function as a DNS server: port=0 # Log lots of extra information about DHCP transactions. log-dhcp # Set the root directory for files available via FTP. tftp-root=/tftpboot # The boot filename, Server name, Server Ip Address dhcp-boot=undionly.kpxe,,<fog_server_IP> # Disable re-use of the DHCP servername and filename fields as extra # option space. That's to avoid confusing some old or broken DHCP clients. dhcp-no-override # inspect the vendor class string and match the text to set the tag dhcp-vendorclass=BIOS,PXEClient:Arch:00000 dhcp-vendorclass=UEFI32,PXEClient:Arch:00006 dhcp-vendorclass=UEFI,PXEClient:Arch:00007 dhcp-vendorclass=UEFI64,PXEClient:Arch:00009 # Set the boot file name based on the matching tag from the vendor class (above) dhcp-boot=net:UEFI32,i386-efi/ipxe.efi,,<fog_server_IP> dhcp-boot=net:UEFI,ipxe.efi,,<fog_server_IP> dhcp-boot=net:UEFI64,ipxe.efi,,<fog_server_IP> # PXE menu. The first part is the text displayed to the user. The second is the timeout, in seconds. pxe-prompt="Booting FOG Client", 1 # The known types are x86PC, PC98, IA64_EFI, Alpha, Arc_x86, # Intel_Lean_Client, IA32_EFI, BC_EFI, Xscale_EFI and X86-64_EFI # This option is first and will be the default if there is no input from the user. pxe-service=X86PC, "Boot to FOG", undionly.kpxe pxe-service=X86-64_EFI, "Boot to FOG UEFI", ipxe.efi pxe-service=BC_EFI, "Boot to FOG UEFI PXE-BC", ipxe.efi dhcp-range=<fog_server_ip>,proxy

As long as you have at least dnsmasq 2.76 or newer it will work correctly. Don’t forget to replace <fog_server_ip> with the IP address of your fog server.

ref: https://forums.fogproject.org/topic/8725/compiling-dnsmasq-2-76-if-you-need-uefi-support/5

@george1421 said in Deploy image only in the SSD hd:

@fog-user The developers have done a great job thinking about all of the different hardware combinations out there and built in a lot of useful “tweaks” that can be done.
I’m glad you were able to get your imaging going like you need. Is it OK to solve this thread?

yes @george1421 is it ok.
thank you

@sebastian-roth Mh, yes i think, strange
Thanks 😄

@john-johnson Check that host with disk diagnostics and ram diagnostics. Often these tests are built into firmware and you can select them when the device is just powering on. Generally though, if the errors are not excessive it’s normally fine.

Is Bitlocker enabled?

Any specific reason for using this over resizable?

@unknownhost99 Could be as Wayne said, a rogue DHCP server or could be a dozen other things. There is no reason to hide internal network IPs. More often than not we see things on the screen that you don’t see. So you might post a full picture and tell us which IPs your DHCP server and which your FOG server has.

By the way, what is serving DHCP in your network? Has your setup ever worked or is it a fresh install? Which version of FOG?

Beside that you can take a look at the files in the TFTP directory on your FOG server to see if they do exist: ls -al /tftpboot

As well see if the TFTP server is running on your FOG server: netstat -antup | grep 69

Post the output of both commands here.

@unknownhost99 What was wrong? How did you fix it? These are things that future readers will wish you shared.

@breit said in Expanded Virtual Disk but FOG doesn’t see the change:

Ubuntu sees it just fine but I’m not able to get FOG to see the newly added space.

What do you mean by “Ubuntu sees it”? We need more details to help. So far you haven’t told us anything about what steps you made (details!) to expand virtual disk, LVM, partition, filesystem and how your setup looks like.

@george1421 said in Unable to UEFI boot to Fog Server:

If Windows 2008 DHCP doesn’t support automatic uefi/bios (I know it doesn’t)

If it does, I cannot figure it out. I spent days trying. One would think it can given the available GUI options in 2008 DHCP, but configuration of it is just way too complicated. 2012 R1 and above handles it nicely though.

@sebastian-roth

ok, thanks for the help

@junkhacker Not invalid password but ACCESS DENIED

@dylan123 I think this is very hard to debug not sitting right in front of the machines myself. You need to know that everything is this chain could be the bottle neck. So the best you can do is cross test things to hopefully nail it down. That means testing at least on three different clients in the exact same scenario (same network switch, no other things running over the network or on the FOG server at the same time). See if they all behave the same. If so, then you need to look into network or FOG server to find the issue. If they all go different speeds, then note down the numbers (start, end, average speed), redo the test again and see what you get. Possibly you can nail down one host that is different than the other two. Do a badblocks and memtest on that machine. As well see if that one has slightly different hardware.

@wayne-workman yes i saw thanks

@dpotesta50 I wanted to add to Wayne’s very important questions that we also need to know what exactly you see before the screen you posted the picture of. It surely is a blue partclone screen and it has the actual error printed. You need to take a picture of that!

@george1421 ah, yes I see it does say that in the Windows 7 guide… i didn’t look at it as i was trying windows 10 first. many thanks

You may have to do this by sql commands since that function is not supported by the GUI, even the latest version. Plus your version of FOG is about 5 years old (if not longer). It is difficult to provide support by the developers for something that old.

Is this thread asking if FOG can automatically assign a name to a host? Yes. It’s call quick registration auto population.

@meki333 If you cannot connect via the computers FQDN, then you have a DNS problem (or are lacking a DNS implementation altogether).