@Aaron-McLaughlin said in Backing up images:

I tried to do this, but the restored image comes up with a 0 kb size and is unable to be used.

You see the 0 kb size because when re-creating the image definition in the FOG webUI we simply don’t know the size as it is only being recorded when capturing the image.

You are saying the the image cannot be used after copying it back. This can be for various reasons.

File access rights (chmod -R 777 /images/imagename) Path name (Linux is case sensitive, so ImageName is not equal to imagename) Image definition (make sure the new definition does match the old one - resizable/non-resizable, compression method

In some cases the error on screen can shed a light on what is wrong with the image. So please take a picture of the error and post here.

Next time: Don’t touch the image definition in the web UI. Just move images to an external disk to get some space and let the definition alone. After moving it back you don’t have issues with the image definition.

Seems legit. May have to try that out.

@EAHarvey FOG supports basically all iPXE can support and then some in terms of UEFI. Do note that this does not mean all hardware will function as expected, since a lot of manufacturers decide to ignore the spec and do their own thing or some devices are so new the iPXE drivers aren’t updated for them yet.

Still, in most cases, it will work wonderfully.

@vincitytaymodaimo said in I have some questions !!!!:

Is there a way to make multiple tasks run one after another for the same host, except using scheduling or crone-style?
What I am trying to understand if I’m able to accomplish a php form with a few checkbox that will make the host do 1 task after another (with reboots in between). I didn’t look yet in the database structure but is there any option right now for, for example, "task1, status (queued, completed, running), task2, status etc.
If there isn’t any, I guess it won’t be very hard to accomplish it unless there are any failed trials I’m not aware of as a user.

I guess you could do something like this using the API.

I noticed there is an auto OS detection code, is it working yet? When does it trying to detect the installed OS, and can it detect a crashed/unbootable OS?

Not sure what you’re referring to here. Where does the OS get auto detected? (this one is problematic anyway, since you can install multiple OS per disk)

Is there a way to pass fog variables from FOG’s PXELinux (such as $mac, $ip, $hostname) to a dos application running from a memdisk image?

Not that I’m aware of. A memdisk image would have no way to access iPXE variables.

Also is there any way to update the database from DOS after the application is over - for example, running a diagnostic dos app and when it returns to dos, make fog server know whether it completed or failed?

Anything scheduled as a task can. Others do not, by default.

I thought of making network drivers load after exiting the application and upload a file to the tftp server named "<mac-address>-completed, then make a line in the init phase checking if the task completed successfully and changing it’s state, or else is there another way to access mysql server from DOS?

There are some driver scripts floating about (postdownloadscripts) that will install drivers after deployment. They don’t report to the database itself, but they do output info to the screen.

Clients never access the database itself, at best they contact the web server which may or may not access the database.

@Redbob Hmm, that’s interesting. Have your tried in non-debug mode again? Failure or does it run through as well? What changed in between? Non-debug and debug mode are not any different while the later one only waits for your confirmations and if variables are set will print more debug information.

No fog does not support this, but you can use a sister linux product called clonezilla to do that. Clonezilla is similar to how the old GHOST imaging solution worked.

my script work \o/

#-*- coding: UTF-8 -*- import requests headers = {'User-Agent': 'Mozilla/5.0'} payload = {'uname': 'fog', 'upass' : 'bar', 'ulang' : 'English', 'login': ''} headers2 = {'User-Agent': 'Mozilla/5.0', 'Referer': 'http://IP/fog/management/index.php?node=host&sub=export'} payload2 = {'fogguiuser' : 'fog', 'fogguipass' : 'bar', 'nojson' : ''} s = requests.Session() r = s.post("http://IP/fog/management/index.php?node=home", headers=headers, data=payload) print ("[+] Connexion OK") s.get("http://IP/fog/management/index.php?node=host&sub=export") u = s.post("http://IP/fog/management/export.php?type=host", headers=headers2, data=payload2, stream = True) mon_fichier = open("C:\\my\\Path\\hosts.txt", "w") mon_fichier.write(u.text) mon_fichier.close() print ("[+] Enregistrement terminé")

thxs for your help.

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