If you expand each option on the Fog Settings page individually, the missing bits are not visible. Only Expand ALL shows the missing bits and only at the top of the list, not where you’d expect them to be.

No they do not.

Server

• FOG Version: 1.3.5 RC10
• OS: CentOS 7.x

Client

• Service Version: n/a
• OS: n/a

Description

Visiting Fog Configuration page, then Fog Settings, the information displayed for Fog Boot settings is malformed:

FOG_PIGZ_COMP
FOG_REGISTRATION_ENABLED
FOG_KERNEL_DEBUG
FOG_KERNEL_LOGLEVEL
FOG_WIPE_TIMEOUT

After selecting Expand ALL, the missing bits appear at the top of the page before Active Directory Defaults.

Hmm, 2nd and 3rd time around upgrading RC8 to RC10 I cannot reproduce it.

Upgrading from RC8 to RC10 it happened again.

Nothing to report from the apache log, but here are some snippets from fogproject/bin/error_logs/fog_error_1.3.5-RC-10.log .

xinetd-2.3.15-13.el7.x86_64
New password: Retype new password: Changing password for user fog.
passwd: all authentication tokens updated successfully.
Failed to execute operation: Invalid argument
● mariadb.service - MariaDB database server
   Loaded: loaded (/usr/lib/systemd/system/mariadb.service; enabled; vendor preset: disabled)

Feb 21 11:05:46 xyzfog systemd[1]: Started MariaDB database server.
ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using password: YES)
ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using password: YES)
Signature ok
subject=/CN=10.12.40.14
Getting CA Private Key
ln: failed to create symbolic link ‘/var/www/html/fog/fog’: File exists
● httpd.service - The Apache HTTP Server
   Loaded: loaded (/usr/lib/systemd/system/httpd.service; enabled; vendor preset: disabled)

Feb 21 11:07:36 xyzfog systemd[1]: Starting The Apache HTTP Server...
Feb 21 11:07:36 xyzfog systemd[1]: Started The Apache HTTP Server.
Saving to: ‘/home//fogDBbackups/fog_sql_1.3.5-RC-10_20170221_110738.sql’
     0K                                                        0.00 =0s
2017-02-21 11:07:39 (0.00 B/s) - ‘/home//fogDBbackups/fog_sql_1.3.5-RC-10_20170221_110738.sql’ saved [0/0]
‘./10secdelay/i386-efi/intel.efi’ -> ‘/tftpboot/./10secdelay/i386-efi/intel.efi’
cp: cannot create regular file ‘/tftpboot/./10secdelay/i386-efi/intel.efi’: No such file or directory
‘./10secdelay/i386-efi/ipxe.efi’ -> ‘/tftpboot/./10secdelay/i386-efi/ipxe.efi’
cp: cannot create regular file ‘/tftpboot/./10secdelay/i386-efi/ipxe.efi’: No such file or directory
‘./10secdelay/i386-efi/realtek.efi’ -> ‘/tftpboot/./10secdelay/i386-efi/realtek.efi’
cp: cannot create regular file ‘/tftpboot/./10secdelay/i386-efi/realtek.efi’: No such file or directory
‘./10secdelay/i386-efi/snp.efi’ -> ‘/tftpboot/./10secdelay/i386-efi/snp.efi’
cp: cannot create regular file ‘/tftpboot/./10secdelay/i386-efi/snp.efi’: No such file or directory
‘./10secdelay/i386-efi/snponly.efi’ -> ‘/tftpboot/./10secdelay/i386-efi/snponly.efi’
cp: cannot create regular file ‘/tftpboot/./10secdelay/i386-efi/snponly.efi’: No such file or directory
‘./10secdelay/ldlinux.c32’ -> ‘/tftpboot/./10secdelay/ldlinux.c32’
‘./10secdelay/libcom32.c32’ -> ‘/tftpboot/./10secdelay/libcom32.c32’
‘./10secdelay/libutil.c32’ -> ‘/tftpboot/./10secdelay/libutil.c32’
‘./10secdelay/memdisk’ -> ‘/tftpboot/./10secdelay/memdisk’
‘./10secdelay/menu.c32’ -> ‘/tftpboot/./10secdelay/menu.c32’
‘./10secdelay/pxelinux.0’ -> ‘/tftpboot/./10secdelay/pxelinux.0’
‘./10secdelay/pxelinux.0.old’ -> ‘/tftpboot/./10secdelay/pxelinux.0.old’
‘./10secdelay/pxelinux.cfg/default’ -> ‘/tftpboot/./10secdelay/pxelinux.cfg/default’
cp: cannot create regular file ‘/tftpboot/./10secdelay/pxelinux.cfg/default’: No such file or directory
‘./10secdelay/vesamenu.c32’ -> ‘/tftpboot/./10secdelay/vesamenu.c32’

