@Quazz said in Group Snapins:

You might be interested in post download scripts for this. Will accomplish basically the same thing, but in a more universal manner.

A post install script is the best for pushing drivers, since the target computer has access to the network using FOS, once windows boots and the drivers are not loaded you are off-line.

There are two tutorials that will help you.
https://forums.fogproject.org/topic/4278/utilizing-postscripts-rename-joindomain-drivers-snapins

https://forums.fogproject.org/topic/7391/deploying-a-single-golden-image-to-different-hardware-with-fog

This one has some background info that is useful.
https://forums.fogproject.org/topic/7740/the-magical-mystical-fog-post-download-script-under-construction

@Wayne-Workman Awesome, thanks for the heads up. I will look around to see if I can find it

@ITCC it is set how it’s set because how it works. It’s not a “host” thing as we don’t have a decent mechanism, in my opinion, to find hosts. Because hosts are found by MAC address the simplest mechanism is to use to Mac table to work against.

@Tom-Elliott That’s exactly what I needed thanks Tom.

nfsiostat will be the tool I use to demonstrate how latencies can degrade network saturation. I’ll be highlighting the RTT (round trip time) with different numbers of unicast tasks running simultaneously. I’ll also highlight total overall NFS throughput. I predict that once HDD seek times are maxed and the HDD can no longer keep up with the number of simultaneous reads, that network performance will drop below 1Gbps, and latencies will skyrocket.

The man page:
http://man7.org/linux/man-pages/man8/nfsiostat.8.html

@george1421 This sort of plugin would highly aid in the FOG Integrity Checker plugin - which is yet to be completed because it’s missing the scheduling part…

Second this request.

@Tom-Elliott Just thinking about the next steps here…

I have to work on a few extra projects for my real job right now, but I’m thinking ahead a little.

In funcs.sh, can we move the code to pickup the kernel parameters and to call hostinfo.php into its own sub function? That we can reuse and call at different points in both the init scripts and via the post install scripts? That way I can reuse that code and have a consistent way of getting the parameters.

I could imagine a sub called getKernelParams() that could be called, and in that sub function if the ( boottype=usb ) then it would call a second function getHostInfo() to pick up the host info (that way too we can call getHostInfo() by its self to pick up the host details from the post install script(s) too (at this time I personally don’t care about the kernel parameters in the post install script, but if I did I could just call the getKernelParams instead). Then of course the /bin/fog script would need to take advantage of these new functions.

Added.

I have not added a way to upload your own files. However, I have added a way to define your own file name. All you have to do is upload your own file and point the boot settings to use that new file. The handling for colour and cpair commands are left just as text boxes. You need multiple changes, you just need to enter a new line and type. This leaves potential errors being left unto the users, but should be able to allow more people to make their own color schemes for the boot menu.

Useful links:

http://ipxe.org/cmd/colour
http://ipxe.org/cmd/cpair

of course, I should note, you can, I suppose, inject any ipxe code in these fields, however I doubt that will be much use to others as they’re stilled called only in their relevant functions (get_console/alt_console/host).

We’re having the same issue as well. Imaging Windows 10 machines. The snapins are trying to deploy before the hostname change / active directory join has taken place.

Fog server is SVN version 7909.
Client is 0.10.6

Done. Moved version information as well.

The update for the time is only done once a minute so as not to spam the server as this time is displayed on ALL pages.

@Junkhacker Ok, I was just thinking of ways for quick image to somehow count toward monthly totals. This happens mostly with laptop deployments. I think I just thought of a work around. Registering network dongle as host so every time quick image is used with the network dongle it will count because the dongle is pre registered. The only trouble would be if the dongle is not compatible. But this should work for many instances I believe.

@Tom-Elliott Thank you

@Joe-Schmitt said in Fog Client Disjoin From Domain Feature:

Could there be an on-demand unjoin task?

Powershell can do that. Why make a custom task? It can be done with a simple snapin and powershell file.

Although I suppose even that is easy to overlook, because if it’s left associated, it’ll run on next image deployment and might un-do the client’s work, causing the client to join the domain twice, and reboot twice as much as it already is.

Bottom line I guess from this thread and multiple others of similar nature is pay attention to what you’re doing, and what’s going on in your environment.

Things can be implimented and safeguarded, but too much of that hinders everything else.

@Wayne-Workman This in latest release I take it? Should help with new nodes I plan to add within the next few weeks.

Understood, and completed.

@Sebastian-Roth I think I did - but that was a long time ago and it looked hard lol.

Keep in mind I’m learning stuff all the time. Looking at it now, that is going to be a piece of cake.

There are many ways to accomplish this, but the simplest was to just edit the variables that define the booturl when the location plugin is enabled.

This has been added and pushed.