mysql

[george1421]

@fredlwal Is there a button on that screen to do just that?

Also what version of FOG is on the new server?

[fredlwal]

@george1421 there is no white botton and its ver:1.3.4 but it was the .gz file install.

[george1421]

@fredlwal Ok this post confuses me a bit. Where did the .gz file come from?

The typical process for installing FOG on a new system is this.

cd <path_where_you_want_the_install_files_install_files>
git clone https://github.com/fogproject/fogproject.git
cd <path_to_your_install_files>/fogproject
cd bin
./installfog.sh -y

That process requires internet access of the fog server. But it will build your fog server for you. There is a step during the build process where it will ask you to go to the management page and create the database. The installer will wait until you go to the web site to create the database. Once the database has been created then go back to the installer and press enter to continue the setup. That is the process.

[fredlwal]

@george1421 I just installed it from a file that I downloaded but now I’m using the upgrade to trunk method.

[fredlwal]

@george1421 I’m able to get to the web interface, now will I be able to just copy the images off the external hard drive onto the new fog server and how do I get the new images to show up in the list?

[george1421]

@fredlwal The quickest is to manually recreate the image definitions.

If you have 1.2.0 still functional. Just copy and paste between the management interfaces. If you have more than a handful of images (<10) the copy/paste process is the quickest and best.

[fredlwal]

@george1421 so do I have to recreate the image again? Or do I just change settings on the new fog server?

[george1421]

@fredlwal You copy the files from your portable hard drive back to the /images directory on new server.

Then you have to manually recreate the image definitions via the web gui. This will then link the the physical files with the web gui

[fredlwal]

@george1421 How do I change my fogserver to hand out DHCP but on a standalone network , how would I make changes to become a standalone server?

[george1421]

@fredlwal You would make that choice when you ran the fog installer to enable the dhcp server in the FOG server.

Do you have an isolated deployment network or does your FOG server span two networks?

[fredlwal]

@george1421 I can isolate it by unplugging the cable that’s to the main network .

[fredlwal]

@george1421 my co-worker was thinking we should keep it on the network to deploy it within the building. He wanted to know what needs to go in Windows DHCP option 67? Where is that file located?

[Jaymes Driver]

@fredlwal that would be the boot file you choose to use.

In most cases it will be undionly.kpxe but you are welcome to use some of the other boot files located on the fog server at /tftpboot

[george1421]

@fredlwal I can say that its easier for you to keep it on the business network, or at least can reach the business network. Many systems require access to a Windows DC as part of their setup (to connect to the domain, and such).

To answer your question (and anticipate the next one).

On your dhcp server you need to enter:
DHCP Option 66 {boot-server}: <ip address of fog server>
DHCP Option 67 {boot-file}: undionly.kpxe (for bios/legacy clients) ipxe.efi (for uefi clients)

If you have a windows 2012 dhcp server you can configure it to dynamically send out the right file name during dhcp setup.

[fredlwal]

@Jaymes-Driver do I copy that file onto the windows DHCP server?

[george1421]

@fredlwal No you do not. All files stay on the fog server.

All you are changing is the dhcp options for the subnet scope you want to pxe boot.

This document may be too complex for what you are doing right now, but it does explain how to setup the windows dhcp server to send out both file names (not the actual file)
https://wiki.fogproject.org/wiki/index.php?title=BIOS_and_UEFI_Co-Existence#Using_Windows_Server_2012_.28R1_and_later.29_DHCP_Policy

[Jaymes Driver]

@fredlwal As George stated, no the files stay on the fog server.

On the Windows DHCP server, you will change options 66 to point to the fog server ip address so that the network knows what server holds the boot file.

And option 67 is the NAME of the bootfile that you want the network to look for.

[Wayne Workman]

This is older but it’s still accurate:
https://wiki.fogproject.org/wiki/index.php?title=Modifying_existing_DHCP_server_to_work_with_FOG

Also, @george1421 and @Jaymes-Driver thanks for picking this thread up, that’s team work.