@steharv Be sure to use my example completely and not just edit your ltsp.conf file to match. My config file is known to work correctly. # 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 Be sure to replace each instance of <fog_server_ip> with the IP address of your fog server. There are several instances of that tag in the config file above. The last bit is to ensure you have the correct version or later of dnsmasq or the config file will not work. From the linux command prompt key in dnsmasq -v. The version returned should be 2.76 or later. If its earlier than this you will have issues with uefi systems even if you use my config file exactly.

@jamesb Which version of FOG do you use? Is this an official iPXE binary provided by FOG or did you compile one yourself? I’ve tried GRUB, EXIT, and REFINED_EFI. All of them, except REFINED_EFI give me the same error. That’s pretty much impossible as the errors/codes you posted seem very much related to SAN boot. So please take the time and try all of them again but this time take a picture of the error and post all pictures together with according labels here.

@Sebastian-Roth said in Replication Issue: max_per_ip=200 Changes in the conf done, will let the rep job running 2 full rounds and edit this post with the results. “Seems like the default of 50 is not enough for the amount of images you have” yeah, as I said in the chat, here we use fog A LOT, bout 7 diferent images in frequent use and others 4 used from time to time. F* good tool indeed. hahaha Edit: Hell yeah! running like a charm! 3 rounds of rep job so far, no mismatch, no max conn reach… beautiful tks dude! Appreciate ur suport!

@Jethrov said in Symantec Endpoint Encryption: I would have assumed it would just have mounted the drive and overwrote it, however my tech is telling me it just failed out as it couldn’t find the mount point. Please do me a favor an let your tech take a picture of the actual error on screen. It’s a lot more helpful than trying to guess what was going wrong.

