@Tom-Elliott Done - looks like its working now 🙂

@Frank I don’t know if an update is stable until somebody updates and lets me know if prior issues are corrected for.

It’s one of the “cons” i guess of being on Trunk.

While I try my darndest to keep things as functional as I can, with changes can come problems.

@danilopinotti So the admin network and the academic network are on two different broadcast domains, and maybe even further separated logically via Vlans.

Then you just need a FOG server with two network interfaces (and connect each one to each network). You’d have two storage groups, and in each of those, one master node each, pointing to the exact same directory, but a different interface and IP for each (for the two network interfaces). I think it could work.

Or, just totally separate out the admin images and academic images. Have a storage group for each, and put each one on it’s appropriate interface and IP, and give them each a separate folder.

But Tom is probably right, the location plugin would be far more simple - just have two fog servers, one just a storage node for academic. Set each up as a location, and maybe even give each their own storage group, and make each the master of their group.

Lots of options.

But - the thing that I’m most concerned with is keeping the domain information straight. You’ll really, really need to pay attention to that - or you might find all of your computers joined to one or the other domains… and that wouldn’t be good at all. So there’s a whole lot of possibility for a really large failure with this setup.

@Sebastian-Roth Thank you.

@Wayne-Workman Code added.

@Rico Maybe this helps: https://bbs.archlinux.org/viewtopic.php?id=179929

Seams like some kind of weird partclone thing… You might need to create an empty output file first.

As well you want to read this: https://sourceforge.net/p/clonezilla/discussion/Clonezilla_live/thread/4db4b2bd/ (partclone.restore seams to be deprecated and you should use partclone.<fstype>)

@Wayne-Workman I think it’s very close indeed, and do realize there are a lot of things that needed to be changed in order to make gpt/uefi/windows 10 work properly. I’m not really complaining as I’ve used many different coding languages, except php, and completely understand the complexities with trying to perfect a program, but we should have a better idea than “hopefully sometime”. It’s just a little discouraging sometimes.

@greenfog @dylan This has been in our Wiki for quite a while: https://wiki.fogproject.org/wiki/index.php?title=Troubleshoot_MySQL

From my personal experience I would recommend updating to the latest trunk version of FOG. It is much more advanced and I can capture and deploy W10 images without issues.

You need to install “subversion” and then download the latest package with

svn checkout https://svn.code.sf.net/p/freeghost/code/trunk

From there you install as usual. But be aware that updating might not always work flawlessly so I would test it in a non-productive environment and consider a clean install of the trunk version.

@Wayne-Workman said:

@plegrand said:

It’s not our dns servers

You don’t have to use them. You can make your own and direct all hosts to use yours.

I install dynamique DNS with bind and it works fine. Thanks again

@Wayne-Workman thank you for support.
Works like a charm.
Regards

Thanks, Tom.

Yep I have the Trunk version running.
I was hoping to have the ability to Add items to the ‘Advanced Menu’ with the new option in FOG Trunk of creating menu items. Is this possible at all?
or if not would it be possible to create another Sub Menu instead using this feature? (Similar to Advanced Menu) that way I can have network tools/Additional PXE options in a sub menu instead of on the Main IPXE menu.

Hopefully I am making sense 🙂

Thanks again.

@vbelous said:

@Arrowhead-IT If you put it that way then i’m going to create new Ubuntu server in our VM host and then install newest trunk

That’s exactly what I did when I took over where I work too. Never regretted it and learned more than I would have if I just tried to carry on with someone elses setup.

Take a look at the Location Plugin - https://wiki.fogproject.org/wiki/index.php?title=Plugins

It allows you to have a “master” FOG server that you could point all clients to (in terms of the FOG client installed on the computers), but have them image from the server at their building. If you have a computer at your office for repair, you could also switch its location while it’s there to image and then switch it back once it’s returned to the building. We use this plugin very successfully with 24 sites, although we only have two FOG servers total since our WAN links are all 1Gb or better.

@Wayne-Workman

That’s also in the works. Again, it’s for the stop gap in between time. The clients are laptops that students roam with, and due to them being on wireless with cached logins, group policy takes longer than I’d like to roll out.

I’ll throw it into PDQ deploy though, that should handle it pretty fast. Thanks for your help and input!

I switched this back to a normal topic as opposed to an unsolved/solved question. This is something trying to get information on a new version of fog and the title is far too vague to give a proper “answer”. Even if it asked when 1.3.0 was going to be released its still not a Solve/Unsolve question. I prefer to use the solved/unsolved questions for bugs and/or features.

@Tom-Elliott

Ok so you would recommend switching to the latest version from the trunk of the repo? I will try that tomorrow.

Yes, I exchanged all the IP addresses with hostnames because my FOG server has different IP addresses depending on the NIC the client is connected to. I think it will work once the dns system works properly with the dns server address provided by the DHCP server.

I keep you updated when I tried with the latest version.

Thanks
Marcel

@sayeed said:

Hi Wayne,

i have installed fog on 250Gb Hdd in my local system, which is not sufficient space for me to save all the images.that’s why i have mounted my NAS storage /storage on fog server.but im unable to configure my /storage on fog,kindly provide the guide to mount my storage on fog…or provide the notes for make softlink between fog and my NAS so that i can save multiple images on NAS.

Linux cannot re-export a directory that is already remote. You shouldn’t mount the NAS on the fog server itself.

You should configure it as a storage node in the FOG web GUI, and create an NFS share on the NAS and an FTP user with full access to that share.

in the NFS share, there should be /storage/.mntcheck and /storage/dev/.mntcheck

/storage should be read only, /storage/dev should be read write.

FTP needs full access to the entire /storage directory.

Depending on the type of NAS (like Synology), you will need to move to FOG Trunk (like Tom said).