I’m writing this poste, because we’re in front of BIG issue, the NVRAM variable of the client machine. Just few words to describe the situation: We have image poste UEFI/GPT with installed Windows and Ubuntu and Grub2win (small boot loader something like grub but installed from windows) Up to now everything was fine the image works grate.but when we send the image to another machine UEFI the computer doesn’t see any more geib2win boot loader and boot only in windows. We tried many different way to overcome this problem but with no success. I was thinking for few scenarios and I really need your opinion on that: When we boot in windows, obviously it boot in windows, can I make some poste install script/snapin to copy the efi partition (cloned from the image machine) to NVRAM variable of the new machine and on next boot to have a new efi boot entry? Up to now I tried with bcdedit to replace boot efi file of windows with the efi file of Grub2win but this doesn’t work. Is there any other way in windows environment? I red in your forum for init post script , which if I understand correctly will run before cloning the machine. Is there a way to make a copy of the boot entry of my image machine with efibootmgr and with the same tool to copy this entries to my client machine before even it was wiped or written? Or at least a command to add an entry to NVRAM like défaut entry to the new machine? I really want to resolve this problem because we came too far with FOG and we really love it and we won’t give it up for an issue like this one, but we have 400 computers UEFI and we have to find a way to image them with our Bootloader on the top of windows Bootloader. Thanks in advance for all your suggestions and help

This may take a few times discussion to find the best solution for you. Lets start with basics of FOG. The operating system that runs on the target computer to capture and deploys images is based on linux, for this talk we will call it FOS (Fog Operating System) Linux. This is a customized version of linux designed just for imaging. So you have to remember that FOS is Linux and can only run linux program not windows programs. There are a few linux programs that let you interact with windows registry but not many. In FOG there are 2 places where the fog admin can add in custom linux bash scripts to interact with the target computer. The first place is a POSTINIT script. This script is run before imaging begins. In the POSTINIT script the fog admin can run commands that maybe needed to connect to disk arrays or configure the system needed before imaging starts. The second place is a POSTINSTALL script. This bash script is called after the image has been written to the storage media and before the system reboots. At this place you have the ability to connect to the target disk and interact with the contents of the disk using linux commands. You may NOT run any windows commands in a POSTINSTALL because FOS is Linux not Windows. If you want to interact with the UEFI bios boot order FOS Linux has the linux command efibootmgr that you can call from your POSTINSTALL script. Your POSTINSTALL script can edit text files on the target computer by mounting the proper partition and using sed or other linux script commands to change the text file values. So if you need to edit the grub.conf file you can do it in the post install script.

Your browser does not seem to support JavaScript. As a result, your viewing experience will be diminished, and you have been placed in read-only mode.

Please download a browser that supports JavaScript, or enable it if it's disabled (i.e. NoScript).

FOG doesn’t copy NVRAM from cloned machine to the new machine

Solved

FOG Problems

2.4k

S

Sebastian Roth Moderator
last edited by

@marted Looking good.
Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG
1 Reply Last reply
Reply Quote 0

152

Online

12.0k

Users

17.3k

Topics

155.2k

Posts