@utilman I can’t explain the wait other than the 2 of the 12 that didn’t compete there is an issue. Since you have php 7.1 install the path to the file is a bit crazy. I should have had you search that instead of using my memory for the path. Well what is at issue, there is a memory leak (FOG asking for a block of memory from the OS and not returning it after the task is over) in the FOG code. The developers are having a hard time finding this one line of code in the 1000s of lines that make up the FOG server. What this “fix” does is restart the pgp-fpm worker threads after they have responded to 2000 requests. This fix keeps the memory usage from ballooning out of control and the UI responsive. Its good practice to have this option on anyway. The next release of FOG (1.5.3) will have this feature enabled by default so I’m told.

@nateuh Remember that your multicast stream will transmit as fast as your slowest computer in the multicast group. So if you have 5 quad core i7s computers with nvme drives and one computer with a Pentium 4 with a 5400 RPM hard drive, the imaging will only go as fast as the Pentium 4 can take in the image. So its possible that one of your target systems is causing this issue too.

Try using a different bootfile such as ipxe.kpxe

For reference here is an example of a isc-dhcp config file: https://wiki.fogproject.org/wiki/index.php/BIOS_and_UEFI_Co-Existence#Example_1

@kreios Under the fog settings there is a kernel update option where you can download new kernels. But if you just installed FOG you will have the latest stuff since the installers will download latest on each install. If you are using hyper-v and 1803 version of win10, there has been reports of people not able to pxe boot into the FOG menu. This appears to be an issue with iPXE and hyper-v under 1803 only.

Here is the contents of those files. I thought i shrunk this drive in windows before I did the capture. I could be mistaken as i was doing a bunch of stuff. Looks like the primary partition itself wants 64GB so its no wonder why its not working however i have included a not resizeable capture i did where i know its shrunk to around 33GB at the bottom that does the same thing. In windows the drive shows 30.8 however the partitions file shows 64Gb for the size. fixed size :2:3:1 minimum label: gpt label-id: CA2CF626-B6A1-BE98-571A-1A6FE2E6B6DE device: /dev/sda unit: sectors first-lba: 34 last-lba: 250069646 /dev/sda1 : start= 40, size= 921600, type=DE94BBA4-06D1-4D40-A16A-BFD50179D6AC, uuid=2B630EF3-1CF9-42FB-846C-792BF8938857, name="Basic data partition" /dev/sda2 : start= 921640, size= 104426, type=C12A7328-F81F-11D2-BA4B-00A0C93EC93B, uuid=95A294AF-CC04-4743-AB0D-ADB83A5E365E, name="EFI system partition" /dev/sda3 : start= 1026066, size= 32768, type=E3C9E316-0B5C-4DB8-817D-F92DF00215AE, uuid=2967A63F-3AA1-4409-BDA8-305B43B9513E, name="Microsoft reserved partition" /dev/sda4 : start= 1058834, size= 64605696, type=EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, uuid=18916FDB-D9D2-4F31-AD1F-1F574B24070A, name="Basic data partition" /dev/sda5 : start= 246730258, size= 3338240, type=DE94BBA4-06D1-4D40-A16A-BFD50179D6AC, uuid=17DDD755-5CBF-4FBE-AAA4-C20CE93D52A8, name="attrs="RequiredPartition GUID:63" partitions label: gpt label-id: CA2CF626-B6A1-BE98-571A-1A6FE2E6B6DE device: /dev/sda unit: sectors first-lba: 34 last-lba: 250069646 /dev/sda1 : start= 40, size= 921600, type=DE94BBA4-06D1-4D40-A16A-BFD50179D6AC, uuid=2B630EF3-1CF9-42FB-846C-792BF8938857, name="Basic data partition" /dev/sda2 : start= 921640, size= 104426, type=C12A7328-F81F-11D2-BA4B-00A0C93EC93B, uuid=95A294AF-CC04-4743-AB0D-ADB83A5E365E, name="EFI system partition" /dev/sda3 : start= 1026066, size= 32768, type=E3C9E316-0B5C-4DB8-817D-F92DF00215AE, uuid=2967A63F-3AA1-4409-BDA8-305B43B9513E, name="Microsoft reserved partition" /dev/sda4 : start= 1058834, size= 64605696, type=EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, uuid=18916FDB-D9D2-4F31-AD1F-1F574B24070A, name="Basic data partition" /dev/sda5 : start= 246730258, size= 3338240, type=DE94BBA4-06D1-4D40-A16A-BFD50179D6AC, uuid=17DDD755-5CBF-4FBE-AAA4-C20CE93D52A8, name="attrs="RequiredPartition GUID:63" Shrunk not resize label: gpt label-id: CA2CF626-B6A1-BE98-571A-1A6FE2E6B6DE device: /dev/sda unit: sectors first-lba: 34 last-lba: 250069646 /dev/sda1 : start= 40, size= 921600, type=DE94BBA4-06D1-4D40-A16A-BFD50179D6AC, uuid=2B630EF3-1CF9-42FB-846C-792BF8938857, name="Basic data partition" /dev/sda2 : start= 921640, size= 104426, type=C12A7328-F81F-11D2-BA4B-00A0C93EC93B, uuid=95A294AF-CC04-4743-AB0D-ADB83A5E365E, name="EFI system partition" /dev/sda3 : start= 1026066, size= 32768, type=E3C9E316-0B5C-4DB8-817D-F92DF00215AE, uuid=2967A63F-3AA1-4409-BDA8-305B43B9513E, name="Microsoft reserved partition" /dev/sda4 : start= 1058834, size= 64605696, type=EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, uuid=18916FDB-D9D2-4F31-AD1F-1F574B24070A, name="Basic data partition" /dev/sda5 : start= 246730258, size= 3338240, type=DE94BBA4-06D1-4D40-A16A-BFD50179D6AC, uuid=17DDD755-5CBF-4FBE-AAA4-C20CE93D52A8, name="attrs="RequiredPartition GUID:63"

