Windows 8.1 mode isn’t enabled, so Secure Boot shouldn’t be doing ANYTHING. I have the machine sitting next to me, so any steps you can give me would be great.

Yes, I know, we’ve been over this before. But is there any new information on it?

I used the legacy PXE client to image Windows 8.1 UEFI. When the system boots, it complains about winload.efi. I can fix the error by running “bcdboot C:\Windows” from WinPE and deleting the extra boot option. However, I don’t want to do this on every computer I image (I’ve got 25 in waiting).

I also would really hate to completely redo this image, and I know that I can make bcdboot copy legacy boot files, so it’s not too big of a deal if we can’t get UEFI booting working. But, can we?

That wasn’t turned on, but FOG_NEW_CLIENT was. Must have been a test I forgot to change back.

Thanks, everyone!

Ah, I see. No matter what I put in the FOG_AD_DEFAULT_PASSWORD field, it changes back to what I had before.

Here’s the apache error that occurs when I try to change it:

[CODE][Wed Dec 17 11:52:15 2014] [error] [client 10.1.2.110] PHP Warning: mcrypt_decrypt(): The IV parameter must be as long as the blocksize in /var/www/fog/lib/fog/FOGBase.class.php on line 268, referer: http://fogserver/fog/management/index.php?node=about&sub=settings
[/CODE]

Yes. This worked at one point. I’ll try to re-encrypt the password, though.

No dice. But the error is different now.

[CODE] 12/16/2014 4:35 PM FOG::HostnameChanger AD mode requested, confirming settings.
12/16/2014 4:35 PM FOG::TaskReboot No job exists for (There’s no reason to remove this)
12/16/2014 4:35 PM FOG::TaskReboot No task found for client.
12/16/2014 4:35 PM FOG::HostnameChanger Additional non-parsable characters are at the end of the string.
12/16/2014 4:35 PM FOG::HostnameChanger at System.ParseNumbers.StringToInt(String s, Int32 radix, Int32 flags, Int32* currPos)
at System.Convert.ToByte(String value, Int32 fromBase)
at FOG.FOGCrypt.hexToByte(String hex)
at FOG.FOGCrypt.decryptHex(String hex)
at FOG.HostNameChanger.changeHostName()[/CODE]

I set the FOG service to delayed startup. Still the same issue. On a a system with an incorrect hostname, the hostname will not change. This is ONLY if the client is set to be joined to AD.

[CODE] 12/16/2014 12:49 PM FOG::HostnameChanger Attempting to connect to fog server…
12/16/2014 12:49 PM FOG::HostnameChanger Module is active…
12/16/2014 12:49 PM FOG::HostnameChanger AD mode requested, confirming settings.
12/16/2014 12:49 PM FOG::UserTracker Module is active…
12/16/2014 12:49 PM FOG::PrinterManager Module is active…
12/16/2014 12:49 PM FOG::HostnameChanger Could not find any recognizable digits.
12/16/2014 12:49 PM FOG::PrinterManager Starting printer manager…
12/16/2014 12:49 PM FOG::PrinterManager Yielding to other services for 36 seconds.
12/16/2014 12:49 PM FOG::HostnameChanger at System.ParseNumbers.StringToInt(String s, Int32 radix, Int32 flags, Int32* currPos)
at System.Convert.ToByte(String value, Int32 fromBase)
at FOG.FOGCrypt.hexToByte(String hex)
at FOG.FOGCrypt.decryptHex(String hex)
at FOG.HostNameChanger.changeHostName()[/CODE]

You want the FOG service to be set to Automatic (Delayed)?

I can confirm this. The hostname changes if the computer is not marked to add to AD. However, it still won’t join the AD after it’s been marked to do so.

2811 works! Thank God!

Rather, thank Tom Elliott.

The problem with undionly.kpxe is one model of machine we have (With an ASUS M4A78L-M motherboard) don’t get past “iPXE initialising devices”. Undionly.kkpxe not only works on all of our machines, but it is faster.

The wait lasts forever to my knowledge.

Undionly.kpxe does NOT work for us. And the init is still getting stuck.

Will try on Monday.

Now I remember why I don’t change things on Friday

If I run a task, iPXE stops at /init.xz… ok

I’m using undionly.kkpxe because it’s the only file compatible with all of our hardware.

I hope there’s a log somewhere that you can read.

Same issue with 2789

Oof… Having a read only Friday.

I’ll try later. Not near the server at the moment.

On a newly imaged system, the hostname never changes. Here’s the relevant section of the fog.log:

[CODE] 12/12/2014 12:25 PM FOG::HostnameChanger Attempting to connect to fog server…
12/12/2014 12:25 PM FOG::HostnameChanger Module is active…
12/12/2014 12:25 PM FOG::HostnameChanger AD mode requested, confirming settings.
12/12/2014 12:25 PM FOG::HostnameChanger Could not find any recognizable digits.
12/12/2014 12:25 PM FOG::HostnameChanger at System.ParseNumbers.StringToInt(String s, Int32 radix, Int32 flags, Int32* currPos)
at System.Convert.ToByte(String value, Int32 fromBase)
at FOG.FOGCrypt.hexToByte(String hex)
at FOG.FOGCrypt.decryptHex(String hex)
at FOG.HostNameChanger.changeHostName()[/CODE]

Don’t know if it’s related, but there appears to be an issue with AutoLogOut as well.

[CODE] 12/12/2014 12:25 PM FOG::AutoLogOut Module is active…
12/12/2014 12:25 PM FOG::AutoLogOut Timeout value is Zero, disabling module.
12/12/2014 12:25 PM FOG::AutoLogOut The path is not of a legal form.
12/12/2014 12:25 PM FOG::AutoLogOut at System.IO.Path.NormalizePathFast(String path, Boolean fullCheck)
at System.IO.Path.GetFullPath(String path)
at System.Drawing.IntSecurity.UnsafeGetFullPath(String fileName)
at System.Drawing.IntSecurity.DemandReadFileIO(String fileName)
at System.Drawing.Image.FromFile(String filename, Boolean useEmbeddedColorManagement)
at FOG.AutoLogOut.doWork()[/CODE]

I’ve also attached the full fog.log

EDIT: The full log appears to have sections omitted. Well, you have what I know.

[url=“/_imported_xf_attachments/1/1553_fog.txt?:”]fog.txt[/url]

I’ll be darned. That took care of it.

[Wed Dec 03 16:24:04 2014] [error] [client 10.1.2.110] PHP Fatal error: Call to undefined function mcrypt_get_iv_size() in /var/www/fog/lib/fog/FOGBase.class.php on line 266, referer: [url]http://10.1$[/url]

To be exact

If I go to a host’s (or group’s) Active Directory settings, check the “Add to Active Directory” box to autofill the options, and click “Update,” I get taken to a blank screen and the update does not occur. The page has no body that I can see in Chrome’s Inspect Element.

This also happens when clicking, “Save Changes” in the FOG Configuration page.