@marc49ca Thanks for your input on this. Though I feel like it’s not related to the OP’s question on VMware Workstation. The guide I was following to set it up mentioned that FOG wouldn’t capture from UEFI. This statement is no true in general (as you post it here)! What’s mentioned in that guide is: One more thing, make sure that Legacy Boot (not UEFI) is enabled on whatever computer you want to capture or deploy. I think FOG supports UEFI already but I haven’t looked into it yet. This is specific to VirtualBox being used in that tutorial and not caused by FOG but simply an issue within VirtualBox that doesn’t properly PXE boot UEFI VMs. I am not exactly sure if this is still true for the latest version. I don’t think so but maybe. ESXi is not like VMware Workstation is not like VirtualBox. After building my Win10 image (tried with 1903 and 1910) and getting the same problem I found took a different approach. Build the Windows system, sysprep it. Before booting again, change the system type from UEFI to BIOS (as we’re not booting Windows it won’t matter). Then registered the host and reboot to capture the image. This hint on using legacy BIOS mode just for capturing might be helpful in the OP’s situation as well! Good point.

@marted Looking good.

Well you have a few things in you need to think about. Moving netboot services to the FOG server. This is pretty easy enough to do. You change the dhcp options 66 and 67 to point to your FOG server from your current netboot server. I do have a tutorial on how to setup FOG as a netboot server here: https://forums.fogproject.org/topic/10944/using-fog-to-pxe-boot-into-your-favorite-installer-images This system uses FOG to create the custom iPXE menu entries to boot into your linix distro’s live installer environment. You may have to tweak the kernel parameters to load your installer seed file. The nfs disk structure and preseed file organization is up to you since netbooting is not a supported feature of FOG, but a hack using the FOG infrastructure for netbooting. Once you have your netboot installer for linux configured then you can focus on the windows bits.

@Ben-Acheff Can you post the contents of the d1.minimum.partitions file and a picture of what you’re describing? For years, Size on Server = Image File Size Post Compression. Size on Client = (Roughly) Minimum required Hard Drive size. From what you’re describing, you’re mixing the two differences.

May also want to check to see if the computer object already exists in AD. If the account does exist, the join account also needs the ability to modify that account either by virtue of being the creator/owner or by having the permission to modify computer objects in the target OU.

Thankyou Fernando!

@Sebastian-Roth Yeah, this isn’t something readily available in the code. @endia If you’re at least semi familiar with code, you might look into /var/www/fog/lib/fog/bootmenu.class.php This isn’t currently coded for, but you might even be able to do what you want using a simple (relatively speaking) hook to alter the boot menu system. There’s a template hook already created that should help get you started. By creating a hook, you aren’t altering the core code within FOG. Hooks are meant as a means to inject custom data specifically around what you’re requesting to happen. The hook that’s setup is located in /var/www/fog/lib/hooks/bootitem.hook.php Ultimately what you would do is make your changes and set the active flag to true. (it’s a variable named active)

@Sebastian-Roth Thankfully, Mariadb has a list of possible issues: https://mariadb.com/kb/en/converting-tables-from-myisam-to-innodb/ We’d need to set some baseline settings in the mysql config, imo.

@babouche said in Client Host not showing after 2nd restart: It’s only when i manually ping from my server to the client that i can see my firewall deny the ping. Ping (ICMP protocol) is handled different by a firewall than TCP connections are. Ping being denied might be a hint on other protocols also being restricted but doesn’t give you a definitive answer on that question.

@NateUH Yes it is supposed to auto-start on bootup of your FOG server. Please run systemctl is-enabled FOGMulticastManager.service to see if it’s enabled on bootup. If you get disabled there must have been an issue when running the installer. You might run systemctl enable FOGMulticastManager.service or re-run the installer to do this for you. But if it’s enabled already then you might be running into a startup dependency issue in FOG 1.5.7 which we have fixed lately. Ask here if you need more details on this.

@Tom-Elliott Nice, it is working now. There was a slight blip where it got stuck at Downloading kernel, init and fog-client binaries… So I ‘quit’ the install removed user fogproject and ran the install again. I was able to update the database schema, continue the install and login. New interface looks slick!

[Mod Note]: Cross linking posts since the issues are related: https://forums.fogproject.org/topic/14134/keyboard-not-recognized-when-using-kvm-switch

@justeverything Do you have the working version of this?

You should be able to use the original refind.efi from 1.6.0 as this is one of the older versions. Whether it works I don’t know, but I do know of at least one person who uses this old version (0.9.4 I believe?) with their HP machines. They also needed to use the 10 second delay files due to NICs being power save ready.

Okay, now the client gets the information from the server without error and can execute a task launched from the server. Thanks a lot.

It turns out that this was a problem with the Trusted Platform Module. Apparently it didn’t like the new O/S being installed on hardware it had already “signed”. Not being too schooled in how TPM works, I’m making an assumption here, but clearing the TPM after deployment fixed my bootup problem. This can be done in the BIOS, or by letting the system boot from the Hard Drive at the Fog Menu, then running tpm.msc and clearing it there.

We have had some success with using the snponly.efi boot file instead of ipxe.efi. Also updating to fog version 1.5.7.100 might have helped as well. I did notice today HP came out with a newer bios verison for the HP 840 G6 model. Bios version 01.04.02 which seems to have a lot of bug fixes. I might give this a try tomorrow but I figured someone else might want to try it out before me and let me know how it goes.

@Base2Nathan I’m not asking to be rude but there’s hardly any information to work from. All fog does from imaging is capture what you tell it to, and deploy where/when you tell it. It’s block level, so there’s nothing fog would be doing in regards to the programs you have installed or removed.

@zuf76 Yes, take a look at the so called “Service Settings” tab within the host’s view. As well there is a global service setting in FOG Configuration -> FOG Settings -> FOG Client - … sections.