@RobTitian16 I should ask, did you use the fog installer to setup this storage node?

and, if you run the command cat /var/www/html/fog/lib/fog/config.class.php on the storage node, it’ll output some variables. Three of them will be snmysqlhost and snmysqluser and snmysqlpass They will be towards the top.

You can test those manually from the storage node via CLI as:
mysql -h hostHere -u userHere -pPasswordhere -D fog

Note that there’s no space between the -p and the password, that is intentional. If it lets you in that way, the DB connection is good. Else, it’s bad.

Also, I doubt the getversion file is actually missing. You may search for it with this:
find /var/www/html/fog | grep /getversion.php

@george1421 said in everything installed. But management page not displaying correctly.:

the installer now uses the right php install sequences and the command line variables are not needed when the installer is called?

Correct. It just works now without anything special.

@dureal99d I’m not sure how dd-wrt handles vendor classes, but I’m pretty certain it can.

What’s likely happening with your problem is dd-wrt is only setup to serve a bios boot file, which is why most of your uefi ISOs don’t work.

Perhaps one of the @Developers or @Moderators or @Testers have dd-wrt at home and know how, but you need to set it up to hand out ipxe.efi for uefi identifying machines and undionly.kkpxe for BIOS identifying machines (generally).

If you read through the article I posted you might better understand what you need to do with your dd-wrt router.

Here’s something I found by searching Google for ‘dd-wrt dhcp vendor class’. The thread is probably so old that it doesn’t even apply to the latest version but it might point you in the right direction:
http://www.dd-wrt.com/phpBB2/viewtopic.php?p=643566

Another idea is to turn off dhcp on the router temporarily and then edit the fog servers /opt/fog/.fogsettings file and change do dhcp and bldhcp to yes or 1, and rerun the installer and just see if your ISOs work then. Because FOGs dhcp setup already well supports many architecture types, some of that work I contributed to, it’s solid. To undo this, same steps but turn those two settings off, then manually stop and disable dhcp. For Ubuntu it should be service dhcpd stop;service dhcpd disable

Here is more info on .fogsettings if you get lost or curious:
https://wiki.fogproject.org/wiki/index.php?title=.fogsettings

@george1421 said in UEFI won boot tools via fog menu.:

Wayne has added the info to the FOG wiki page

@Sebastian-Roth did the dnsmasq section I’m pretty sure lol. Seems he’s always a few steps ahead of us.

@dureal99d said in UEFI won boot tools via fog menu.:

should I use fogs built in dhcp server

Yes. The installer will set it up for you perfectly. Earlier in this thread, I described how to change your current server to do this.

@John-Johnson said in Fog update:

@george1421 It is 14.04 but I intend to update that too.

Don’t. It’ll be a disaster. I don’t know of anybody who has successfully updated Ubuntu without screwing up fog. I cannot tell you how many threads we have here where someone upgraded Ubuntu to the next version and all kinds of weirdness and instability and non-functioning happened. And it’s always guesswork about what happened, and it’s painfully slow to troubleshoot, and often faster to nuke and repave - and do it right. I strongly recommend against upgrading the OS.

If you want a newer OS, backup your images and database, sit aside the old FOG Server’s HDD, put in a new one, build from scratch, install fog 1.3.0 RC, and then import your images and database.

@wanderbread ok… so Ubuntu 12 isn’t recommended for the new fog 1.3.0 release candidate, and upgrading Ubuntu has always ended in fog disaster. And your current installation is messed up and on a very old OS, and running a fairly old version if fog.

You need to rebuild.

I’m going to recommend to you that you make a copy of your images to somewhere, they are in /images and then backup your database with thus command and put this somewhere safe too: mysqldump fog > fogdb.sql

And then nuke this server and install something recent like CENTOS 7 or Ubuntu 16, use the same IP, and install fog 1.3.0 release candidate, and after that is done, backup the new database with tge same above command, then import the old database, and move images back over.

@Tom-Elliott said in FOG Client Power Management issues:

Also, you must know that having the client on the same system within multiple boot layout can cause the invalid security token also.

Not can, will.

I have a box in the basement that I have two images for, that I go back and forth between as I need. One is Server 2012 R2, the other is Win10. Of course I have the fog client installed on both images. Every single time I swap to the other image, authentication for the client breaks, and I have to clear the encryption for that host. It’s because there are two OSs reporting in as the same machine. Of course this would cause authentication issues, I would expect it to.

But for me, I understand, and clicking a “clear encryption” button isn’t a big deal to do when I decide to swap to another OS every few weeks for my testing purposes.

@mp12 invaluable information, thank you. I have to sit down and test WOL with @Tom-Elliott and get this resolved ASAP.

6152 is super old, it’s not even a release candidate, and that version of the client you’re using is also very old. This issue is surely fixed in Release Candidate 13. Please update. Follow instructions here and it’ll probably be fixed:
https://wiki.fogproject.org/wiki/index.php?title=Upgrade_to_trunk

Also, if you are sys-prepping your images and are using the new fog client, you need to take these steps in this article concerning sysprep:
https://wiki.fogproject.org/wiki/index.php?title=FOG_Client#FOG_Client_with_Sysprep
If you’re not sys-prepping then you don’t do these steps.

