@martial The fog-client mostly fails with Middleware::Response Invalid security token. From that I see in our code this can only happen if there is a security token set in the DB for this host (identified via MAC address but it’s always the same as you re-use the same adapter over and over). Well let’s see if we can figure this out in the DB: shell> mysql -u root -p Password: ... mysql> use fog; ... mysql> SELECT h.hostID,h.hostName,h.hostSecToken,m.hmMAC,m.hmPrimary,m.hmPending FROM hosts h JOIN hostMAC m ON h.hostID=m.hmHostID AND m.hmMAC LIKE '%aa:bb:cc:dd:ee:ff%'; ... Use the USB nic adapter MAC address instead of aa:bb:cc:dd:ee:ff. See if you get any results.

I can’t seem to recreate it, but I know it’s broken whenever I deploy a new computer. So next time I have to image a computer I’ll come on back

@Sebastian-Roth This is exactly what it was. I feel a little embarrassed haha. Thank you for your help

@xburnerx00 The fog-client is running as a service (system account). It’s probably not able to write into a users home (Desktop) directory. Try using something like C:\Temp and make sure that is writeable for everone…

@Sebastian-Roth Ok, Thank you for the help. I will have to research snapins some more. It seems the issue for this post has been resolved. So I will mark that post as the answer. If I have anymore problems I will make a new post.

@Sebastian-Roth said in Unallocated space: df -h Looks like i’m good to go. Thanks very much for all your help. I will save the commands for future reference.

@andrewhancock91 Asking the internet for “runas password” brings up a huge amount of questions and answers on this. Maybe just use psexec… Or even using a text file as password input. But that’s just my point of view trying to tackle this as low cost as possible.

@thomasg07 What Linux OS (version) did you try to install FOG on? Your PHP version seems to be way to old (5.4.45) and causes the problem.

oh ok thanks :)

@lacaca Please post the picture!

The intent of the following tutorial is to show you how its possible to use FOG to pxe boot a live environment with FOG: https://forums.fogproject.org/topic/10944/using-fog-to-pxe-boot-into-your-favorite-installer-images Again creating a disk-less boot environment is not the intent of FOG, its just a proof of concept.

Thank you so much, with the new / old inits the capture process ran successfully. Am trying to deploy now and see if everythin works out. Thanks for your help Sébastien

@Sebastian-Roth I have this issue on the Dell 7730 as well, but after the successful deploy in debug task mode the CentOS boot option reappeared, however the new long name for the windows partition is still there, also the new long name for the linux drive/partition is still there even after the CentOS boot option reappeared. Another problem was that when the CentOS came back into the bios it was placed at the top of the boot order sequence, which breaks PXE boot requiring a reboot into setup to correct. I believe that I ran across something related to that on the forums while searching for other information, but at the time I didn’t care what the drive/partition was called here so long as it worked.

@george1421 said in Presenting On FOG at conference?: I happen to have Raspbian installed without the gui. We all know that’s the only way. :-)

@totoro Sounds like you have a rough DHCP server somewhere in your network! Read about this topic on the web and try to find it. Yes it’s true, but the message is the same, I am fairly sure the IP address is also different!!! Next time post your own picture!

@sudburr I believe that solved it! On my first attempt I inserted a 5 second delay after every command in my SetupComplete.cmd; that did not help. Then I added an additional 60 second delay at the start of the SetupComplete.cmd and my first test after was successful.

Thank you all; you have answered my questions! I have about five images I use most of the time. I do believe your suggestion to deploy from FOG and then capture using CZ would be my best option! And thank you for helping me understand the fundamental differences between FOG and CZ!

@Scott-B Understand that link is for BIOS based computers. I might expect the UEFI mode computers will need a bit different boot kernel. Looking at that error message again, why is it asking about bootmgr.exe that is a “MS Windows” thing. The Rescue CD of the link appears to be booting a linux (variant) kernel.

You can see the code in this link: https://github.com/FOGProject/fogproject/commit/501e2e947abe55f61fec434751e51e517dcba4d4