Posts made by willian

@Sebastian-Roth said in Updating FOG and retaining settings:

@willian Upgrade will rewrite the DHCP config of your FOG server. So make a backup copy if you have modified it.

I could even clone the server for testing but later I will see how I do.

As well make sure you read und understand this before you upgrade: https://forums.fogproject.org/topic/13488/fog-1-5-7-officially-released

Is there any important information in this topic about this issue? I read everything but I saw nothing related.

Thanks.

Hello. One question, here at the company we are currently at version 1.5.6 and I am thinking of upgrading to 1.5.7. The FOG server is also the DHCP server. I was wondering if updating will make any changes to the DHCP service or just the FOG settings.

Thanks.

@george1421 the next time I need to change something in the golden image I will test these scripts. Thank you.

@george1421 So, since Change Hostname Early might not work for me since I use sysprep, could I enable Hostname Changer to do the check but not reboot the machine in a forced manner, but when it is manually restarted by the user?

@george1421 I had understood that by enabling the change hostname early, the hosts would have their hostnames changed during or after the deploy of the image, according to which they were registered on the server. For example, if I registered a host like Test-123, after deploy the image that would be its hostname.

Hi @Sebastian-Roth that’s exactly what I wanted to know. I keep the Change Hostname Early enabled, as in the picture I posted, but the hosts “receive” random hostnames, DESKTOP-XXXXX. As I use sysprep to create the golden image, I do not include the ComputerName option in the unattend.xml file. I’ve also performed a debug deploy task to check:

Hello.

I wonder if these two settings do the same thing or is there any difference between?

Thanks.

@george1421 Here we also deploy one by one. What I meant is if you configure each machine to enter the boot menu by F12? Or is there a way to configure multiple machines at one time?

@george1421 said in Change the boot order automatically:

@willian One thing (a bit off point) is that for my company, I enforce my guys to use the F12 boot menu to pick pxe booting. The default boot order is always the hard drive, but they pick F12 boot menu to do a pxe boot. That way on a restart it will go back to the default of a hard drive boot.

Do you do this for all machines? One by one?

@george1421 I did some testing initially on VMs (Hyper-V), and on two machines, one with Biostar motherboard and another Asus.

Hello.

Is there a way to change the boot order automatically after deploying a Windows 10 image in Legacy/BIOS mode?

When I do a deploy in UEFI mode, the order is changed automatically, the reboots that the system makes during the installation already goes directly through the HD. In Legacy/BIOS I have to change manually after the image deploy, otherwise it will always start with iPXE.

I’ve tested almost all of the “Exit to Hard Drive Type” options: sanboot, grub, grub_first_hdd, grub_first_found_windows, but all continue to boot from iPXE.

Thanks.

I don’t know what happened but now it’s just capturing used space.

@Quazz yeah, but as it is a VM, I think there is no such option.

@Sebastian-Roth but there is no Fast Boot option in the VM, and BitLocker is disabled.

And I think the VM is properly shutdown when I run sysprep.

Guys, I came back because I think there’s still something wrong with the image capture I’m doing.

Somehow I can now capture the image without appearing the error I posted in the attached image, I commented the lines I had added fog.postinit script (provided by @EduardoTSeoane ) and nothing else, and now the capture normally occurs, but I still see a problem due to the fact that the whole disk is being uploaded instead of just the space that was used. So I read, it could be something related to Fast Boot, Hibernation or BitLocker, but as the image I made is coming from a VM, then I do not see how this could happen, other than that, the image type is as Single Disk - Resizable .
Was there anything else that could cause this?

Thanks.

Hello @Sebastian-Roth

Yes, I saw it, but since I used sysprep to make the image, I thought that there would not be that problem.

@EduardoTSeoane Thanks a lot for the help.

I made the changes to the file you mentioned and it worked, but a question if you can help me, in the attached print shows that /dev/sda4 is being cloned, only 13.3GB of space was used in the image I made, but apparently it is being cloned the partition in its total size 135.7GB and is taking a long time to finish. Is this right?

I have a Fog installation (1.5.6) and am having trouble trying to capture a Windows 10 image. I created the image in a VM and ran Sysprep.
Two months ago I had done an installation with version 1.5.5 and gave the same problem, but I had managed to solve, I just can not remember how

Thanks.