Just tested again to confirm, it works fine on RC-13.

Is this a pre-existing production server or did you build it to try fog?

@Thiago Did you specify a port when you did the test or no? Is CentOS 7 firewalld configured? You can check by running systemctl status firewalld

@Tom-Elliott, yes he did:

@TomBagley said in Hostnamechanger problem on new installation:

I recently rebuilt my Fog Server from scratch

@TomBagley FYI, in the future when you do something like this, you need to follow these instructions:
https://wiki.fogproject.org/wiki/index.php?title=FOG_Client#Maintain_Control_Of_Hosts_When_Building_New_Server

Because you didn’t, you have to un-install and then re-install all the FOG Clients in your environment. If they are joined to the domain, you can script this. Installation arguments for the FOG Client MSI are here:
https://wiki.fogproject.org/wiki/index.php?title=FOG_Client#FOG_Client_0.10.0.2B_Installation_Options

You can uninstall via a .bat script with msiexec /x FOGService.msi or you can use the product code guid if that suites you.

All of your images that have the FOG Client installed will also need to be updated the same way, uninstall the fog client and re-install it, reboot, ensure it’s communicating properly by looking at the log, and then re-capture.

If you have a backup of your old FOG Server, we can help you restore the old certificates to the new server so you don’t have do do all of the above.

@Tom-Elliott said in Upload / Download issue:

you need to change the image from a non-resize mode and capture it as resizable.

That’s the answer.

@TomBagley Since you have your old fog server on hand, you have saved yourself a huge amount of work. Follow the link about maintaining control of hosts when building a new server. Basically you need to get the ssl directory off of the old fog server, put it onto the new server, and re-run the installer. Then you should be good to go.

@RobTitian16 @Tom-Elliott I wrote a BASH script that is working. I’ll make a github project for it soon but here it is:

#!/bin/bash

#----- MySQL Credentials -----#
snmysqluser=""
snmysqlpass=""
snmysqlhost=""
# If user and pass is blank, leave just a set of double quotes like ""
# if the db is local, set the host to just double quotes "" or "127.0.0.1" or "localhost"


#----- Begin Program -----#

selectAllImageIDs="SELECT imageID FROM images ORDER BY imageID"
selectLowestImageID="SELECT imageID FROM images ORDER BY imageID LIMIT 1"

options="-sN"
if [[ $snmysqlhost != "" ]]; then
	options="$options -h$snmysqlhost"
fi
if [[ $snmysqluser != "" ]]; then
        options="$options -u$snmysqluser"
fi
if [[ $snmysqlpass != "" ]]; then
        options="$options -p$snmysqlpass"
fi
options="$options -D fog -e"

lowestID=$(mysql $options "$selectLowestImageID")

#If the lowest image ID is greater than 1, we can renumber all images sequentially.
if [[ "$lowestID" -gt "1" ]]; then
    count=1
    mysql $options "$selectAllImageIDs" | while read imageID; do

        echo "-------------------"
        echo "Attempting to change Image ID $imageID to $count"
        mysql $options "UPDATE images SET imageID = $count WHERE imageID = $imageID"
        mysql $options "UPDATE imageGroupAssoc SET igaImageID = $count WHERE igaImageID = $imageID"
        mysql $options "UPDATE hosts SET hostImage = $count WHERE hostImage = $imageID"
        echo "Attempt completed"
        count=$((count + 1))

    done
fi

Sample output:

[root@fog-server ~]# ./renumberFogImages.sh 
-------------------
Attempting to change Image ID 2 to 1
Attempt completed
-------------------
Attempting to change Image ID 3 to 2
Attempt completed
-------------------
Attempting to change Image ID 4 to 3
Attempt completed
-------------------
Attempting to change Image ID 5 to 4
Attempt completed
[root@fog-server ~]#

@Tom-Elliott said in Change Image ID Number:

@RobTitian16, @Wayne-Workman is correct.

On all the of the “if lines” you must have a space after [[ and before ]]

Tom, you’re correct. And this whole mis-understanding and errors with the script are due to a nodeBB bug. It was stripping out the spaces between the brackets. I’ve checked the script’s original text that I posted by clicking the “edit” button on the post, there are spaces there but the forums isn’t displaying the spaces, so when @RobTitian16 copy/pasted he got a copy without the needed spaces.

@RobTitian16 said in FOG Won't Join Imaged PC to Domain:

I suppose that’s the reason this is failing?

Yup.

The FOG Client is the software that the FOG Server communicates with to do things on hosts post-imaging. The FOG Client also allows for full life-cycle management of your hosts. You would need to update all of your images to have the FOG Client installed and working, and then re-capture your images. If you sysprep, there are special steps to follow linked below. The below link also in general is the go-to place for information about the FOG Client.
https://wiki.fogproject.org/wiki/index.php?title=FOG_Client

If you have further problems, please create a new thread, include details, and the FOG Client log file if relevant.

You can follow steps here:
https://forums.fogproject.org/topic/8730/fog-installer-distro-check