Because I’m not affiliated with FOG in any official capacity and I’ve never actually contributed to it in any way before, I completely avoided making any actual changes to the source. I have noticed that there could be a couple of things that could make the docker implementation a little easier though, specifically around the FOG services themselves. I’m not entirely sure they are completely container friendly, but I really need more hands on this to test it out thoroughly.

Also, I used Debian 13 as the base image for this and it ends up being pretty large (2.5GB). It might be possible to shrink this with alpine-linux but I didn’t want to break a bunch of stuff and then have to spend more time chasing those bugs. Anybody that wants to work that angle, please feel free.

@Frode-Woldsund

I created an image. Give it a go and let me know

https://forums.fogproject.org/topic/18000/unofficial-docker-image-beta

@JJ-Fullmer @ramone

I created an image, check my post here

https://forums.fogproject.org/topic/18000/unofficial-docker-image-beta

I do believe it’ll be able to utilize an existing DB, but I haven’t tested it yet.

please check my post here

https://forums.fogproject.org/topic/18000/unofficial-docker-image-beta

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