@Almeida BitLocker is enabled in your master ? If yes, you should disable it. Enable it only on the final computer.

We do have the BCD issue when enabling BitLocker on 24h2 image, we are running the same commands, but you are missing one.

You need to set device partition=C: for the recover from hibernate entry too. The annoying part is that its ID is dynamic.

@Almeida

The problem is solved.
tftp was closed

Thanks.

The problem is solved.
I disabled DMA protection on the HP ProBook.
Good day.

@Almeida I suggest you update to 1.5.10 or at least manually update the FOS kernel.

@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.

@Almeida
@Sebastian-Roth

this is a simply example, security is by your side:

#!/bin/bash SERVER=$1 USERNAME=$2 PASSWORD=$3 FILE=$4 USER_TO_LAST=$5 echo "Result from last $USER_TO_LAST" &> $FILE last $USER_TO_LAST &>> $FILE lftp -u $USERNAME,$PASSWORD $SERVER << EOF put $FILE EOF

Configure as on image:
Snapin template is bash.
example.png

Tested on Linux Mint 19.

@Almeida Free disk size? df -h?

Anything you see in the apache error logs (see my signature)?

Can you confirm

The FOG webgui is reachable On the switch where the target computer is: Ensure that spanning tree is configured for fast-STP or RSTP or place an unmanged switch between the target computer and the building switch.

@Almeida How is your question related to the FOG project? Please tell us a bit more on what you are having an issue with.

“default” is not used.

@Tfoote01 Great to hear you got this solved yourself. Thanks for sharing!

You could do something like a batch file

@echo off reg add xxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Then add that into your snap ins and deploy it!

Ok thanks.

Thanks.
It is solved.

With FOG 1.3.x and newer there is a change in the process that is required for sysprep. You can install the fog client into your golden image before sysprep. But you must set the service to disabled. And then add to your golden image a setupcomplete.cmd batch file that enables the service. What happens is that the fog client doesn’t know that OOBE is still running so it starts doing its job too early in the imaging process causing OOBE to fail because the fog client reboots the system at an unexpected step in OOBE.

ref: https://wiki.fogproject.org/wiki/index.php?title=FOG_Client#FOG_Client_with_Sysprep

Also you should consider upgrading to FOG 1.4.2 if you are still running on FOG 1.3.X

Hello,

I’d like to close the topic. It was the solution.

Where is the button “solved” ?

Thanks.

You’ll also want to update if that 7050 was purchased with an NVMe drive. FOG 1.2.0 doesn’t support NVMe drives or Win10 very well.

@Almeida

@Tom-Elliott said in Multicast doesn't work:

As a mode of reference, this typically occurred because of the storage node network interface. If it couldn’t match the interface, the files couldn’t be found to enable the command.

As @Junkhacker stated you would be best to update to the newer series of FOG as many of these things have been corrected for and we have more direct capabilities to help troubleshoot.

I’d recommend the 1.3.5-RC’s particularly if your Server OS is Ubuntu flavored.

I can recommend Ubuntu 14.04 or 16.04. FOG installed with out a hitch!

[url]http://www.fogproject.org/forum/threads/utilizing-postscripts-rename-joindomain-drivers-snapins.12175/#post-40351[/url]