Feature Request

• P

  [solved]Set Multicast group task with a given name or even the group name
  • processor  

  9
  0
  Votes
  9
  Posts
  85
  Views

  P

  @Sebastian-Roth, @Tom-Elliott Many thanks! Works exactly like I needed ! @Tom-Elliott I’ll take a look at the 1.6 asap
• T

  RBAC functionality
  • The Dealman  

  11
  0
  Votes
  11
  Posts
  104
  Views

  T

  @Fernando-Gietz Okay I got it working. You guys are awesome keep it up!
• S

  Multicast udpcast options
  • Sebastian Roth  

  7
  0
  Votes
  7
  Posts
  130
  Views

  

  @Tom-Elliott said in Multicast udpcast options: Also, the recommendation for the max-bitrate issue is it already exists and is based on the Master Storage Node’s bitrate setting. The rexmit-hello-interval should also be added based on the Master storage node (as opposed to global values.) This is simply because the global value means EVERYTHING that does multicast will use the same rexmit and bitrate settings. Having it per master storage node makes this much more dynamic and site specific. You are right. Is better have a configuration per node than a global one. I have done: #git diff working-1.6…working – schema.php And return me a lot of changes :( The new line in schema.php will be like this: // 264 $this->schema[] = array( "ALTER TABLE `nfsGroupMembers` ADD COLUMN `ngmHelloInterval` " . "VARCHAR(8) AFTER `ngmMaxBitrate`", ); I define the ngmHelloInterval like string and not like integer.
• 

  Create users who can only use the function WOL
  • Lenain  

  31
  0
  Votes
  31
  Posts
  265
  Views

  

  @Lenain I think that your only option is develop a new plugin to do this.
• 

  file format and compression option request
  • Junkhacker  

  8
  0
  Votes
  8
  Posts
  345
  Views

  

  @Junkhacker further testing suggests that everything works fine without the --ignore_crc flag we have set in all restore operations. i’ve also learned that due to a bug in partclone 2.89, the checksums it was making were practically useless. if/when we upgrade to the newer version of partclone, we might want to consider disabled checksums to be the default, since we’ve been, in essence, operating without checksums all along.
• 

  Reports with filters
  • Fernando Gietz  

  1
  0
  Votes
  1
  Posts
  85
  Views

  No one has replied

• J

  Option to delete files when deleting multiple images / snapins.
  • jflippen  

  9
  0
  Votes
  9
  Posts
  250
  Views

  

  @Sebastian-Roth said in Option to delete files when deleting multiple images / snapins.: I really like the idea although it would mean that users need to confirm twice. I think it’s fine. It’s like Tom said, very serious to mass delete images.
• A

  Spk Packet for synology
  • Aigor  

  3
  0
  Votes
  3
  Posts
  114
  Views

  A

  @george1421 Thanks for the answer, do you know you can install DSM over VM or into no synology hardware? check xpenology
• J

  Detect if PXE client is already iPXE
  • jms  

  3
  0
  Votes
  3
  Posts
  320
  Views

  J

  @Sebastian-Roth Thanks that all makes sense. Thanks Sebastian — from my point of view I could still get rid of TFTP by recognizing either UEFI HTTP Boot (physical hardware) or existing iPXE ROM (in my Nutanix VM) vi DHCP headers (vendor class / user class) and in either case chainload the FOG iPXE binary (with “params” enabled) via HTTP and eventually perhaps HTTPS. This should be pretty straightforward, I’ll see if I can work it out and I’ll post back - may be worth a wiki article. Now … the next item to tackle would be replacing FTP (vsftpd) with SFTP :-) Feel free to close this thread if it’s no longer appropriate as a “feature request”.
• 

  Under dual systems Boot from not default partition
  • Fernando Gietz  

  4
  0
  Votes
  4
  Posts
  134
  Views

  

  @Fernando-Gietz So lets think about it a bit. in a way you want to tell the pxe booting client (in iPXE) don’t boot of the normal boot loader, but boot from a different partition (lets use /dev/sda6 for discussion). By default sanboot will boot from the first hard drive, and uefi will boot via refind. Grub can boot uefi. I don’t know if grub distributed with FOG can boot uefi. If you set the exit mode for a host to Grub first hard drive the iPXE menu is created this way: chain -ar ${boot-url}/service/ipxe/grub.exe --config-file="rootnoverify (hd0);chainloader +1" || goto MENU I’m wondering if someone could repurpose the setting rootnoverify (hd0);chainloader +1 to actually load /dev/sda6? The other challenge is that grub.exe is probably a bios mode application where we would want to use grub.efi for uefi. Again this is just me thinking out loud about the issue.
• R

  Adding capture menu to fog
  • robertkwild  

  3
  0
  Votes
  3
  Posts
  241
  Views

  S

  @Tom-Elliott Maybe add another user confirmation to make clear this will overwrite an existing image…?
