@george1421 I agree with it all. I can’t imagine a need for latency being enabled by default. I added it to 1.6 for safety. Shouldn’t be hard to port to 1.5.x

Good, the values are changing. there is also an execution time limit that should be set in one of the ini / conf files as well. I believe the setting is max_execution_time which I think takes a value in seconds and defaults to 30. you may want to play with that value to see if you can get a response in a reasonable time. It may take upwards of a minute or two depending on how many entries are getting pulled.

@george1421 Thanks George - After selecting deploy Image and entering username and password is when error occurs can register devices no problem will try last one first thing monday as I am being kicked out of the office - it’s weekend :-)

@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,

@gusto I am not sure I can follow your questions. According to this instructions we need to enable it Options --> Feature --> Nestig - ON Where did you read about “Nesting”? Can see anything about this in the linked wiki article. Did you follow the instructions mentioned in the wiki about Apparmor? Do I need also to install NFS on a host (proxmox)? I have done a LXC installations a couple of years ago but can’t remember this part anymore. If it’s not in the wiki I don’t think it’s needed. That means I have to change pxelinux.0 to undionly.kpxe? Yes, use undionly.kpxe for legacy BIOS machines and ipxe.efi for UEFI machines. Also see https://wiki.fogproject.org/wiki/index.php?title=BIOS_and_UEFI_Co-Existence and my post here: https://forums.fogproject.org/post/130612 I have tentatively installed NFS in LXC (centos 7). Then I wanted to destroy the LXC, but I couldn’t destroy the LXC because filesystem in use. Not sure how to solve this. Not great but rebooting the whole server should definitely fix it.

@tlehrian Great you are bringing this topic up again. Even though I try to keep track of all open topics I still miss one or the other sometimes. Which version of the FOS inits do you currently use?

@george1421 said in FOG/Apache PKI/Certificate Authentication: The issue is that FOG needs a named user in its local database for authentication. Hmmm… okay. I wonder if it would it be possible to pull the alternate name from the certificate offered to be temporarily added to the FOG database. And then if that alternate name is part of an LDAP group, that user would be allowed to log into FOG. I don’t know, just throwing some stuff out there. I know this isn’t functionality that very many people are looking for, if any. Either way, I truly appreciate the assistance and support.

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.

@sudburr In my FOG installation (1.5.5), the value for DATABASE_PASSWORD in config.class.php is in single quotes, so the sed statement for needs to be: sed -i.bak 's|DATABASE_PASSWORD', '<oldpassword>'|DATABASE_PASSWORD', '<newpassword>')|g' /var/www/html/fog/lib/fog/config.class.php I would also like to note that the values in .fogsettings are only initial values for during installation. So it does not matter if you patch the password there really (not 100% sure though).

@WalterT Good to hear you could fix this issue on your own. Too bad that we don’t have any information from you about how the password was, when ich caused an issue! How can we improve this if we don’t have any informaiton on what exactly went wrong?! @Tom-Elliott Possibly it’s the \ but I am not sure. We already changed the password generation method in dev-branchand therefore this won’t be an issue from the next release on.

@brehuffm said in Centos7 hostname change not working: Is it safe to assume that this fix will be in the next Fog image? Not sure what you mean by fog image. The next fog-client version will have that fix included, sure…

@sgoodman Is the server set to Delayed auto?

@Gilberto-Ferraz Try this running this PowerShell script as a snapin. What it does is moves the first non-windows boot selection to the top, in your case it will move “IP4 Intel® Ethernet Connection I217-LM” to the top of the boot order. Works for me…

I don’t have a clue, but could figure it out how to setup a dhcp forwarder on the Aruba/Procurve switch. But I would have to say, if you have a single dhcp server today AND you have vlans in place then you should have a dhcp-helper/dhcp-relay service already installed on your vlan/subnet router. The only reason why you would need to change this service is if you are running dnsmasq service on your fog server (something you would intentionally turn on and configure). If you are not using dnsmasq then changing the dhcp-relay service is not needed. Can you explain a bit more about what issue you are having?

If this is accurate shouldn’t broadcast be 192.168.1.255?