@Sebastian-Roth I added the new lines to my /etc/apache2/sites-enabled/001-fog file, entered my credentials and waited 10 minutes… No change, still getting an HTTP/503 response.
I downloaded the script to the FOG server, ran ./updateIP.sh, and got the following results:
Updating the IP Settings server-wide.
A password was not set in /opt/fog/.fogsettings for mysql use.
Updating the IP in /tftpboot/default.ipxe
Backing up /var/www/html//fog/lib/fog/config.class.php
Updating the IP inside /var/www/html//fog/lib/fog/config.class.php
Updating the fields inside of /opt/fog/.fogsettings
I tried to log in again, and it’s still spinning around (although, it’s only been 2 minutes since I ran the script and tried to log in).
EDIT: It’s working now! After running the script, I also restarted Apache, PHP and MySQL, then tried again:
@loosus456 Yea, I have no objection to that. But I can’t get the Taskbar Customization to work (even after fixing the .xml file that is generated), so I gave that part up. It resets the taskbar to just Edge and Explorer, and allows users to customize it how they wish.
you need to apply taskbar customs via group policy, if so the user has change rights:
If you use a provisioning package to configure the taskbar, your configuration will be reapplied each time the explorer.exe >process restarts. If your configuration pins an app and the user unpins that app, the user’s change will be overwritten the >next time the configuration is applied. To apply a taskbar configuration and allow users to make changes that will >persist, apply your configuration by using Group Policy.
Is it possible to only upgrade debian , or is it better to reinstall everything from scratch ?
You could do either. There are pros and cons for both. That said - I don’t test upgrading Debian that already has FOG installed - I only test installing fog on upgraded Debian. And upgrading always involves some risk.
@lukebarone Great to hear that you intend to participate in this! You can do it either way. I am pretty sure both ways should give us the same results but I’d recommend using the FOG debug mode as you are using the very same tools as would be used in the initrd later on anyway.
Schedule a task for those clients you want to check. Does not really matter if it’s an upload or deploy task. But just before you create the task check “Run as debug task”. The PC will boot up as normal into the FOG system but then drop you to a shell. The you can just run the command and post results here. Please make sure to double check when typing the results. Thanks!
Also, sounds like you need to update the fog server too. 7981 is behind, we already have release candidates.
I’m going to bet this is the solution… I’m rebuilding the image now, and will disable the service (I never saw that Wiki page before - lots of good info). I also just updated to the Release Candidate (using Git), so hopefully that combination works.
@lukebarone You should use the file that works with most of your computers (most likely undionly.kkpxe) and for the rest should set DHCP reservations that just consist of the correct boot file, not IP.