Excellent George, I will give that a try. Thanks for the feedback!

@tlehrian It would be really great if you could test this fairly soon so we have a little bit of time in case it needs further work. The earlier we know the better! We can’t guarantee a quick fix some time in January when you really need it.

https://github.com/FOGProject/fog-community-scripts/tree/master/RenumberImageIDs

@execcr said in Fog and pxe boot Esxi 6.7u3 installer on HPE Server can't pass k.b00 module: i just spin up a VM with UEFI bios and E1000E adapater and tried to deploy esxi 6.7u3 to that vm and get past the loading modules stage and i can actually install esxi here. From what you have told us so far I think this might be some problem with iPXE booting in the other VM. Can you please give us more details on what setting(s) is/are different between the one that works and the one that doesn’t properly load.

Thank you for the response, I appreciate it. I’ll give that a try.

@Sebastian-Roth said in Database Stress when cloning on Big Environments: @EduardoTSeoane I’d be very interested to hear if this quick fix helped to ease the DB load. We might consider make this value configurable through the web UI then. Good Idea. When I get some tests on production I’ll post it here.

@george1421 Morning George the issue is resolved - it was the ‘-M’. There was no <space> at the beginning so iPXE clearly doesn’t like ‘-’ at the beginning. Thanks again :-D

@fogQuestions said in Can fog deploy images to a single partition?: However, whenever I deploy images to from my FOG server to my computer, the iPXE software gets wiped by my image. May I ask why you have iPXE installed on disk at all? Usually this is send to the client on PXE boot on the fly and there is no need to have it on disk. Can fog deploy images to a single partition? If so how? Yes you can define an image in the web UI to capture/deploy only one single partition. The problem with this is that on the target machine you already need to have the correct partition layout set from an earlier deploy as we don’t touch that but simply deploy the contents of that one single partition set in the image definition.

@vic60400 Would be interesting to hear if (and how) you were able to exchange the certificates. Other users might find it very helpful.

Hey @Daniel-Miller and @george1421 thanks again for your effort in helping me figure this out. I think the complexity (for me) for what I was about to do scared me into thinking of a roundabout approach to solving this issue. I think I found a better solution than what I was originally trying to do (and WAY simpler). I will post here in case this will be of use for anyone in the future. Rather than appending a date to the hostname so I can change the computer name I decided to start out with the date appended to the hostname so that renaming the computer would be exactly how I want it to be then for my other requirements (adding the user to be admin of the computer) I simply removed the date from the hostname to come up with the username. Basically, if my username is bobsmith and today’s date is 2019-12-06, I will name the host: bobsmith191206 then in my Powershell script I just need to set $userName = $env:computername -replace '[0-9]' then the hostname remains bobsmith191206 and now I have a variable $userName that now equals BOBSMITH Anyhow, that is one of those… so easy it is dumb solutions. Not sure why I didn’t think of it earlier. Thanks again you guys for helping me to think outside of the box I stuck myself in.

Found and should be fixed if you do the latest pull. Thank you,

Of note, I’m calling it 1.6 because when we do release it, that’s what this will become. It is using the current latest version (1.5.7) and the .XXX after is the number of commits ahead of the master branch the working-1.6 branch is at.

@franck25 said in How to boot uefi on ltsp server via ipxe fog: I find myself facing a problem of boot on my server “ltsp ubuntu” Please take a picture of the screen where we see what goes wrong and post that here.

This has been added. I’ve also tested it for functionality. In the case a color is not defined it will use the original color schemes. Of note, for 1.6 I did add a bit better method for distinguishing colors between nodes. So the variance should be a lot better. Of course you can now set your own colors as well. Thank you,

I thought of a bit of an easier way to explain the field mapping between the kernel parameters ( cat /proc/cmdline ) and the grub menu. Here is a graphic that explains how to map the values between the two different booting methods.

Hi Sebastian - interestingly when I switch to the 32bit kernel everything woks fine so as far as were concerned the problem is solved

@jhumpf Which version of FOG do you have installed? Can you please take a picture with a bit more of what you see on the screen. I don’t really understand where you are in the web UI to get this picture.

@Shiro228 We didn’t have the time to implement printer management on Linux yet. You are more than welcome to work on this.

@george1421 Thank you so much ! It works well ! Have a good day.