@sebastian-roth said in configuration ssl interface de fog:

@julio The certificate we see in the picture is not generated by FOG I would say (Issued To: Administrateur, Issued By: Administrateur, Expiry Date: 17/11/2120?!?). Did you put that CA certificate file there?

The mentioned path /opt/fog/snapins/ssl/CA/.fogCA.pem is where the FOG installer will generate the CA certificate. It then copies that file to /var/www/html/fog/management/other/ca.cert.pem, where it is used by the Apache webserver. So you might want to compare those two files. Maybe you need to import the later one if you have messed with those files.

Be aware that importing the CA certificate into the Personal key store is probably not going to help. You need to import into Trusted (Root) Certificates section.

pour ceux qui sont intéresser suivez les etapes de mr roth.

@sebastian-roth I have but I’m still trying to wrap my head around how it properly works. I think its more me trying to understand the Documentation thats available to read online/watch, but Im wanting to do it more with Powershell but not finding any documentation on the Wiki.

@the_ccm Would you mind if I included a link to your tutorial post in my larger post here? https://forums.fogproject.org/topic/10944/using-fog-to-pxe-boot-into-your-favorite-installer-images

Networked storage is mainly used in small office environments such as smoking gun slot and in workgroups, where it has adequately replaced the classic servers. They serve as shared file storage for documents and backups, as well as mail and Web servers. On them run the messaging services, automation systems, video surveillance, and other tasks relevant to the modern office. Unlike a classic server, NAS is beautifully designed, takes up only a fraction of the space of a traditional office computer, is quiet, and consumes minimal power. Perhaps the greatest advantage of a NAS, however, is that it is a complete, boxed solution that starts working as soon as you plug in the drives and plug it in. You don’t need a specially trained person to use it, and in terms of ease of operation, it’s comparable to a modern tablet.

NAS have proven to be equally interesting for home use where they are typically used as a torrent station and large storage for movies, photos, and music. However, the home uses of NAS are not limited to these. They take into account the interests of advanced users running specific and complex tasks on NAS, as well as ordinary users, for whom it can be a very convenient and functional tool for working with multimedia content, creating backups, anti-virus protection and, of course, for creating a personal “cloud”.

MOD’s edit: removed external link as it does not seem to be related to FOG at all.

@Jamaal
@jj-fullmer said in fog API powershell help:

Glad I had the code for get-foggroups somewhere to be found. It looks like something weird happened to the get-foggroups function and all the code disappeared from it. I’ll need to get that fixed as soon as I can as that function is used all over the place. I have made an issue for it https://github.com/darksidemilk/FogApi/issues/3

I just published a new version of the module fixing the issue with get-foggroups and subsequently get-foggroupsbyname if you update to the new version 2103.2.12 those functions should work now.

@tom-elliott
Ok thought so thanks.

@brakcounty Please read through this topic: https://forums.fogproject.org/topic/9624/control-access-plugin

Understand this is not like full access control as FOG wasn’t implemented like that and a plugin cannot simply fix this. But it might still suite your needs.

Note: This plugin code does not get much attention because the original developer does not seem to find the time right now. So if you find an issue we might not find the time to help and fix this.

@renard Would you give us a clear picture of the error taken with a mobile phone? We need to see where in the imaging process where these messages are created.

I found something, I have to ask what version of the FOS Linux kernel are you using (fog web ui -> FOG Configuratio -> Kernel update)

ref: https://askubuntu.com/questions/1272026/acpi-bios-error-bug-could-not-resolve-symbol-sb-pcio-sato-prto-gtf-dssp

Will you tell us more about the computer you are trying to image? What is the model and manufacturer. If you are using a custom built computer what motherboard do you have? Is the firmware the latest for this motherboard?

We will be building a new VM with Ubuntu 20.x…it won’t be an in-place upgrade. I will post any issues we run into…fingers crossed.

@tom-elliott

Very good, after understanding what you were trying to tell me and applying those changes I was able to finally understand what the problem was. It worked!

I thank you for your patience and perseverance in helping me! I just deployed the FOG in our organization, which by the way is working very well! About 400 machines in the park. Thank you Tom! The FOG is awesome!