It also appears you’re missing the actual FOG-API-TOKEN header. E.G. Try: curl -H 'fog-api-token: YourFOGAPITokenHere' -H 'Content-type: application/json' -u api:password 'http://fog.home/fog/task/active' -vvv

@sebastian-roth What do you think about setting the kernel parameter of ACPI=off if its a conflict between the Linux kernel and the target firmware?

@Sebastian-Roth Yes it does return. I even see a ton of data being downloaded. I have cut off the data towards the end due to the length of the capture. 563 13.682607 10.86.96.177 10.85.195.199 TCP 74 50514 > 8080 [SYN] Seq=0 Win=29200 Len=0 MSS=1460 SACK_PERM=1 TSval=1729539897 TSecr=0 WS=128 569 13.742557 10.85.195.199 10.86.96.177 TCP 78 8080 > 50514 [SYN, ACK] Seq=0 Ack=1 Win=65535 Len=0 MSS=1460 SACK_PERM=1 TSval=400875488 TSecr=1729539897 WS=64 570 13.742594 10.86.96.177 10.85.195.199 TCP 66 50514 > 8080 [ACK] Seq=1 Ack=1 Win=29312 Len=0 TSval=1729539912 TSecr=400875488 571 13.742693 10.86.96.177 10.85.195.199 HTTP 161 CONNECT fogproject.org:443 HTTP/1.1 575 13.801898 10.85.195.199 10.86.96.177 TCP 66 [TCP Window Update] 8080 > 50514 [ACK] Seq=1 Ack=1 Win=771008 Len=0 TSval=400875548 TSecr=1729539912 576 13.864407 10.85.195.199 10.86.96.177 HTTP 105 HTTP/1.1 200 Connection established 577 13.864424 10.86.96.177 10.85.195.199 TCP 66 50514 > 8080 [ACK] Seq=96 Ack=40 Win=29312 Len=0 TSval=1729539942 TSecr=400875608 579 13.87112 10.86.96.177 10.85.195.199 TLSv1.2 583 Client Hello 582 13.992592 10.85.195.199 10.86.96.177 TLSv1.2 1414 Server Hello 583 13.992609 10.85.195.199 10.86.96.177 TCP 166 8080 > 50514 [PSH, ACK] Seq=1388 Ack=613 Win=771008 Len=100 TSval=400875738 TSecr=1729539944 [TCP segment of a reassembled PDU] 584 13.992616 10.86.96.177 10.85.195.199 TCP 66 50514 > 8080 [ACK] Seq=613 Ack=1488 Win=32128 Len=0 TSval=1729539974 TSecr=400875738 585 13.992893 10.85.195.199 10.86.96.177 TCP 1414 8080 > 50514 [ACK] Seq=1488 Ack=613 Win=771008 Len=1348 TSval=400875738 TSecr=1729539944 [TCP segment of a reassembled PDU] 586 13.992908 10.85.195.199 10.86.96.177 TCP 166 8080 > 50514 [PSH, ACK] Seq=2836 Ack=613 Win=771008 Len=100 TSval=400875738 TSecr=1729539944 [TCP segment of a reassembled PDU] 587 13.992916 10.86.96.177 10.85.195.199 TCP 66 50514 > 8080 [ACK] Seq=613 Ack=2936 Win=35072 Len=0 TSval=1729539974 TSecr=400875738 588 13.992928 10.85.195.199 10.86.96.177 TLSv1.2 640 Certificate, Server Key Exchange, Server Hello Done 589 13.995298 10.86.96.177 10.85.195.199 TLSv1.2 192 Client Key Exchange, Change Cipher Spec, Encrypted Handshake Message 593 14.114585 10.85.195.199 10.86.96.177 TLSv1.2 117 Change Cipher Spec, Encrypted Handshake Message 594 14.114752 10.86.96.177 10.85.195.199 TLSv1.2 182 Application Data 598 14.237584 10.85.195.199 10.86.96.177 TCP 1414 8080 > 50514 [ACK] Seq=3561 Ack=855 Win=771008 Len=1348 TSval=400875988 TSecr=1729540005 [TCP segment of a reassembled PDU] 599 14.237599 10.85.195.199 10.86.96.177 TCP 166 8080 > 50514 [PSH, ACK] Seq=4909 Ack=855 Win=771008 Len=100 TSval=400875988 TSecr=1729540005 [TCP segment of a reassembled PDU] 600 14.237607 10.86.96.177 10.85.195.199 TCP 66 50514 > 8080 [ACK] Seq=855 Ack=5009 Win=40704 Len=0 TSval=1729540036 TSecr=400875988 ...... ..... .... ...

