General

• J

  [HELP WANTED] Client Internationalization
  • Joe Schmitt  

  45
  2
  Votes
  45
  Posts
  9571
  Views

  S

  @scosta Thanks! Will add this. Just have not had the time to do so and not sure when that will be. But be assured, this is not lost.
• J

  Firewall Configuration
  • Joe Schmitt  

  24
  2
  Votes
  24
  Posts
  12961
  Views

  

  the firewalld configuration no longer works on Fedora 21. The commands succeed, but at least http is blocked still.
• J

  SELinux Policy
  • Joe Schmitt  

  19
  2
  Votes
  19
  Posts
  14802
  Views

  

  Bumping this - it would be so nice to have SELinux enabled as a standard configuration.
• C

  FOG Status
  • Chuck Syperski  

  59
  0
  Votes
  59
  Posts
  33738
  Views

  

  Nope it’s still heavily in the beta phase, I bet when we do have an idea we will post it on the forums or on the main site letting everyone know we are close. There is a thread you are more than welcome to monitor it can be located here ->[url]http://fogproject.org/forum/threads/latest-fog-0-33b.6476/[/url]
• M

  API updated?
  • maikBat  

  4
  0
  Votes
  4
  Posts
  46
  Views

  S

  @maikBat said in API updated?: I have updates from 2017 What do you mean by that??? Which version of FOG do you use?
• 

  FOG Client Last Check-in Report
  • fry_p  

  7
  0
  Votes
  7
  Posts
  70
  Views

  

  @fry_p Maybe too late, but in addition to complete a few: You can configure the fog client to delayed-auto and to reboot the service on each error with the commands below recommended before start it: sc.exe config FOGService start=delayed-auto sc.exe failure FOGService actions= restart/60000/restart/60000/restart/ reset= 120.
• S

  Database security
  • Sebastian Roth  

  9
  1
  Votes
  9
  Posts
  154
  Views

  S

  Starting to collect information on password setting mechanisms for different versions of MySQL and MariaDB in the initial topic description. Please post here if you know of other things.
• A

  LDAP plugin - apache2/error.log - password in plaintext
  • antonionardella  

  6
  0
  Votes
  6
  Posts
  83
  Views

  S

  @antonionardella You are right this is not good that it prints the full credentials in the logs. But the error you have is caused by the php-ldap module not being installed I guess. That shouldn’t happen at all if you don’t mess with the FOG setup. I am not sure we can prevent if from showing this in the logs…
• 

  Arch install issue 06-29-2019
  • Wayne Workman  

  1
  2
  Votes
  1
  Posts
  38
  Views

  No one has replied

• M

  SOLVED PXE Boot could not boot
  • maikBat  

  3
  0
  Votes
  3
  Posts
  39
  Views

  M

  Today I learned that when adding a new item to PXE menu “Menu Item” cannot have spaces. Instead type “New Item” you should type “NewItem”. When I checked the PXE config file using the link was kind of evident that this was the problem and in effect it was. Thanks for the help
• M

  FOG install overwrites /etc/exports with no warning
  • mechalas  

  14
  0
  Votes
  14
  Posts
  113
  Views

  

  @Wayne-Workman said in FOG install overwrites /etc/exports with no warning: In what scenarios do you see having two? If you were to install fog side by side with another product that supports nfs. What is the likelihood of two installs creating an entry with fsid of 0 or 1? We see that issue today when someone wants to create a second nfs share on the fog server and clones what is currently there but updates the paths only.
• 

  New Plugin: Host Status plugin (1.5.6 FOG version)
  • Fernando Gietz  

  14
  4
  Votes
  14
  Posts
  185
  Views

  

  @fry_p You can change both, line 110 and 114. If all works fine, when you are in FOS, must return 111 code. If you are under windows, must return 0. which value return when you are under windows? 0 or 6? If the value is 6, which OS are you using (Windows 7,8,10)? Another oddity is that the built in host pinging on the host list page is working properly and even detecting these are windows clients. The hostStatus plugin uses the same code that FOGHostPing daemon, if the daemon detects fine the status, there is something that doesn´t work correctly. You have 1500 hosts, the daemon launchs one ping per second then the status is updated every 25 minutes, in your case the status info is not very reliable. In my opinion is better disable this daemon.
• T

  Client Side Scene Fog?
  • tutu10  

  2
  0
  Votes
  2
  Posts
  43
  Views

  

  @tutu10 i think you posted this to the wrong forum…
