@russel0901 Well lets dig a little deeper into what the pxe booting client is being told. Please follow the instructions here to create a network capture of the pxe booting process. This tcpdump command will only collect pxe booting traffic. Please run the commands and then upload the pcap to a file sharing site (google drive, one drive, etc.) and post the link here or IM myself or Sebastian the link so we can take a look at what the pxe booting client is being told. https://forums.fogproject.org/topic/9673/when-dhcp-pxe-booting-process-goes-bad-and-you-have-no-clue

Your amazing! That worked! Thanks so much! and the quick response #FOG4LIFE until next time.

@Solo509 Best if you take a picture of the exact error on screen and post here. From what you wrote so far I would imagine that iPXE is not having the right driver for your USB-to-Ethernet or USB-C adapter. Which iPXE binary do you use? undionly.kpxe, ipxe.efi, snponly.efi, intel.kpxe, realtek.kpxe?? Take a look at /tftpboot/ on your FOG server to see all the different ones you can try.

@george1421 I actually got the legacy and efi to boot to fog without using the script. I put undionly.kpxe in the scope policy and ipxe in the scope options…it seems to work…i just wanted to see if it would make a difference. It Works! Eric

@george1421 Nice work George!!

Hi @antonionardella , I tried to reproduce the problem but I can’t (log with bad credentials). My log files don’t show the password or the username. Can you paste the error to try find where launch the exception or the error?

@Sebastian-Roth Well it looks like I need to pay better attention to the wiki articles. I reinstalled mono, complete this time, and I was able to push a task to the host. The Host still doesn’t show up as online within the host list on fog, but I can live with that. Thanks again! Now I can replace a fleet of windows signage machines!

@Sebastian-Roth For now, since I’m doing training laptops and they will always be in my work area when performing the imaging, I can use debug mode with lsblk/reboot for both capture and deploy to ensure the desired image is processed. Or I can just let it process both drives each time.

@george1421 @Tom-Elliott I think I have put this off for way too long as I expected it to be complicated to handle in all cases (fresh install as well as updates). But seems like this is fairly easy to accomplish: https://github.com/FOGProject/fogproject/compare/dev-branch...rename-account It’s still not finished yet but the basis is done and locking down the account won’t be much work I hope as I have done all the research and testing before. Highly appreciate any comments you guys have on this. I have greped the whole code to make sure I don’t miss anywhere to change the name or handle the new name.

@Sebastian-Roth I am now, as what I expected is the case.

@barachd Have you read my post about there being a bug within the Linux client implementation. See further down in this topic.

@Sebastian-Roth Okay so I just did a complete fresh install on a brand new server. Dev version 1.5.5.3. Absolutely no logs for me to look at inside the log viewer. Weird.

@Sebastian-Roth Thanks for your reply. Interesting to know, how FOG is starting up. As mentioned before, I think the issue was, that DHCP-Server couldn’t hand out a dynamic IP. So one of the last two requests seem to request with the wrong MAC address, as my DHCP has fixed reservations for the right MAC and should have delivered the right IP. Anyhow, as also mentioned before, the bug (or feature) is not occuring anymore as i freed up some space for dynamic hand out. So sorry, but I can’t provide additional Screenshots/Informations…

@Sebastian-Roth Hello, yes I have setup 3 servers with fog running and I was successful in capturing the image and deploying it to 18 computers at the same time. I did look at FOG API, but I had questions about it like does is it run on bash or other script but later figure that it runs on bash.

@Sebastian-Roth Thanks We’ll wait 1.5.6 as it’s non-blocking

@Sebastian-Roth Thanks!

Managed to get it to work however got stuck on another issue. After deployment I am encountering another issue after joining the computer to domain windows update is coming up blank and when clicking on start button and start typing nothing comes up (using the built in administrator everything works fine) On the legacy image I managed to fix it by using the setupcomplete.cmd (%WINDIR%\Setup\Scripts\SetupComplete.cmd) however this being a Dell laptop with OEM license it seems that this does not work REM "C:\Windows\Setup\Scripts\SetupComplete.cmd is executed as final step of coming out of Sysprep under SYSTEM account" REM "Clean up problems caused by using COPYPROFILE=TRUE" rd /s /q "C:\Users\Administrator\AppData\Local\Microsoft\Windows\WebCache" rd /s /q "C:\Users\Administrator\AppData\Local\Microsoft\Windows\INetCache" del /f /q /a:sh "C:\Users\Administrator\AppData\Local\Microsoft\Windows\WebCacheLock.dat" rd /s /q "C:\Users\Default\AppData\Local\Microsoft\Windows\WebCache" rd /s /q "C:\Users\Default\AppData\Local\Microsoft\Windows\INetCache" del /f /q /a:sh "C:\Users\Default\AppData\Local\Microsoft\Windows\WebCacheLock.dat" sc config FOGService start= auto shutdown -t 0 -r```

@Sebastian-Roth, @Tom-Elliott Many thanks! Works exactly like I needed ! @Tom-Elliott I’ll take a look at the 1.6 asap

@Franklyn I am not sure I get the point of verifying the images right after the transfer as image replication is a constant loop that does a check and re-transfer (if size and or checksum don’t match) of all the image files. Which versions of FOG do you run on the master and the storage nodes? Is it all surely 1.5.5???

@flo FWIW, one of the developers are adding your request to the LDAP plugin. Those should be in the mainstream code on the next release of FOG 1.5.6.