@JJ-Fullmer Dear Fullmer, thanks in advance for your intervention.

Unfortunatly in the machine that run my fog container there is another mysql database listen on port 3306.
This is not a problem, i just semi-resolved creating a non-privileged/shared network host mysql container with no exposed port -> place fog container and this database container in a same network (they can ping each other with fqdn) and i’ve just modified the /opt/fog/.fogsettings with your suggestion in the past, but the solution doesnt work:
The installation goes fine, but the result is a blank http page that it say: database error. (something like that).
I think (but is only supposition, im not absolutly a developer) that there is written php scripts that must to be point to a localhost database (something in /var/www/html/fog/*).

This problem is born because the fog container must be in privileged mode, with the same network namespace as the host, and in this host there is another database already.

Thanks for confirm me the inevitable death of the container version of fog. it really hard to containerize this application without setting privileged mode and/or share the host network. and the huge problem of systemd processes make this containerizzation very difficulty to maintain.

Thanks for the patience

Haven’t really found a great fix here, I’d love to get some logging to work. But this seems to be working better than before. It moves the argument from the calling command and embeds it into the Snapin Arguments:

Snapin Type: Normal Snapin Snapin Run With: powershell.exe Snapin File (exists): runCmd.ps1 Snapin Arguments: "%ProgramFiles%\FusionInventory-Agent\Uninstall.exe /S"

the command in runCmd.ps1 then no longer passes an argument so needs to be changed to:
start-process -filepath "$exe"

@george1421 Thanks! I wonder if a chat bot could help with reading through what worked and make a tutorial.

@fabritrento As you stated it, UAC is preventing access. There is no real way to fix user cleanup that I’m aware of.

We have started working to remove the features that we cannot manage.

case 'service-autologout': $this->serviceAutologoutPost(); break; case 'service-displaymanager': $this->serviceDisplaymanagerPost(); break; case 'service-hostnamechanger': $this->serviceHostnamechangerPost(); break; case 'service-hostregister': $this->serviceHostregisterPost(); break; case 'service-powermanagement': $this->servicePowermanagementPost(); break; case 'service-printermanager': $this->servicePrintermanagerPost(); break; case 'service-snapinclient': $this->serviceSnapinclientPost(); break; case 'service-taskreboot': $this->serviceTaskrebootPost(); break; case 'service-usertracker': $this->serviceUsertrackerPost();

Sorry that it isn’t “pretty” but this is the code moving forward. You can think of anything not on this list, but still accessible in the 1.5.x versions as being deprecated (to non-functionality)

@baovipboy156
thanks for your input, but cannot get it working with it…
would you please post more details and steps by steps to get it work, please…

iventoy1.20
fog 1.5.10.1615

@Tom-Elliott

Yes, I even spun up a new FOG VM where the mount points were created before FOG was installed to makesure the FOG installer created all the files and set permissions.

edited - words

@Tom-Elliott yay, thank you

@Tom-Elliott Looks like its working now, thank you!

@JJ-Fullmer But should it just be a backup, or just a history that can be reverted between?

How many iterations should we allow? (So we have to track by version number/date, and that there are those different versions, and where they’re located, and dynamically update the “location” path to which ever is the most current version.)

Just thoughts out there, but complicated and too simple to screw up. It really needs a schema thought process (maybe a plugin could do this?)

@Tom-Elliott
Hi Tom,

set as default, but how we can run this as a task like deploy, capture or disk or other tasks ? We have clients, they are not online at the moment. On next boot they should automatically go to the correct PXE Menu entry.

BR
Klaus

@mark29 The dynamic nature of images and systems FOG doesn’t track the IP address of systems, anymore. In really early versions it did track the IP address at least but hasn’t for quite some time.

That said, I think what you’re asking for is possible but it would require a Snapin to do so, and even that would be ugly. (If it truly must be static, this would be the best route in the end if you’re requiring only using FOG to manage this I think.)

You would create a Powershell scriptp that utilizes the Set-NetIPAddress statement and probably need a lookup to figure out which device needs to be using which IP address and all (that’s really the ugly part.)

The best case, though, I think, is to utilize DHCP reservations, as this would not require any special programming or even a snapin for that matter (another kink that can potentially not work appropriately.)

The DHCP server options of your AD controller, can be used to define specific IP’s in an automated way, rather than rely on a program to set the IP address.

@Tom-Elliott

Thanks Tom. Understood.

An Idea I had was programming this into the BIOS or requesting HP to make a BIOS/UFEI which has this feature of “channels”

Or using a boot file, such as with secure boot, but that would require HP or Dell or whichever PC manufacturer to make boot files for secure boot.

but this would be out of the scope of the project.

I do appreciate your input though.

Regards,

Matt

@Tom-Elliott My apologies. So what I meant is that, the inventory information is sent in the mail.

So for example the following information will come with the mail:

System Manufacturer Dell Inc.
System Product Latitude E5470
System Version Not Specified
System Serial Number H857NC2
System UUID 4c4c4544-0038-3510-8037-c8c04f4e4332
System Type Type: Laptop
BIOS Vendor Dell Inc.
BIOS Version 1.29.4
BIOS Date 12/21/2021
Motherboard Manufacturer Dell Inc.
Motherboard Product Name 0VHKV0
Motherboard Version A00
Motherboard Serial Number /H857NC2/CN129636920214/
Motherboard Asset Tag Not Specified
CPU Manufacturer Intel® Corporation
CPU Version Intel® Core™ i5-6300U CPU @ 2.40GHz
CPU Normal Speed Current Speed: 2400 MHz
CPU Max Speed Max Speed: 2400 MHz
Memory 7.66 GiB
Hard Disk Model SATA3 256GB SSD
Hard Disk Firmware U0506A0
Hard Disk Serial Number 2021120601747
Chassis Manufacturer Dell Inc.
Chassis Version
Chassis Serial H857NC2
Chassis Asset Not Specified

Hello
We primarily use Fog for software management on the clients
This works relatively well, even if it wasn’t intended for that purpose.
We would still like to keep this as this function is very convenient for us.

You can certainly add the version number to the name.
I actually wanted to avoid this because I can’t guarantee that there might be problems here in Fog if the name of an assigned packet changes all of a sudden.

To the node status
I currently know that you can read this in the logs

One field in the dashboard for each storage node would be enough for me to operate it
what the status is

Example
synchronization
Ready
Error

If there are errors, you can read them in the log.

Thank you for the great work on this project

@rpeterson ok, so the pcbios is sending characters to the serial port and CONSOLE_SERIAL is also sending characters to the serial port. This is what I’m guessing because of this post: https://superuser.com/questions/1358359/putty-serial-port-access-to-rs-232-console-showing-double-character-display-with

So I have to ask the question. Have you tested the fog stock ipxe boot loader? If PCBIOS is redirecting what would go to the screen out the serial port then that is all you should need. Now once you get the fog ipxe menu to display correctly, when you pick a menu item on the ipxe menu and bzImage and init.xz are loaded that is where the kernel parameters console=ttyS0,115200n8 come into play. You don’t need to edit bootmenu.class… just go into FOG Configuration->FOG Settings->Kernel Parameters and add in that line. It will be added to every computer that pxe boots into fog.

@hancocza Its a bit complicated, but the short answer is that the inits will need to be updated to support NFSv4 then its needs to be paired with the current kernel. You will have this issue with usb booting or booting via PXE. The default inits don’t support nfsv4. The answer is they can be fixed.

@Developers can we enable the inits to be compiled with NFSv4 support but not update the scripts to include NFSv4 support. This way the FOG Admin can just unpack, add the settings and repack the inits because everything would be already compiled in. Or simply include my hack below to enable a kernel variable to enable nfsv4 and only have one master inits package.