@Tom-Elliott

Your command has changed something.
Now, it runs “single snapin” only on the host that have it added (it means only 1).
Is this normal ? lol

edit : Found out, with Thomas, that I have to associate this snapin to each host to create a working task for every host using group single snapin task.

This works now. Thanks All.

@cleric.marcos You’re more than welcome. I do want to say I did very little to help anything here. I think @george1421 deserves more of the kudo’s here than I do.

Juste une légère correction, tout fonctionne jusqu’à ce que j’essaie de télécharger le noyau mis à jour, puis je reçois la même erreur que rdaval3.

Aucune erreur n’a été signalée dans le journal des erreurs apache.

English:
Just a slight correction, everything works until I try to download the updated kernel, then I get the same error as rdaval3.

There is no error posted in the apache error log.

@george1421
Thanks a alot 🙂
that works now

@BardWood If you still have the original backup file from when you upgraded the server originally, this would be your best bet. It should be in /home/fogDBbackups

It typically is time stamped.

Once you reinstall 1.2.0, you’ll need to use the backup sql file to restore it as a lot changed in the DB between the two.

Also remember, with the exception of WOL, Shutdown and Restart “on demand” Power Management items are not “immediate”. As @Junkhacker stated, they require the New FOG Client on the systems to be “tasked” and they will be performed on the next time the check in with the FOG Server.

@Tony-Ayre https://wiki.fogproject.org/wiki/index.php?title=Location_Plugin

@cajos001 one might wonder if there’s a powershell way to add local printers?

Maybe something like this ps script from our friends at Admin Arsenal: https://www.adminarsenal.com/blog/how-to-add-printers-with-powershell/

FWIW: Power shell scripts can be deployed as a FOG snapins. I might suspect that someone with a bit of skills could deploy the driver to the remote host and then run a powershell script to add it to the windows environment.

While I doubt this will fix the problem, I do hope to have a nicer approach to having a device receive an IP Address now.

As stated before, the current mechanism just waited for “ANY” ip address to be assigned to any NIC as needed. As long as it received an IP address (regardless of if that IP could communicate to the FOG Server) it would break out and try “driving” forward with the tasking.

I’ve added what I hope will allow a more dynamic approach to detecting the real fog network. Would you mind giving a try using the init’s and instructions here:

wget -O /var/www/fog/service/ipxe/init.xz http://mastacontrola.com/init.xz wget -O /var/www/fog/service/ipxe/init_32.xz http://mastacontrola.com/init_32.xz

With this, you’ll also get the latest fixes from last night in regards to resizing code bits and what not. (This isn’t a bad thing)

@Wayne-Workman Thank you, that’s exactly what I needed! Problem solved.

@ch3i
Okay, I’ll test that and let you know. Thank you for your help.

@george1421 That will be overwritten the very next time he updates fog unless the blexports option in /opt/fog/.fogsetting is set to 0

You can edit this file with vi or nano and set that option to 0. This way the changes that George suggests will stick the next time you update fog.
Reference:
https://wiki.fogproject.org/wiki/index.php?title=.fogsettings#NFS

This is a Face Palm picnic error!

I was updating the main fog settings. I was thinking if I changed that setting it would change it for all hosts. I forgot I have to edit the host information to make a change to a existing host. (Did this via a group)

Still, my username and password hadn’t changed between the fog upgrade, so something was wrong, but I should have spotted my error when trouble shooting 🙂

This ticket can be closed

Good day,
issue is solved; line 060 was being used by WDS server, which is inactive for some time and we do not use it anyway. It was agreed to disable this line and so FOG server is already running smoothly - 40 GB test image deployed on testing PC within 3 minutes. AWESOME! Plus I’ve managed to integrate few utilities such as Clonezilla, Clonezilla Server Edition (or DRBL live), System Rescue CD, PMagic, GParted and AVG Rescue CD.

Will come back with other questions; thanks so far!

@oraniko Either you want us to help you fix the issue or you want to do your own thing.

FOG RC 15 and 16 where both released 15 actually hopefully having a fix to the problem you’re describing.

If you really want to go back to 1.3.3 that’s up to you, but doesn’t help us fix what the problem actually is.

@IhaveNoIdea said in Help with school project:

And now i got another question, i have movable hard drive where i have installed linux and fog. The main hard drive in computer is win 7 and can fog clone it and make image off it?

The way I interpret that is the computer has two disks in it, and he’s got Linux + fog on one, and Windows on the other. Still the second disk cannot be imaged by FOG if it’s in the same system that is running FOG - at least not literally like that anyways.

@george1421 George hooked me up after sending him a screenshot. Turned out to be something incredibly simply on my part–search scope was set to “Base and Subtree” instead of “Subtree and below”. I seriously compared these side by side I don’t know how many times, but my brain was not seeing that difference for some reason.

Really appreciate the help!

@george1421
I had Pxelinux.0 in my dhcp, the new code replace it now.

@oraniko yes you found that pxelinux.0 is not wanted/needed with the current version of fog.