@Junkhacker The majority of my images are ~55 GiB compressed, 85-115 GiB deployed. And yah, Autodesk and Adobe products suck it up real good.

I had this happen on 19 servers (no storage nodes) of varying versions 1.3.0 + up to and including RC5.

No relevant indicators or errors in /var/log/httpd/error_log or /opt/trunkgit/fogproject/bin/error_logs .

Server

• FOG Version: 1.3.5 RC8
• OS: CentOS 7.x

Client

• Service Version: n/a
• OS: n/a

Description

In-place upgrading versions of 1.3.0 and later with 1.3.5 RC8, the iPXE Boot Menu option of ‘Boot Key Sequence’ is being reset from its intended setting to ’ - Please select an option - '.

This is what I do with CentOS7:

echo "Make Apache Default Web Page default to <servername>/ instead of <servername>/fog/"
sed -i.bak "s|DirectoryIndex index.html|DirectoryIndex /fog/index.php index.html|g" /etc/httpd/conf/httpd.conf
sed -i.bak "s|/management|/fog/management|g" /var/www/html/fog/index.php

The first part is in Apache’s documentation. The second part cinches the knot.

What we use for our M72z with BIOS - f6kt43a :

For Legacy Network Boot (undionly.kpxe):

- POWER UP / hold [F1]
- Menu EXIT  \ OS Optimized Defaults = [disabled]

- Depress:  [F9] … to load setup default configuration

- Menu Startup \ Primary \ Automatic \ Error Boot Sequences
1st device = [Network 1]
2nd device = [SATA 1]

For UEFI Network Boot (ipxe.efi):

POWER UP / hold [F1]
- Menu EXIT \ OS Optimized Defaults = [ENABLED]

- Depress:  [F9] … to load setup default configuration

- Menu Security \ Secure Boot \ Secure Boot = [disabled]

- Menu Startup \ Primary \ Automatic \ Error Boot Sequences
1st device = [Network]
2nd device = [SATA]
3rd device = [USB HDD]

- Menu Startup \ CSM = [disabled]
- Menu Startup \ Boot Mode = [UEFI]

I just tested this out with 1.3.5 RC5

To expand further:

Windows Registry Editor Version 5.00

; delete a registry key
[-<HIVErootkey>\<keyname>]

; delete a registry value
[<HIVErootkey>\<keyname>]
"<value>"=-

; delete only the value data of a value
[<HIVErootkey>\<keyname>]
"<value>"=""

A great starting point

Looks like you mean to say the following to list available branches:

git branch -a

Okay, let me put it another way.

Does the default FOG setting for `Exit to Hard Drive Type(EFI)’ of EXIT work for anyone?

Server

• FOG Version: 1.3.5 RC3
• OS: CentOS 7.2.x

Client

• Service Version: n/a
• OS:

Description

I’m having fun delving into UEFI systems now and I have a `problem’, or rather a question.

Has anyone got any EFI exit type other than rEFInd to work universally?

‘EXIT’ as an option always elicits a chainloading error for me, while the other options are hit and miss.

Whether it is this RC or happened between 1.3.4 and now, I like what you’ve done to the UEFI network boot. It has solved an issue I had with Lenovo M72z being unable to successfully use any EFI exit type from the FOG menu.

Beauty.

FYI, svn checks out as 6065, but the install reports 6066.

Thank you for the update regarding the SVN repository’s repurposing. This is all good to know.

Thank you for this great info. How about svn or is it not being used anymore?

What are the different development and release branches of FOG and how does one download each?

The circle of logic my head is spinning around is what happens when you have x number of mobile devices that can only connect by using the USBNIC one at a time.

I guess you would be forced to change the host definition before starting each time to avoid auto-naming each subsequent device with the same name.

But then thinking out loud … I’m going to guess that the best practice would then be that the USBNIC must be removed from MOBILEDEVICE_1 before it boots for the first time, so that if there is a pre-installed fog client, it doesn’t confuse the database.