Categories

• Announcements

  Get the latest news on what's happening.
  168
  Topics
  706
  Posts

  T

  @Tom-Elliott said in Ubuntu is FOG's enemy: apt-get -y remove unattended-upgrades This saved my bacon, thank you very much, first command failed but second one worked, i have also run the unattended-upgrades command, once again thank you.
• General Topics

  View tutorials or talk about FOG in general.

  General

  Tutorials
  1970
  Topics
  15799
  Posts

  S

  @ty900000 I don’t think anyone has tried this before but I am sure it can be done. It’s not as straight forward as one might think because it’s not just the web UI accessed by the browser but also PXE booting clients and the fog-client sending requests to the webserver. If you are keen to give it a try we can support you to make it work. Start reading here: https://stuff-things.net/2015/09/28/configuring-apache-for-ssl-client-certificate-authentication/ I’ll try to give you more details on how to generate the certificates on you FOG server tomorrow.
• Technical Help

  Get help with your FOG system.

  FOG Problems

  Hardware Compatibility

  Windows Problems

  Linux Problems

  Mac Problems

  General Problems
  9450
  Topics
  93281
  Posts

  

  @WalterT the password is randomly generated at install time. Every now and again, however, this random password has some codes in it that are literally interpreted. I had something (t%Pr\rAs[]E and it stripped the \r due to this. I don’t know why it did this but that was my issue. Look at the storage node password in the GUI. Copy to notepad. Look at the file on the server under /opt/fog/.fogsettings and make sure the password there is the same as the one you just copied to notepad. Look at the file on the server under /var/www/fog/lib/fog/config.class.php and make sure the ftp password there is the same as the one you copied to notepad.
• Developers

  Report bugs, request features, or get the latest progress.

  General

  Feature Request

  Bug Reports
  2047
  Topics
  19285
  Posts

  T

  @Daniel-Miller said in LDAP Bind during Login: Now, if you happen to know what the DN suffix will be, an alternative to the search and bind method would be a direct bind where the required static information is added to the username to create the DN that is proffered to LDAP for the bind request. Right, this is something like I was thinking about, especially on a domain-joined machine. I suppose I didn’t phrase it properly or concisely - that’s my bad. No particular reason for this functionality; just didn’t know if it would be something worth adding in or how difficult it would be to code into the plugin. No worries! Thanks for the quick reply!