I was updating from 1.5.0 RC 11 to RC 13 and the update failed when I got to “Creating SSL Certificate” on the fog installer. The OS is Debian 9. Any help would be appreciated.

Thanks,

Hello, I’m having an issue creating a location using the location management snap-in. When I try to create a location, I get an error message “ID Must be set to edit”.

Server OS: Debian 9
Fog Version: 1.4.4

Any help would be appreciated.

@sebastian-roth Correct. My Dell Optiplex 5040’s are in legacy mode. Never had luck with FOG and UEFI always got the “Chainloading” error message that is why they are in legacy mode. Thanks for your help.

@george1421 Correct. The boot order on the computer is IPXE first. If I take IPXE out of the boot order, Windows boots just fine.

@Sebastian-Roth I switched the HOST Bios Exit Type to GRUB and computer was able to boot into Windows. Thanks.

@george1421 I have not yet created an image for this version yet. 1703 is a clean install and not an upgrade from 1607.

@Sebastian-Roth I will test with the different exit styles and get back with you soon.

@sebastian-roth I too am seeing the exact thing with Window 10 1703 with after fog boot menu all I get is a blinking cursor. My environment is Windows 10 1703 in legacy mode running Fog 1.5.0 RC-8. What information would you like to see? Would it help if I take a video of the boot process so you can see what we are seeing?

@Tom-Elliott Thanks Tom. I went ahead and deleted all the columns and just left the <mac> and <hostname> and they imported successfully.

SERVER
• FOG Version: 1.4.0
• OS: Ubuntu

DESCRIPTION
Importing fails when trying to import host under Host Management. The CSV file looks good with about 200 entries. But when importing that CSV file, the Import Host Results (Total Rows, Successful Host, Failed Host, and Errors) are 0.

@Wayne-Workman here is the output /usr/local/sbin/udp-sender

I am seeing the same issue with a fresh install of Ubuntu 16.04 and RC19. Any suggestions?

Running Fog 1.3.0 RC-8, I am getting the “ChainLoading failed” error message when trying to boot into the Hard drive. These are Dell Optiplex 5040 booting using the ipxe.efi file.

I changed the “Exit Hard Drive Type(EFI)” to the other options and it will not boot to the HDD only if the exit type is “EXIT” do I get the chainloading error.

@Wayne-Workman Ah. Did not know I had to do that first. Thank you for your help.

@Joe-Schmitt For my image, I just install the Fog client. I do not do anything special with it before sysprep.

@Wayne-Workman No antivirus is installed in the image. I guess just the Windows 10 built in defender is on but other than that no. I will do more testing today. I post back what I find.

@Tom-Elliott Just an update. I did try that and that did not work. But I did look at the fog log and did notice that the last entry was over 30 minutes old so just for fun I looked at the Fog service and it was stopped. I restarted the service and the computer restarted to change the host name but was not joining to the domain so I looked again and the service was stopped again. The Startup time is set for Automatic but for some reason it is not starting on its own I had to go in and manually start the FogService. I think that is the smoking gun to my issue.

@Tom-Elliott I did verify that those settings are correct and I still need to do a second restart for the PC to join to the domain.

I think that there might be a bug with Fog auto joining computers to the domain right after imaging with Windows 10. I have two independent Fog systems one with the Fog client version 11.0 running Fog version 8179. The other Fog system is running the newest Fog client 11.3. I have notice with both, after deploying a Windows 10 image, it will not join to the domain, but if I restart the PC then it will join to the domain. I don’t know if it is something with the Fog client and Windows 10 or another issue that requires a second restart of the PC to join to the domain.

@Sebastian-Roth

After editing that file, the image deployed successfully.

Here is that screenshot with the commands before I deployed that image. Thanks for your help.

@Sebastian-Roth

Here ya go:

@Sebastian-Roth

Here are my results:

ls -al Optiplex745Win10/
total 7519176
drwxrwxrwx  2 root root       4096 Jun 16 10:19 .
drwxrwxrwx 32 root root       4096 Jun 14 12:10 ..
-rwxrwxrwx  1 root root          1 Jun 14 09:52 d1.fixed_size_partitions
-rwxrwxrwx  1 root root    1048576 Jun 14 09:53 d1.mbr
-rwxrwxrwx  1 root root        190 Jun 14 09:53 d1.minimum.partitions
-rwxrwxrwx  1 root root         30 Jun 14 09:52 d1.original.fstypes
-rwxrwxrwx  1 root root          0 Jun 14 09:52 d1.original.swapuuids
-rwxrwxrwx  1 root root  325089680 Jun 14 09:53 d1p1.img
-rwxrwxrwx  1 root root 7373459536 Jun 14 10:15 d1p2.img
-rwxrwxrwx  1 root root        190 Jun 14 09:52 d1.partitions

/Optiplex745Win10# cat d1.partitions
label: dos
label-id: 0x1288f3ca
device: /dev/sda
unit: sectors

/dev/sda1 : start=        2048, size=     1024000, type=7, bootable
/dev/sda2 : start=     1026048, size=   155273216, type=7
root@RoyFogMasterNode:/images/Optiplex745Win10#

cat d1.minimum.partitions
label: dos
label-id: 0x1288f3ca
device: /dev/sda
unit: sectors

/dev/sda1 : start=        2048, size=     1024000, type=7, bootable
/dev/sda2 : start=     1026048, size=    35327996, type=7

 cat d1.fixed_size_partitions

root@RoyFogMasterNode:/images/Optiplex745Win10#