@kevinnew22 said in Error trying to restore GPT partition tables (restorePartition TablesAndBootLoaders):

understood, the release of the new version will be when more or less? I can help with something?

Can’t give you a date as we don’t have a fixed plan for new releases. Not great but that’s the way it is right now. Hardly anyone has time to work much on FOG and so things are going very slowly. You are more than welcome to join in an help us push this forward. See my post in the forums. Please send me a private message if you are keen to get involved and I am sure we have something for you! Looking forward to hear from you.

@louvet-christophe Can you please take a picture of the error on screen and post that here in the forums?

I forgot to isntall the client it’s working now sorry !

@tom-elliott J’essaie d’avoir un espace de stockage supplémentaire pour FOG, en créant un nouveau nœud de stockage.

Est-ce possible de stocker des images sur un poste Windows 10 pro dans un dossier partagé?
Est-ce obligatoire d’utiliser Windows Serveur pour stocker des images?
Doit on utiliser un NAS?
Si vous avez des procédures?

Merci pour votre réponse.

@librarymark I came accross the same error here with a different software that does the same. Couldn’t fix it but I see you managed to fix it and I don’t mind to use RRRx instead of Radix.

Can you walk me through this please? My FOG server is set to undionly.kpxe as far as I know (last time I checked this was long ago). Do I need to change it in /etc/dnsmasq.d/ltsp.conf

@george1421 great! by habit we turn secure boot off. i have someone looking into attempting to capture in a while to see what we get. thanks for all of your help so far.

@nockdown You might check the UEFI/BIOS firmware settings to see if you can disable the automatic boot order switch. Or maybe even contact Asrock to see what they can offer.

@Almeida The fog-client service runs as SYSTEM user by default. Not sure if that has enough access rights to run bcdedit. Search the forum for “psexec” to find a topic explaining how to use PsExec to test-run commands under the SYSTEM user account.

@jacyjacy77 While I realize this won’t help you, I do find this entreging from a secops perspective. So the bad actors were able to compromise the cloud hosting provider, compromise the command and control function to reset the devices. This is just a postmortum question, but can you manage these devices without a cloud account? Is there local management features? If you can manage them locally, the simple security fix is to assign a static IP address and subnet mask to this device but don’t set a gateway address. The device will not know how to leave your local network. There will be no chance for it to access the cloud controller or receive external commands. That way the device should remain functionally locally and not have the risk of external compromise. Firmware updates haven’t been issued since 2015 so unless WD fix this hole with a firmware update that probably the easiest and most assured way to keep using this device if you are so inclined.

Bonjour, @tallier

Pensez à écrire en anglais sur ce forum (en attendant un sous-forum français). Deepl est votre ami pour la traduction https://www.deepl.com/translator

Pour déployer un serveur Windows, je mettrai Windows Other au niveau de l’image.

Traduction Deepl :
Think of writing in English on this forum (while waiting for a French sub-forum). Deepl is your friend for translation https://www.deepl.com/translator

To deploy a Windows server, I will put Windows Other at the image level.

@yeet said in Setting up my 2012R2 DHCP server to handle UEFI and BIOS PXE boot, and I need some help.:

I’ve had ipxe.efi work 99% of the time, but there’s some models that only snp.efi and snponly.efi work on.

The issue is that those models having an issue with ipxe.efi use the same vendor class than the others and can’t be distinguished from the by vendor class identifier.

I am not very good with Windows DHCP server but in generel you’d setup a particular rule/policy for problematic clients using their MAC address to distinguish those from other machines.

@samdoan said in Multi drive image reversing disks.:

This tells me that it’s deploying Disk1 to /dev/sda AND /dev/nvme0n1

I don’t think this is the case! It’s just the partition layout that was deployed to /dev/nvme0n1 on an earlier run and it’s still like that because for some reason it only deploys one disk right now.

Please check your image and host settings again. Is the image set to All Disks? Also make sure Host Primary Disk is not set for the host you deploy to.

@george1421 My apologies for the repeated posting. Just wanted to follow up to say that the FOG Client DID join my test machine to the domain as desired this morning. Not sure what the difference was (other than that the laptop had not previously had a power cord plugged in), but it looks like everything is behaving as I had hoped it would. Thank you again for your time and effort to help me out.

@Bristow-0 As well question arises if both the workstation and VM are in the same mode - legacy BIOS or UEFI. With ProxMox you use KVM for this I suppose.

@sebastian-roth Sorry if this is a dumb question but I’m pretty new to all of this, I am trying to PXE boot now but its showing no boot file name received. Thanks!

@tom-elliotthello,
Excuse me for the long time to do the tests, I don’t have much at the moment for this project.
Here is the photo of the debug (the error message comes up over and over again countless times).

image0000001(1).jpg

@Bristow-0 Has this ever worked before? I remember that others had issues with domain join in a Samba domain. Search the forums for that.

As well you might take a look at the fog-client log (usually in C:\fog.log) and post the relevant part here.

@d2freak82 said in Certificate Nightmare:

on install if I select HTTPS it will not install because of the certificate error.

Even when using the updated SmartInstaller mentioned below?

Where exactly do you see the certificate error? Can you post a screenshot? Possibly it’s something we can/need to fix in the fog-client setup.