When checking the Log file i can see the client getting the information that a snapin is set to be executed, but then when accessing the file i can see that an ipv6 address seems to be used and get a line saying that access is not possible.
Please post that part of the logs here in the forums. That way we are less likely to miss-understand things.
@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?
@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.
@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.
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).