@george1421 Actually, I’ve just figured it out for the most part. However, is there a way to set it to use the default values already set in FOG?
I’ve updated the JSON to have:
“useAD” = “Y”
This ticks the ‘Join Domain after deploy’ box. I don’t particularly fancy having to tap in the details for the system to join the domain when they’re already configured within FOG itself, though.

@Pere-Pozo-Miro You can learn a lot from this:
https://wiki.fogproject.org/wiki/index.php?title=Replication

@jpaul Ok that error is saying it can’t find the image to deploy. (btw: excellent picture having the kernel variables will help to debug this issue).

Can you post the output of this command. You will need to key it into the linux console of the FOG server. ls -la /images

@YG2018 no need for a snapin pack if your snapin only consists on a batch file, just create a normal snapin from bat (cmd), if your below post is a paste of the contents of your bat file then your are missing a space " " 😉

@YG2018 said in Install snapin packs with elevated command prompt.:

Bat file (uninstall.bat) —> MsiExec.exe /X{A1E58BXX-ECXX-XX19-XXEA-B85CA4F1A2XX} /qn /norestart

It should look like:

msiexec.exe /x {A1E58BXX-ECXX-XX19-XXEA-B85CA4F1A2XX} /qn /norestart

Regards X23

I will try it out and post update here.
All our disks have 2 partitions. which are created by windows when it was installed. system reserved 100MB & rest is 😄 drive. here are pictures i took from FOG…could you help me select correct options. it’s bit confusing for me. our FOG version is 1.5.4

1_1535473437005_3.PNG 0_1535473437004_2.PNG

Dumb switch solved the issue. Please resolved this thread.

Thank you for your assistance.

@george1421 Yup that did it! It was a combination of the Fog server’s firewall as well as my trying to connect to the web interface using the imaging network’s IP instead of the business network IP. Once I disabled the firewall again and tried the other IP I was able to finally reach the web interface.

Thanks for the help!

Tom, Thank you so much for help on this. it did work. i noticed on Fog dashboard. disk space shows 190gb.

@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.