The figures seem much more stable now, much less fluctuations. Thank you @Quazz !

@EduardoTSeoane It will be interesting to see how optimization works for you. With the size of your campus we may need to split the database from the FOG server to give the sql database more CPU time. We need feedback from large campuses like you have to help with performance tuning of FOG.

@Ken-Zug The only thing I might add to George’s answer is that we might add even newer kernels like 5.8.x to help people with newer hardware. There is nothing specific about 5.6.18 but it was a stable kernel version back then when people started asking about driver support on newer hardware.

The 4.9.x line is rock solid from a Linux and a FOG perspective - been tested many times in hundreds of setups. The 5.6.x and newer kernels have not been used as much…

Don"t worry it’s not for copy 😉
I use FOG, just want to see (untderstand) how wakeonlan is send by FOG. (etherwake or wakeonlan, with options or not etc)
When i have try grep i do mistake syntax this explain why i found nothing on my server.
Sorry thanks for the tips

@Kirill Great, I will add this to the fog-client in the next days!

For the FOG translations you wanna take a look at the files here: https://github.com/FOGProject/fogproject/tree/dev-branch/packages/web/management/languages

The master branch points to the current version (1.5.8 as of now) and for new things we work on dev-branch (as in the link above) or created feature branches. As we don’t have much changes in the language files currently I would suggest you work on what we have in dev-branch.

Best if you grab a copy of the english version and start translating on that. I know there are many lines marked as fuzzy because of changes in strings. I was hoping to clean this up at some point but never got to it so far. If you are keen you are more than welcome to clean this up first. Would be really great!

Holy wow, that cranking out a newly image system about every 30 seconds or so. That is crazy fast. Well done!!

@Uzzi Not on Windows as far as I know. But you can probably script that when installing. Depends on what software you use to deploy the MSI.

@zaboxmaster That command is surely possible if the existing hard drive contents are available. My previous post was only considering a bare metal install where there was no previous windows install to reference. If you have access to the previous disk content and it matches the smbios key then it makes things a bit easier.

If you look at this post for a post install script example you will see a command that is already built into FOS linux called reged https://forums.fogproject.org/topic/8889/fog-post-install-script-for-win-driver-injection/57 In this example I’m poking a value into the registry. While I haven’t looked it may be possible to read with reged too. As for hivesh it could be added if the source code could be found. It could be integrated into FOS Linux. It might take a little work, but its possible if that IS the solution.

edit: man page for reged http://manpages.ubuntu.com/manpages/bionic/man8/reged.8.html

Hi @gn_ro ,

I tested it in the last version 1.5.8 and works fine.

FOG_PingHosts.png

Take note that you must have opened the 445 TCP port in the client and you only see the status in the host page, not in the search page.

I have checked source code and opened a Github issue:
https://github.com/FOGProject/fos/issues/38

@Sebastian-Roth said in LDAP Plugin install:

Did you see Tom’s post? There seemed to be an issue in the version check script on our webserver which led to it saying you are “up to date” eventhough you are running the years old 1.5.5 version. Tom fixed it. You can always be sure the version number in the bottom right corner is the one you have.

Hey sorry about the confusion I did see his comment, but clearly did not understand. It’s a huge relief that we aren’t dealing with a failed upgrade.

Thanks for all your help with this everyone, I have finally got the plugin working. As @Kiweegie suggested early on the password complexity seemed to be the issue. I had made sure there was no special characters in it, but I had made the password obscenely long. Changing it < 24 characters seems to have done the trick.

Apologies for all the confusion and thanks again for all the help.

I’ve removed Arch Linux from the automated tests due to complications within Terraform. These issues were sort of the final straw in my Arch testing efforts.

The Arch community doesn’t supply an official AWS AMI. I had been relying on a privately built AMI that isn’t 1:1 with a manual Arch installation. For perhaps the last half year, my Arch tests were failing but the installer worked if you tested it against a manually setup Arch installation. This can only be due to differences between the AMI I was using and a manual installation.

The Arch community is vehement about only providing help if you follow their installation instructions on their wiki exactly. Because of this, when I asked for some help sorting out the issues, they were not willing to help.

Until someone with some Arch prowess can put some time into helping with this, Arch Linux will not be included in the automated tests.

@sascha735 If you installed FOG using the git method, switch to the dev branch and reinstall fog. That will put you on a prerelease version of 1.5.8 that does support Centos 8 and Debian 10.2 (I think).

cd /root/fogproject git checkout dev-branch git pull cd bin ./installfog.sh

That should put you on version 1.5.7.85 (or later)

When FOG 1.5.8 is released (should be some time later this month) you will then need to do the following to switch back to the master branch.

cd /root/fogproject git checkout master git pull cd bin ./installfog.sh

@Tom-Elliott ok, no worries

Finally merged all the work into dev-branch. Done.

@Sebastian-Roth if my memory serves correctly, GUI watcher was a part of the now very old client

@Quazz Not sure from the top of my head. Thanks for finding this!! I will take a look later on.