In my organization, I have started using the FOG for the past month and found it to be very flexible. We either register the host and deploy the image it via the console or just PXE boot and select “Deploy Image” and select the specific image for deployment. The whole process take less than 10 mins.

%WINDIR%\Panther\unattend.xml

@fettforce These might help you get going:

https://forums.fogproject.org/topic/9373/sim-creating-the-unattend-xml-guide https://forums.fogproject.org/topic/10465/anyone-share-a-working-unattend-xml

@OFlaherty GHOST does some magic thing when rebooting a client into a job. It backups and rewrites the master boot record and boot partition to bring up the GHOST imaging environment. FOG does not do this as it is quite dangerous and can break things fatally. FOG relies on real PXE booting a client to be able to run a scheduled job.

@bmick10 said in DHCP Server Change:

I think I have tried to get in by clicking on and said I didn’t have access even though I am administrator.

Linux doesn’t have the concept of ‘Administrator’, that’s a Windows thing. Linux has users, and root. And sometimes users are allowed sudo privileges for some or all commands. Really, you need to be root to edit the file. Usually, that’s done via CLI.

@Wayne-Workman

You can mark this one solved.

I deleted ALL power management entries. (Regardless of seeing any listed.) I haven’t had any hosts shutdown since.

Thanks again!

I suppose, to answer the question more directly, you can do a snapin pack.

Create a base batch file, and all your others. Create them into a zip file. Your “base” batch file would simply call the other batch files as required.

For example, you create a snapin pack with licensing.zip as the base name.

Inside licensing.bat you would, essentially, have:

@echo off %~dp0\license1.bat %~dp0\license2.bat %~dp0\license3.bat %~dp0\license4.bat %~dp0\license5.bat %~dp0\license6.bat %~dp0\license7.bat %~dp0\license8.bat %~dp0\license9.bat %~dp0\license10.bat %~dp0\license11.bat %~dp0\license12.bat %~dp0\license13.bat

(Some of the syntax may be off, but the idea is the same. For what it’s worth, the %~dp0 is windows slang for, the current drive and path of the running script, this way you don’t have to hardcode the path to find these other files.)

Resolve with this :

Web FOG Settings :
-FOG Client - Hostname Changer was enabled : Now DISABLED
-General Settings / Change Hostname early was enabled : Now DISABLED

After disable this two settings it’s ok …

Problem solved.

@NT_Tech product key censor?? thx tho, i’m saving your stuff for future reference too.

Has there been any progress with this issue. I am having the issue where the “_” flashes but goes no further and I have been searching for a solution for the past 3 days.

In my case, I am attempting to boot a WinPE Environment to run a 3rd party application.

I tried both clean boot.wim files from Win7 and Win10, both fail. But when booted from a USB Drive or CD the application boots.

Everything worked perfectly when I was running 1.5.0 but no longer in 1.5.4.

Dell PowerEdge 910
Windows Server 2016

DHCP
** Option 66 - IP of CentOS 7 Server Running Fog
** Option 67 - undionly.kpxe DNS Hyper-V
** CentOS 7
** Fog 1.5.4
** 16 Cores
** 128GB Ram

0_1531514314481_PXE Boot to WinPE boot wim stalls.png

It will sit here forever.

@restlesshustle As outlined in the wiki page use the setupcomplete.cmd batch file to reenable the service or you can do it in the unattend.xml file in the first login if you have auto admin login set up after oobe finishes.

@aspiringtow that is correct.

@davido38 I can tell you that we have 7010s and they will not pxe boot past the ipxe kernel. I haven’t found any kernel that will work. Its something specific with the firmware on the 7030 model. Bios mode works correctly for that model.

Noted. This makes sense.

@varun-r Please provide:

A screenshot or well-focused photograph of the error. FOG Version FOG OS Information about your DHCP setup - like what OS is doing it, any current special settings, etc. Model of the hardware you’re trying to capture/deploy. Have you had FOG working in any capacity prior to this?

@tom-elliott said in After update to 1.5.3 node offline and unable to PXE boot.:

selinux is set to permissive or disabled

well that was it. it was disabled before never thought of looking at that. i turned it to permissive mode. i was able to boot to my fog Server. we had a power outage it must of defaulted back to enforcing. thanks appreciate it.

Take a look at https://wiki.fogproject.org/wiki/index.php/FOG_Client#FOG_Client_with_Sysprep

If I’m understanding you right, that is.

Couple of things to check:

Is the original machine in BIOS or UEFI mode? Is the target machine in BIOS or UEFI mode? If both are in UEFI mode, you may have to manually add the boot option in the UEFI of the target machine.

Thanks for the reply. I never noticed it before.