Hello,

The best way to do that, i think, is to disable host registration in parameters to prevent not wanted hosts in your console.
After that, create your hosts manually (or .calc file or api fog) in your console.
Create groups with hosts you want to deploy. (by model, by image, by classroom … )
In that way, you are sure to only deploy expected hosts.
Does it meet your needs ?

Glen

Hello,
You can also have a look at this topic :
https://forums.fogproject.org/topic/16876/dual-boot-grub-issue-after-deploying?_=1696487644593

Hello,

Here is a link for taskbar in Windows 10 :

https://learn.microsoft.com/en-us/windows/configuration/configure-windows-10-taskbar

Hi,

I just rebuilt two proxmox debian 11 containers with FOG 1.5.10

Master node > install HTTPS
Storage node > install HTTPS

Install plugin Location

Master node and storage node are in the default storage group
Master node > default’s Master node

Create new location > location_1
storage groupe > default
storage node > defaultmember
storage node protocol> HTTPS

Create new location > location_2
storage groupe > default
storage node > secondary node
storage node protocol> HTTPS

Create snapin in default storage group with replication enabled

Configure one host with location_1
Deploy snapin > OK, it works

Configure one host with location_2
Be sure the snapin is replicated into the storage node
Deploy snapin > it doesn’t work
What am i doing wrong ?

Here is the snapin log

---------------------------------SnapinClient---------------------------------
------------------------------------------------------------------------------
 03/07/2023 12:39:24 Client-Info Client Version: 0.13.0
 03/07/2023 12:39:24 Client-Info Client OS:      Windows
 03/07/2023 12:39:24 Client-Info Server Version: 1.5.10
 03/07/2023 12:39:24 Middleware::Response Success
 03/07/2023 12:39:24 SnapinClient Running snapin snapin_1
 03/07/2023 12:39:24 Middleware::Communication Download: https://xxxxxxxx//fog/service/snapins.file.php?mac=00:23:24:19:46:64&taskid=2
 03/07/2023 12:39:24 Data::RSA ERROR: Certificate validation failed
 03/07/2023 12:39:24 Data::RSA ERROR: Trust chain did not complete to the known authority anchor. Errors: La signature du certificat ne peut pas être vérifiée. (NotSignatureValid)
 03/07/2023 12:39:24 Middleware::Communication SSL certificate chain error: Une chaîne de certificats a été traitée mais s’est terminée par un certificat racine qui n’est pas approuvé par le fournisseur d’approbation.

 03/07/2023 12:39:24 Middleware::Communication ERROR: Could not download file
 03/07/2023 12:39:24 Middleware::Communication ERROR: La connexion sous-jacente a été fermée : Impossible d'établir une relation de confiance pour le canal sécurisé SSL/TLS.
 03/07/2023 12:39:24 SnapinClient C:\Program Files (x86)\FOG\tmp\file.zip
 03/07/2023 12:39:24 Middleware::Communication URL: https://xxxxxxxxx/fog/service/snapins.checkin.php?taskid=2&exitcode=-1&mac=00:23:24:19:46:64&newService&json
------------------------------------------------------------------------------

Hello,
I use debian 11 and v1.5.10 of FOG. Thanks for explanations. I will rebuild a test environment to try another time.
Best regards,
Glen

Hello,

Did someone try to connect to the API with the FogApi module with an https environment ?
It works well with http but with ssl i have this message :

Invoke-WebRequest: The remote certificate is invalid because of errors in the certificate chain: UntrustedRoot

I tried to find infos about offered features (http/https) but i didn’t find anything.

Thanks,

Hello,

I had the same problem during my dualboot deployments with Refind as boot loader. Even putting Refind first in the boot order on the master, when deploying my clients, Windows were almost systematically first (sometimes, multiple Windows entries). I solved the problem by creating a post-deployment script that recreates the BDC store with the desired configuration.
The doc here: https://learn.microsoft.com/en-us/windows-hardware/drivers/devtest/bcdedit--enum

Hello,
When ou create your container, try to uncheck “Unprivileged container”.
After, go to “Options” on your container params and enable “Nesting” and “NFS” options.

Hello,
I would like to know what is the right way to install a FOG infrastructure with a complete SSL configuration.
For me the main difficulty lies in understanding and setting nodes with the location plugin activated. I can’t deploy snapins to my clients when I force a different location from my master node. I am interested in any useful info on this subject. Already know if it is possible
Thanks,