• D

  View FOG logs from web interface?
  • Duncan  

  4
  0
  Votes
  4
  Posts
  255
  Views

  

  @Tom-Elliott Store them in the database and have a daily cron job that cleans out logs older than N days (user defined). If FOG were to switch to MariaDB 10.3, the TokuDB engine would be available for use. TokuDB has in-engine compression. The compression savings is pretty staggering compared to InnoDB. TokuDB does not support foreign constraints - and because the FOG db doesn’t use them, we are A-OK there.
• D

  Compatibility Test menu - add item - show queued tasks; run queued tasks now
  • davemc  

  2
  0
  Votes
  2
  Posts
  162
  Views

  

  The compatibility menu is accessible to a host machine when there are no tasks for the host. When you have a queued task the host would automatically boot into it.
• D

  Schedule image on next cold/warm boot
  • dsloan.ethra  

  4
  0
  Votes
  4
  Posts
  252
  Views

  

  @dsloan-ethra Thanks. Also another option would be to just stop the FOG Client service via a snapin.
• P

  Option to edit Windows registry via FOG PXE boot?
  • psyfer9983  

  10
  0
  Votes
  10
  Posts
  1374
  Views

  

  @psyfer9983 There isn’t a tutorial on what you ask, because poking about in the windows registry using a non-windows OS is not typically a good choice. But with that said, I can give you the match and can of gas. What you do with them is up to you. In this post there is an example of how to use the reged linux utility. https://forums.fogproject.org/topic/8889/fog-post-install-script-for-win-driver-injection/4 From that post here is the interesting snippet of code. regfile="/ntfs/Windows/System32/config/SOFTWARE" key="\Microsoft\Windows\CurrentVersion\DevicePath" devpath="%SystemRoot%\DRV;%SystemRoot%\inf;"; reged -e "$regfile" &>/dev/null <<EOFREG ed $key $devpath q y EOFREG You can probably stack the ed commands so you only need to call reged once. Here is a help page for reged: http://manpages.ubuntu.com/manpages/bionic/man8/reged.8.html So once you have the bash script you need, you can call it during the post install actions after the image is placed on the target hard drive and before FOS exits and reboots. The first link shows you how to update/attach scripts to the postinstall script (which can be used for driver deployments).
• L

  Deploy associed image on boot menu
  • lebrun78  

  4
  0
  Votes
  4
  Posts
  323
  Views

  L

  We have made a special setting in deploy.image menu for the computers of the room. Then login and password are not requested to access to deploy menu. #login params param mac0 ${net0/mac} param arch ${arch} param hostname ${hostname} goto host_${hostname} || goto autres :host_bug :host_win10-3 :host_i207m01 :host_i207m02 :host_i207m03 :host_i207m04 :host_i207m05 :host_i207m06 :host_i207m07 :host_i207m08 :host_i207m09 :host_i207m10 set username userlogin set password userpassword params param username userlogin param password userpassword param qihost 1 isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme goto fin :autres login params param username ${username} param password ${password} param qihost 1 isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme :fin
• P

  Retry snapins on error?
  • p4cm4n  

  2
  0
  Votes
  2
  Posts
  170
  Views

  

  @p4cm4n You could probably use a snapin-pack to deliver the Chrome MSI as well as a powershell script. The powershell script could do a small loop with a maximum of say three iterations. Each time, it can try to install Chrome and then check if it’s installed. If the correct version is installed, exit the loop.
• A

  SOLVED Web interface SSL
  • astrugatch  

  9
  0
  Votes
  9
  Posts
  1157
  Views

  

  @astrugatch all -S does is setup the vhost file so it will redirect to requests to https. The -c specifies which private key to use. If you need the installer to create keys for you, you can use the -K switch, and if you need a new CA you can use -C switch. The installer already creates the keys for you by default, and the fog client looks for the servers CA key for validating the client is talking to the proper server. If you want to use your own self signed cert, I might recommend using the servers CA so it works with that being the only difference you use. As we do create the keys, if you’d like to use the fog generated key, the installer can just be ran with the -S argument. The only thing is recommend for that case is to import the ca cert so you dont have the self signed error. Machines with the fog client installed should see the green padlock as we do import the ca as I said earlier.
• 

  Deploy only partition
  • Fernando Gietz  

  4
  0
  Votes
  4
  Posts
  319
  Views

  

  If the imagesize is empty, FOG only shows me the option to capture or deploy all image. If the imagesize is not empty, FOG shows me the options: all image or only one partition
• 

  Release plan for FOG
  • TrialAndError  

  8
  0
  Votes
  8
  Posts
  535
  Views

  S

  @trialanderror I get where you’re coming from, but I agree with Tom that this for free software would be too much of a nightmare to do LTS support on. I mean, there isn’t even a support team. I’m glad they don’t spend a ton of time going back to old codebases and backporting it. The installer does a good job of not blowing stuff up and the db schema typically upgrades fine too. I say “good” because it isn’t totally transparent about what’s going on, so you do actually have to be a bit familiar with the upgrade process to make sure that you don’t do anything that could lead to loss of data.