This would be a great feature to have, even if it were limited to only capturing to the image already assigned to the already registered host. It would be a good idea to have an extra confirmation message and invert the color scheme to make sure the user realizes what they’re about to do. However, deploying incorrectly can cause just as much damage as capturing incorrectly. FOG is a very sharp, double-edged tool.

Sometimes it’s a chore to go find another PC with network access so I can log in and set up the capture task or I’ll have to set up the capture task using the same PC before rebooting it. I can’t always carry my laptop with me and I don’t enjoy navigating any web interfaces on my phone.

@yeet said in UEFI and Legacy Bios coexistence with SonicWall DHCP:

Problem is we use our SonicWall for DHCP

Yes this can be a problem if your SonicWall doesn’t support dynamic boot options. The quickest and most direct route is to install dnsmasq on your FOG server to supply only the pxe boot information. Your sonicwall will supply all other dhcp settings except pxe booting.

I have a tutorial on how to add dnsmasq in about 10 minutes to your FOG server here:https://forums.fogproject.org/topic/12796/installing-dnsmasq-on-your-fog-server

If your pxe booting computers are on a different subnet than your fog server, you will need to update your dhc-relay/dhcp-helper service on your subnet router. Add the fog server as the last dhcp server in the helper service. Then everything will just work. If everyone is on the same subnet then just install dnsmasq and it will work.

Success! Dropped the files into /var/www and used set web-path to ${fog-ip}. In case anyone else has this issue this is my iPXE menu item parameters:
set tftp-path tftp://${fog-ip}/os
set web-path http://${fog-ip}
set pe-path ${web-path}/pm11_winpe
kernel ${tftp-path}/wimboot gui
imgfetch --name BCD ${pe-path}/BCD BCD
imgfetch --name boot.sdi ${pe-path}/boot.sdi boot.sdi
imgfetch --name bootmgr ${pe-path}/bootmgr bootmgr
imgfetch --name boot.wim ${pe-path}/boot.wim boot.wim
boot || goto MENU

@develroo I’ve had the FOG server running on raspberry pi 2 for quite a while. That is the 1.4.x series. For fog 1.5.x you should run that on a Pi3 or Pi4. The matter of fact, for fog imaging a Pi is more than enough for hosting the fog server. Now realize that the scope of service is for imaging a small number of system and no computers running the FOG client. The Pi4 is a bit more capable with 1GbE networking and USB3 for externally attached sata drives. The Pi 2 suffers with 100Mbs networking and USB2. The Pi3 has 1GbE networking and USB2.

For FOG imaging all the Pi needs to do is monitor the imaging process and move the image from local storage to the network adapter. The target computer does all of the heavy lifting. So the Pi3-4 is more than enough for acting as a limited or mobile FOG server.

@george1421

Good to know. I’ve been rolling with the same script since Win7 and likely would not have looked at another way to do it short of it failing to run on a new version.

@danieln I just realized that the persistent group plugin is not very well documented. It is covered a bit here: https://forums.fogproject.org/topic/8836/basic-persistent-groups-and-1-3-0rc16

The executive summary is

Add the Persistent group plugin Manually create a new host with a unique name that signifies it is a template host. Associate all of the snapins and what not that you want consistent for every host added to the group. Create a new Group that is exactly the same name as the template host. Now add hosts to this group (you can do this when you are registering the new computer with FOG too).

The settings will be copied over from the template host to the new host.

The workaround is just a patch file that needs to be replace on the FOG server. Replace this file BEFORE you install the plugin. If the plugin is installed before you add the patch file, uninstall the plugin then add it back.

We are discussing the discovered bug here: https://forums.fogproject.org/topic/15084/persistent-groups-snapins-added-to-host-but-not-deployed

The thread also has the temporary patch file link.

It works great !

Thanks a lot !

With apologies for the necropost, I’m looking at exactly this question at the moment. My thinking is you could possibly pair FOG with Relax-and-Recover or SystemImager for a complete backup/image/bare metal restore solution.

Looks like you would be able to add a Relax-and-Recover (ReaR) menu item to FOG’s menu for a full network-based restore, in the event of disaster. Since FOG can be used as a scheduler and general-purpose task executer, it is entirely possible to run one of these open source “live backup” solutions alongside FOG - i.e. on the same server.

I also note that ReaR can deal with UEFI/MD RAID situations, which seems to be a rare gift. 🙂

@george1421 Done. 👍