@sebastian-roth thx, at the bottom it’s nearly what I look for.
But how can I set a default parameter as a Path for example in the snapin screen, but overwrite it if I set a parameter…?

regarding the example on the link:

{
“taskTypeID”: <IDOFTASKTYPE>,
“taskName”: “robocopysync”,
“destination”: “<path>”,
“source”: “<path>”
}
Can I use them like this?

And regarding the API: Whats the difference between a SnapinTask and a SnapinJob?

TIA

I searched and didn’t find any information for this…
Maybe I am just blind
Short question: Is it possible to execute a Snapn as task by webapi with then custom parameters/arguments?
I know many workarounds - but if possible this might be cleaner and would be nice
Just as robocopy.bat which some defined parameters…

TIA!

@lee-rowlett said in Executed Snapin Status information in Webinterface:

i have one snapin install several software packages dependant on several variations however with the task state, the engineers know at what it is at… this can be easily achieved with http calls within ur script, you will just need to obtain mac and taskid and then send stateid and hook to display custom states.

Exactly!
Do you have a example http call?

@ally_uk
Just dont install fog with DHCP role.
Then the Server gets his IP by the usual DHCP in your network.
You then need to configure the “real” dhcp inside the network that IPXE boot should be the ip of your FOG.
If I remind correct it was the next-server port 53 setting… depending on your existing dhcp.
Its like in Highlander - there can only be one (DHCP)

I have a quiet similar setup.
finally you just should identify the network card and for example in my debian 9
the isc-dhcp-server is used so I ensure with

INTERFACESv4=“enp2s0”
that the dhcp is only working in the enp2s0 nic.

additional in
/etc/network/interfaces
I got this config for example:

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

source /etc/network/interfaces.d/*

# The loopback network interface
auto lo
iface lo inet loopback



# The primary network interface
# for the 8port switch and FOG automation
auto enp2s0
iface enp2s0 inet static
address 192.13.37.1
netmask 255.255.255.0

# additional gb nic which is used for external
# communication 
auto enp4s0
iface enp4s0 inet dhcp

It’s really quiet strange at beginning to find all the tools which are used here in fog but the nice thing is that all
is somewhere in a usual plain text config.

but my hosts alo should stay offline in the own network (currently) so I also installed a dnsmasq only for no-resolving and that the hosts can reach each other in the hosts switch network.

For me it’s ok and FOG helped me a lot and I have to cross verify all the things I might need and if they are really not there or I just missed to find them

It is more complicated if you need AD from hosts for example like @george1421 already wrote
I had to change to legecy mode for example due to several issues I had in first with uefi in win10 on a new Asus mainboard… maybe I try this again later

Thanks for the answers!
It might be a workaround to have a smb share on the debian system, but how does the progress bar in the tasklist actually work for the current status?
I would prefer a non smb way due to this might influence the tests I would like to run.
Something like RabbitMq / AMQP might be interesting also…

Hello and thanks for this great project first!
I run Fog in version 1.4.4 and basically all works productive. I usualy use it to run application tests on real hardware and recover / start tests for software.
Currently my main question is how to get the current state of a host to the webinterface or requestable by api.
When I start a task of execute a snapin it is started like expected but I would like to get status information from current step back instead of blind testing.
I like the progress information when I deploy an image and would love to have that also for python scripts, batches or other applications.
Any documentation I missed?
Thanks in advance.
Fog Host is a Debian 9 Server and the usual hosts are Win10 based…

TIA!