I think that I will disable it because I have done a tcpdump to see the traffic in the port 445 and the performance is not good. We are very far of 10 hosts per second. 1 hosts per second :( # tcpdump port 445 -i ens192 tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on ens192, link-type EN10MB (Ethernet), capture size 262144 bytes 13:21:53.447925 IP fog7.lgp.ehu.es.40826 > u030011.xa.bn.ehu.es.microsoft-ds: Flags [S], seq 2649384977, win 29200, options [mss 1460,sackOK,TS val 2588131295 ecr 0,nop,wscale 7], length 0 13:21:54.448890 IP fog7.lgp.ehu.es.40826 > u030011.xa.bn.ehu.es.microsoft-ds: Flags [S], seq 2649384977, win 29200, options [mss 1460,sackOK,TS val 2588132296 ecr 0,nop,wscale 7], length 0 13:21:55.591994 IP fog7.lgp.ehu.es.48832 > u030012.xa.bn.ehu.es.microsoft-ds: Flags [S], seq 3272040579, win 29200, options [mss 1460,sackOK,TS val 2588133438 ecr 0,nop,wscale 7], length 0 13:21:56.592905 IP fog7.lgp.ehu.es.48832 > u030012.xa.bn.ehu.es.microsoft-ds: Flags [S], seq 3272040579, win 29200, options [mss 1460,sackOK,TS val 2588134440 ecr 0,nop,wscale 7], length 0 13:21:57.724226 IP fog7.lgp.ehu.es.57840 > u030013.xa.bn.ehu.es.microsoft-ds: Flags [S], seq 1809232999, win 29200, options [mss 1460,sackOK,TS val 2588135571 ecr 0,nop,wscale 7], length 0 13:21:58.724890 IP fog7.lgp.ehu.es.57840 > u030013.xa.bn.ehu.es.microsoft-ds: Flags [S], seq 1809232999, win 29200, options [mss 1460,sackOK,TS val 2588136572 ecr 0,nop,wscale 7], length 0 13:21:59.797692 IP fog7.lgp.ehu.es.39344 > u030014.xa.bn.ehu.es.microsoft-ds: Flags [S], seq 969204538, win 29200, options [mss 1460,sackOK,TS val 2588137644 ecr 0,nop,wscale 7], length 0 13:22:00.798892 IP fog7.lgp.ehu.es.39344 > u030014.xa.bn.ehu.es.microsoft-ds: Flags [S], seq 969204538, win 29200, options [mss 1460,sackOK,TS val 2588138646 ecr 0,nop,wscale 7], length 0 I wiil wait to 1.6 version and see :)

@nadhim Are you working together with @rlindenschmidt or simply seeing the same issue? Have you read my answer? Please post a picture of windows disk management so we know more about your partition layout. Changing to a newer Kernel didn’t fix it either (I first used 4.410-1 and I am now running 4.6rc7-1) Those kernel versions don’t seem to match those that we use in FOG lately. Are you sure you are using FOG at all? Which version?

Are you saying you have the same error and it was fixed by disabling dhcp-snooping on the switch? I’m just trying to understand the context here.

@iekozz There are two commands you need to use when removing applications. The first one removes it from the current user the second one removes them from the system. You do this as the administrator before any one else logs into the computer. After the script is run, the next users that login will not have the application on the desktop or start menu. That is the way at least it use to work. I have not done image design in a few months. MS could have changed things (yet again) with 1809 that I’m not aware of.

@Sebastian-Roth @Quazz Make sure you disable fast boot and shutdown the machine using shutdown -s -t 0 -f in Windows command line. I used the shutdown command. I’ll try disabling fast boot and reimaging. Is it possible you’re deploying an MBR (legacy/old BIOS) (assuming, based on your partitions) to a system that’s trying to boot in GPT (new/UEFI) mode? It’s possible the VM i made uses MBR. But i’ve enabled Legacy boot on the BIOS and disabled secure boot. Also with the other image(not resizable) i made i have no problems deploying. Does d1.mbr exist in your image folder? Yes, it does. The thing i don’t understand is how i don’t have any problems deploying the other image i made. Which is Not Resizable. I’m deploying on the exact same machine. I do have the option legacy boot enabled in the BIOS, and secure boot disabled. I’ve tried using uefi boot but that doesn’t work at all. Maybe i have to add some kind of option or parameter in the host options on the FOG UI?

I want to use the automatic brightness adjustment. The only thing, the slider in the windows settings shows me 100% but I know that the brightness is not all the way to 100%. Because if I un-check the autobrightness, the screen flashes me to is so much brighter. It is getting much brighter on 100%, then 100% with auto brightness. (When I take a flash light and point into the sensor, the screen will adjust correctly. And again, that all compared to a Surface Go out of the box = which is working fine.)

If anyone is interested this worked for me. I found this in a MS thread. I placed this in my Windows\Setup\Script\SetupComplete file just above the fog service enabled command. del /F /Q C:\Users\Default\AppData\Local\Microsoft\Windows\WebCacheLock.dat del /F /Q C:\Users\Default\AppData\Local\Microsoft\Windows\WebCache*.* del /F /Q C:\Users\Default\AppData\Local\Microsoft\Windows\INetCache*.*

@Wayne-Workman It doesn’t unset the storage group, it just doesn’t show the storage group under the list all item. Likely just a typo, but at the moment not a high priority thing.

@Dee I’d suggest removing those half way uploaded images: rm -rf /home/images/dev/f48e38d9d9cd /home/images/dev/f48e38dc5f88 (be careful with this rm -rf command, I am not accountable for anything going wrong with deleting files from your server) Then again check free disk space df -h, probably we’ll need to delete real images as well. I’m wondering if the system is looking for sda7 as in the image_0496 and sda7 doesn’t seem to exist. This is on the client being imaged. Just means your client has seven or possibly more partitions. Or maybe it’s just one primary (sda1) and three extended ones (sda5, sda6, sda7).

@Fernando-Gietz You mean the installer or pushing a single partition to clients via multicast?

@Sebastian-Roth Dear Sir, Thank you for your kind reply. Basavaraj, From India.

@jdcraymond Ok, official 4.19.1 kernels with mentioned driver enabled are uploaded.

@afriedman said in UEFI, Dell Workstation Tower, FlexBay PCIe NVMe, Windows 10, FOG cannot detect PCIe NVME SSD: Is there any way I can incorporate these .cat, .inf, .sys, and .oem files into the FOG deployment process, since Windows Setup can use them to see the SSD? Those drivers won’t help you with FOG. They are from a completely different world and won’t work on Linux / FOG.

@Sebastian-Roth Dear Sir(Sebastian-Roth), I understood (Not Everything) what you explained about My Questions… You explained that not to define DNS Address in My Network Scenario… But I already defined it with this Address10.10.1.2 Now Whether it is possible to remove it OR let it be as it is…? Kind Hardheartedly Thank you For In Time Help… Kind Regards, Basavaraj, From India.

@Sebastian-Roth Yes it is working now - thank you !!

George, Thanks for the ideas. I am going to try to build my own customized LIVECD version and see if I can get it to run. Will report back (will most likely take me a while!). Thanks for the insight. Colin