@Wayne-Workman said in install fog offline:

FOG 1.2.0 is obsolete now, so is Ubuntu 10. And it’s just a bad idea to use anything but the latest LTS version of Ubuntu for a new build.
Until well ago was the official version, this I say, are LiveCD with FOG 1.2. installed so you only have to install and configure.
Fog 1.3.4 still gives errors, we are testing it, so I think this is a good solution to install without connection.

In any case you can always try …

@george1421 OK! At last it’s now working! the info from my friend here : https://forums.fogproject.org/topic/8668/qnap-nas-storage worked awesome! It’s sad that I cannot see the status of my NAS storage on my web fog management->home but I could see it on my NAS

@Smennywheek to debug the client, look at / provide the C:\fog.log file on the host with issues.

@cnkpadobi I’d like you to start with this: https://forums.fogproject.org/topic/6400/usb-boot-uefi-client-into-fog-menu-harder-way

Don’t let the title scare you. Its not really that hard. What you will do here is create an iPXE boot stick that will launch you into the iPXE FOG menu. The only thing that you need to be concerned with is the iPXE kernel have built in usb support for the generic network adapter.

If that process fails we can build a FOS usb boot stick and bypass iPXE altogether.

Thank you

@Wayne-Workman i won the race 😉

https://forums.fogproject.org/topic/9324/parted-magic-for-uefi-bios-boot?page=1

@Tom-Elliott maybe hes asking about the technology a node is talking with the main fog system, (sql, ftp etc.)

Regards X23

@Tom-Elliott It’s working perfectly, thanks 🙂

@Joe-Schmitt
Thank you Joe. Following the steps as described in the wiki worked and fixed it. At first I wrongly assumed that I only temporarily disabled the service and it fixed the issue. Turned out the service needed to be started again after sysprep.

@Tom-Elliott

Perfect! Thank you.

@Chrisjmuk And remember where you cloned the fogproject to for next time. Now you have two copies of it on your server. You could probably find them with this:
find / | grep installfog.sh

@Tom-Elliott Yes, “imaged to the server” meaning captured. Thanks for the correct reference Host=deployed, Images=Captured. I was looking at this a different way. We use FOG only for saving images of customized hosts (about 20) in our environment. Thanks!

@Tom-Elliott The script you posted had a few issues, I’ve fixed them up. A mistyped variable in the first loop, and I added code to update the snapinAssoc IDs too so those aren’t lost. I’ve submitted a pull request.

All, the improved script will be available here:
https://github.com/FOGProject/fog-community-scripts

This is just a hold-over honestly. We need a big and comprehensive script to just cleanup and re-order everything. Locations, images, snapins, groups, everything - as well as running cleanup commands that we know fixes stuff and can’t hurt but can only help.

In plainer terms, you can update Ubuntu from an older version to a newer one - sure. But if it fails or leaves fog crippled, we don’t just “know” what went wrong. We don’t know how the old OS was setup, what was installed, how it was configured, and so on. It can be troubleshooted but how long that will take or if it’s successful or not, I can’t tell you. The Developers and Moderators and other community members are normally willing to help people - but your pace is limited to their free time.

So… Last night I wrote an article about migrating fog. For this - we know all the steps, and it’s less risky - and you can follow along with it and work at your own pace instead of relying on us.

If you’re strong with Linux and you’re Google-Foo is up to snuff, sure upgrade your OS. If you’re a newbie in a crunch don’t want risks, migrate.

found this post from @cml and tried the image from there!

https://forums.fogproject.org/topic/4782/help-usb-boot-fog/25

It works with 1.3.1 RC6! Thank you man!

Can be closed here

@Joseph-Hales it deals with the firmware that might be applied. while this is typically reset on reboot, windows firmware applied holds in the NICs ROM. The fog inits load their own firmware in a temporary state.

@george1421
Thank you! I’ll check it out.

This article has also been updated with instructions detailing how to do this:
https://wiki.fogproject.org/wiki/index.php?title=Upgrade_to_trunk