@Greg-Plamondon If you ever see an issue where the web UI doesn’t load, take a look at the apache logs - see my signature on where to find those on your FOG server.

@siheobs This might be a good one for you to follow: https://forums.fogproject.org/topic/11285/can-t-chainload-past-fog-menu-boot-hard-drive-hp-zbook-laptop

Could be a similar issue with rEFInd not having a driver for this particular disk/controller model.

having issues with trying to upgrade from dev-brnach to working right now. I will update as soon as i get the upgrade resolved.
Thanks.

@Marco-Antonio Is this still an issue?

@st4tus Any news on this?

@kafluke Please post the logs as requested or let is know if you’ve already solved this yourself so other users having the same issue can help themselves too.

@wayne-workman @george1421 It worked! in hindsight I should have just changed the management user, my bad.

Thanks again!

@jjsplitter Since you still had firewalld enabled, did you remember to set selinux to permissive? If not you will have a sad time when you try to capture an image.

@vinay said in Post Install Script does not work while deploying ubuntu 16.04 image using FOG.:

@sebastian-roth
Would you help me with the procedure to include chroot in my below mentioned script as i messed it up adding multiple things.?

I looked over your script. Looks like you’d put the chroot related lines at the start of your script. You should play around with chroot before doing this though. On a linux VM, boot to a live Ubuntu disk or something - then try to chroot from the Ubuntu disk to the local disk. Once you do this a couple times you’ll understand what chroot does and how to work with it. Also you should Google search it (or duckduckgo search it) too. We can’t do all your work for you, we rather show you the way.

@george1421
Thanks for all your help on this. Next time I will make sure I am running the same branch.

@george1421 Thanks for the info george1421! I’ll give it a try! Thanks again!

This can be closed. I switched my switch and this error went away! Different error now but this is gone after HW change.

@tfoote01 The fix was to disable the rogue dhcp server that was giving conflicting information to the target computer ( in Tyler’s case )

If you are having a similar issue, please open a new thread with your specific details. We like to keep specific conditions to their own threads if possible.

@obsidian said in Fog Replication Not working:

So I am confused as to why the Windows 10 image has not replicated to the ones that are syncing.

I have no idea. Check the master node’s replication log. It should give a reason.

I have finally figured it out. The ISO’s won’t boot in UEFI mode and must be set to legacy (BIOS)
For now everything is working. Thanks for the help guys.

This ticket can be marked as solved. Just need to make sure documentation for RC10 is up to date as there is a problem with the link.

@uwpviolator Yep, I sure am calling the unattend. I’m imaging the same way I have been for a while.

Would you be able to sanitize your unattend and provide, and I’ll do a line by line? As stated, my Unattend hasn’t really been updated since hte Win7 days, so I’d love to see a modern one that is known working…

Hello Guys,

thanks for all these information,

I installed FOG 1.2 (old) and updated later to the 1.4 on the same server with debian 9 .

I had the same problem
<
The server will boot to the FOG menu, but after selecting the quick registration, the system does not get an IP address

It have simply an wrong ip adresse in FOG configuration, like :
…
TFTP Server
…
Web Server
…
(wrong ip from the old install, ip adress changed)

after fixing the fog server ip address every things works fine.

Debian9 fully compatible with FOG1.4

Bye

Hassan

@george1421
What’s odd is that it doesn’t work in legacy mode on my laptop but does work in whatever the other mode is. I wouldn’t call it UEFI mode because the laptop has both UEFI and BIOS modes and is permanently set in BIOS mode. It is indeed UEFI mode. The other odd thing about all of this, is that it works in both UEFI and BIOS modes when booting as a virtual machine in ESXi 6.5 which is where I have been doing most of my testing since it is much easier than rebooting my laptop over and over. I am going to continue to play around with it. I can always fall back to booting any systems that fail PXE booting by booting from the GRUB4DOS USB harddrive and/or flash drive which accomplishes the same thing. I was just trying to avoid having to have the USB drive available at all times. Plus since I have ethernet throughout the entire house, it was a fun project to work on.