Okay, got it working by checking the box Name Change/AD Join Forced reboot. It never fails that I can look at something for 2 hours and soon as I finally break down and ask everyone, I find the problem. 🙂

Thanks.
Scott

Problem solved, perfect 🙂

@amtiskaw This is not a FOG issue. It depends on so many things and can go wrong easily. Software or hardware RAID controller, model, driver; UEFI or legacy BIOS; …

There is no simple answer to this and I won’t be able to help with this.

Finally, I had to reinstall FOG and everything was fixed.

Thanks guys for the answers.

@aksl well you can edit the refind.conf file in /var/www/html/fog/service/ipxe/refind.conf and change the line for scanfor to look like this

scanfor internal

Save the config file and then attempt booting it again.

@bricktop135 At which stage do you get the cursor on the black screen? Can take a series of pictures or video so we see the whole boot process?

@andrewg78 I’m still thinking its bit locker that is causing your issue. When you use single disk not resizable then clone the image, you are not changing the geometry of the disk. Please read through this post and see if running the commands to disable bitlocker makes single disk resizable work better. https://forums.fogproject.org/topic/10824/image-upload-deploy-taking-a-long-time/43

Looking over the entire thread just for your info.

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

@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.