• 

  Fedora 30
  • Wayne Workman  

  1
  1
  Votes
  1
  Posts
  55
  Views

  No one has replied

• S

  Circumnavigate fog user issues
  • Sebastian Roth  

  29
  3
  Votes
  29
  Posts
  490
  Views

  S

  Did some more testing and will merge this into dev-branch now before the new release. Have tested on CentOS (existing installation and fresh) as well as Debian (fresh installation). Should be good to go.
• T

  Image capture schedule every day at 8pm
  • tejen  

  3
  0
  Votes
  3
  Posts
  40
  Views

  S

  @tejen While @ckasdf is totally right about saying that it sounds like you might be using FOG as a backup tool and it’s not a great idea, I can still tell you that you can create scheduled jobs. Just do as if you’d manually create a capture task but on the last step instead of do an “instant task” click schedule as cron task.
• K

  Full Host Registration - Group Associating - AD GroupEntries deleted after add host membership!
  • klaus.jauk  

  2
  0
  Votes
  2
  Posts
  35
  Views

  S

  @klaus-jauk In FOG groups are not like you might be used from other software. It’s more like a tool to push out settings to a group of hosts but it’s mostly not a persistent settings thing where you store information for the whole group. For AD settings, if you set those through the group you’ll see that the values will be shown in the group AD settings as long as you don’t change a value for any of the single hosts. When you do this the value from the group AD settings will disappear. This is the concept of FOG groups. Search the forums for “persistent group” and you’ll find a lot of information on this. I see that it’s a bit unfortunate in the case you describe where you register a new host and join that to the group. But on the other hand you’ll still have all the values set for all the other group members. You just don’t see it in the group AD settings view anymore.
• M

  Write scripts to do fog work
  • Mark krikunov  

  3
  0
  Votes
  3
  Posts
  55
  Views

  M

  @Sebastian-Roth Okay, I will give it a try. Thanks for the response.
• 

  USB to Ethernet dongles host registration
  • vervoordeldonk  

  10
  0
  Votes
  10
  Posts
  96
  Views

  

  @vervoordeldonk What we are finding is the mainstream hardware vendors (dell, hp, lenovo, intel nuc so far) do an excellent job of making each system unique so coming up with an alternate method of identification isn’t a problem. The issue is like the system below System Manufacturer xxxxr System Product TMB-3010 System Version R0M0 System Serial Number To be filled by O.E.M. System Type Type: Notebook BIOS Vendor American Megatrends Inc. BIOS Version 1.00/636G00WPC76508 BIOS Date 05/06/2016 Motherboard Manufacturer xxxxr Motherboard Product Name WEB-889A/WEB-889AA Motherboard Version R0M0 Motherboard Serial Number To be filled by O.E.M. Motherboard Asset Tag To be filled by O.E.M. CPU Manufacturer Intel® Corporation CPU Version Intel® Core™ i5-3210M CPU @ 2.50GHz CPU Normal Speed Current Speed: 2500 MHz CPU Max Speed Max Speed: 3800 MHz Memory 3.74 GiB Hard Disk Model 2.5" SATA SSD 3ME3 Hard Disk Firmware S15A19 Hard Disk Serial Number xxxxxxxxxx000025 Chassis Manufacturer xxxr Chassis Version Chassis Serial To Be Filled By O.E.M. Chassis Asset I put the lower case “x” in just to mask a few values, but as you can see there is nothing unique on this system from the next system from the same manufacturer other than the disk serial number. I have a few examples of other systems that are very similar. One solution is to go ahead and use the mac address as part of the mix for system identification. In that case we would be no worse off than we are today by only using just the mac address. We also want to bring in the asset tag value so at the very least if FOG can’t identify the system the IT tech will need to populate that field to create a unique ID for that system. (sorry I’m a bit thinking out loud here)
• M

  FOG API
  • maikBat  

  19
  0
  Votes
  19
  Posts
  2054
  Views

  

  I’ve updated the rout.class.php in 1.5.X branch (dev-branch) I will ask @MarkG if you would like to install this to see if it address what you need directly? I know you don’t want to move to the alpha build, but dev-branch is where the bug fixes found since 1.5.5 have been addressed. If anything, you can simply copy this dev-branches router class with: wget -O /var/www/fog/lib/router/route.class.php https://raw.githubusercontent.com/FOGProject/fogproject/489ba2952f5750e1483083eedade17dde6bb3cd8/packages/web/lib/router/route.class.php This should allow you to clear out items such as snapins with the code you were using: { "snapins": [], "printers": [1,2,3,4] }