@quinniedid said in FOG Storage Relication:

Also, what port/protocol is used for storage replication or needed in this scenario?

Depends on how you choose to set it up. Using the multi-master configuration that George explained, you just need FTP for replication and port 80 for the PHP scripts on the remote nodes to listen for requests from the master server on.

But, with a 20 to 40Mbps link between your sites, that’s enough to just use fog in the standard way - with one master server and other storage nodes at your remote sites - and you can accomplish sending specific images to specific locations. You’d setup the location plugin - and you’d use FOG’s group-to-group image sharing. There’s no need to export/import anything in this setup and it’s officially supported.

@kte This is an English speaking forum. Please use some kind of online translator. (Ceci est un forum anglophone. Veuillez utiliser une sorte de traducteur en ligne.)
We need more information to be able to help:

Which version of FOG did you install? Any errors when the installer was running? Is this a clean Ubuntu install or some server you already had in production and reused for FOG? Can you connect to the database on the command line? - SSH to your server and try mysql -u root -p - are you able to login? Check /var/www/fog/lib/fog/config.class.php - DB settings defined as DATABASE_USERNAME, DATABASE_PASSWORD and so on.

@george1421 OK, great.

Thank you so much for your assistants and help.

Much appreciated.

@mpatel the second question doesn’t do anything anymore. It is from before the fos system was able to grab dns from dhcp.

The first question is only needed if you’re using fog for dhcp, so no is the correct answer.

yes. zip up all the installers you wish to package together into a single zip file with a single batch install script (let’s call it install.cmd) that runs each executable with its relevant silent install options (these can typically be found at their websites).

zip file contents:

install.cmd 7z-x64.exe firefox.exe firefox.ini ChromeStandaloneSetup64.exe vlc3.exe

install.cmd:

7z-x64.exe /S /D="C:\Program Files\7-Zip" firefox.exe /INI=[FOG_SNAPIN_PATH]\firefox.ini ChromeStandaloneSetup64.exe /silent /install vlc3.exe /S /L=1033

note: you would need to create & include firefox.ini in the zip file along with the relevant firefox installer, as seen above

when you create the snapin pack use:
template: batch file
snapin pack file: cmd.exe
snapin pack arguments: /c “[FOG_SNAPIN_PATH]\install.cmd”

Same issue for me

@loosus456 I should not speak for the @developers, instead I’ll ask them to answer you. What I will say is that FOG is built around the idea of registered, managed hosts. Nearly all of it’s features require hosts to be registered. ‘quick deploy’ I think is one of the very few features that does not require registration…

@mpatel said in Fog setup question:

Do i need to set mysql root password ?

No.

is this correct way for setting it up for private network ?

If that’s what you need, yes.

We have a method where we can boot into fog from a usb stick. Its mainly used for debugging purposes (and MAC computers) but it should work for your request.

Here are the instructions for setting this up: https://forums.fogproject.org/topic/7727/building-usb-booting-fos-image

Pay attention to the requirements and the caveats of booting this way. You will loose some functionality of FOG that is delivered through the iPXE boot menu, but imaging is surely possible booting from a usb stick.

Look at the forum chat bubble for a bit more info.

@john-sayce Ignore this. Either I managed to do as described or the problem was actually something else (because I was tired or stupid) and I’ve broken it then fixed it.

Thanks anyhow.

@wayne-workma Thank you very much for your help, your first question helped me. I never moved the client machine over to the switch, I just ran the FOG Server alone on the switch, once I moved to client over to the switch, the FOG Management was to run and work properly.

If anyone else needs this:

I cheated but it worked for my needs
My personal notes =

Imagelog cleanup
Downloaded MySQL Workbench to complete tasks

See records to be deleted.
SELECT * FROM fog.imagingLog where ilImageName NOT LIKE ‘%<latest image name>%’;

Delete Records (Rerun command until effected rows =0) - due to safety feature in Workbench
DELETE FROM fog.imagingLog where ilImageName NOT LIKE ‘<latest image name>’ LIMIT 1000;

@george1421
Hi George,
I advanced on the problem and i am very confused…
I identify problem is just after post download scripts.
I say that because in my multiple tests if i shutdown computer just after sed, cancel fog tasks and boot on Windows 10 1803 the name is correct !

See screenshot of step where i ientify problem occurs :
In tests where windows computer name is correct i shutdown computer just before this screen.

text alternatif

As i saw rubric “Changing hostname” i search in my 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 …
2 months to identify this !
Problem solved.

Very thanks for your helps and guidance to post download scripts.
I was convinced that it was coming from Windows/Sysprep.

Don’t know why that did not bother Windows 10 1709.

Thanks again 🙂

Thanks Tom

@george1421 ok thanks for the information

@tom-elliott
Thanks Tom

There are a couple of issues that have come up since 1.5.4 has been released that have been fixed in 1.5.5 (still unreleased at this time).

Roll your FOS kernel back to 4.15.2 to get past the mbr/gpt issue. Make sure you download both the 32 and 64 bit PC kernels (not ARM). Edit the www.conf file to update/include these settings, then reboot your FOG server. pm.max_children = 35 pm.max_requests = 2000 php_admin_value[memory_limit] = 256

If you are having issues with multicasting then we will need to have you switch to the 1.5.5 working branch to get that update.

@junkhacker That’s probably the best path to follow actually. There’s no rush for us to purchase everything at once. Worst case we have enough nodes now to get us by if we do need more. Thanks again for the help!

@dholland said in "Copy" image to repository:

I have my fog server at one site, and a fog repository at the other site.

Lets makes sure our terms are the same.

You have a FOG Server at your HQ and a FOG Storage node at the remote location? If this is the case if both the FOG Server (master node) and the Storage node are in the same storage group then replication happens automatically.

In addition at your remote location you will configure the dhcp scope to pxe boot from the IP address of your FOG Storage node.

The last bit of magic you need is to install the Location plugin. Then allocate each server to a plugin location. Finally when you register target computers you will need to assign that target computer to a Location. That way the target computer knows where to pull its image from.

During the pxe boot process the target system will need to make a http lookup call to your FOG Server at HQ but all file transfer will happen with the local storage node.