@tom-elliott Thank you, I will follow the step and let you know if I run into problems. Tom

What goes wrong with your storage node? What are you trying to accomplish? Deploy from different storage nodes in different locations? (read up on location plugin if you haven’t already)

@stylus3530 In fact, you can deploy a 1.2.0 image and re-capture with 1.5.2. All you need to do is not allow the image to boot. Once deployed, immediately re-capture and all should work fine.

Here is what my unattend.xml looks like. I have made some redactions and comments to help out. I made mine using Windows System Image Manager. This is one of many webpages I used to learn about building my unattend file (and lots of trial and error): https://www.tenforums.com/tutorials/3020-customize-windows-10-image-audit-mode-sysprep.html <?xml version="1.0" encoding="utf-8"?> <unattend xmlns="urn:schemas-microsoft-com:unattend"> <settings pass="specialize"> <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <ProductKey>Your key</ProductKey> <TimeZone>Your TimeZone</TimeZone> </component> <component name="Microsoft-Windows-Deployment" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <!--I had to add this as FOG wasn't expanding my OS partition all the way after OOBE ran--> <ExtendOSPartition> <Extend>true</Extend> </ExtendOSPartition> </component> </settings> <settings pass="oobeSystem"> <component name="Microsoft-Windows-International-Core" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <InputLocale>en-US</InputLocale> <SystemLocale>en-US</SystemLocale> <UILanguage>en-US</UILanguage> <UserLocale>en-US</UserLocale> </component> <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <OOBE> <HideEULAPage>true</HideEULAPage> <HideLocalAccountScreen>true</HideLocalAccountScreen> <HideOEMRegistrationScreen>true</HideOEMRegistrationScreen> <HideOnlineAccountScreens>true</HideOnlineAccountScreens> <HideWirelessSetupInOOBE>true</HideWirelessSetupInOOBE> <ProtectYourPC>1</ProtectYourPC> </OOBE> <UserAccounts> <!--If you skip account creation in OOBE, you need to enable local Administrator account or create another admin account in unattend file --> <AdministratorPassword> <Value>Your AdministratorPassword==</Value> <PlainText>false</PlainText> </AdministratorPassword> </UserAccounts> <StartTiles> <PromoteOEMTiles>false</PromoteOEMTiles> </StartTiles> <AutoLogon> <Password> <Value>password again</Value> <PlainText>false</PlainText> </Password> <LogonCount>1</LogonCount> <Username>Administrator</Username> <Enabled>true</Enabled> </AutoLogon> <FirstLogonCommands> <SynchronousCommand wcm:action="add"> <CommandLine>reg add &quot;HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon&quot; /v AutoLogonCount /t REG_DWORD /d 1 /f</CommandLine> <Description>Set AutoLogin count back to zero</Description> <Order>1</Order> <RequiresUserInput>false</RequiresUserInput> </SynchronousCommand> </FirstLogonCommands> </component> </settings> <settings pass="offlineServicing"> <component name="Microsoft-Windows-PnpCustomizationsNonWinPE" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <DriverPaths> <!--If you are using the postdownload script for driver injection, you will need this --> <PathAndCredentials wcm:action="add" wcm:keyValue="1"> <Path>C:\Windows\DRV</Path> </PathAndCredentials> </DriverPaths> </component> </settings> <!--don't think the offline image part is needed, but it's part of the one that get's made when I use Windows System Image Manager --> <cpi:offlineImage cpi:source="source" /> </unattend>