I appreciate what you do for FOG. If you need VM space, you know you can give me a hollar.

There’s a copy of fog and fog-community-scripts stored in the arctic printed on film that will last over a thousand years.

I think that is simply awesome.

Primary: https://archiveprogram.github.com/

Others:

• https://www.datacenterknowledge.com/open-source/githubs-arctic-vault-makes-sure-open-source-code-survives-apocalypse
• https://hackaday.com/2020/07/29/ask-hackaday-why-did-github-ship-all-our-software-off-to-the-arctic/

@WalterT This post is completely unhelpful to yourself and to the fog community, and seems rash as well. If you need help with getting fog setup, create a thread about your specific problem, provide details, screenshots, logs, information. The community will help you as best as possible after you provide basic details about your specific issue.

Ok…

I’m feeling pretty ignorant at the moment.

I got to messing with this again and was able to try out a new unmanaged 1Gbps Cisco switch with it and I went through several different configurations in my tests and kept getting inconsistent results.

I have finally found out what the issue was. It was a bad patch cable the whole time.

That’s pretty shameful on my part as a technician, but it would be more shameful to conceal my mistake and not report what the issue was.

I do believe I exhausted every single other possible option before I realized it was the patch cable. Checking simple things first is hammered into all of us as troubleshooters, and the lesson has definitely been reinforced in me.

I come from Semantic Ghost background.

Fog is MUCH faster, supports queuing, renaming, joining to the domain, and there is ample support and high-responsiveness on the forums, with ample materials available in the wiki as well.

FOG images in general compress very well. 40GB compresses down usually to about 19GB on the server’s disk.

It’s free - not free like free beer, but free as in you may freely examine the code, freely make copies, freely make changes to your copies, freely distribute it under the GNU GPLv3 License, free to charge for it even, if you can (although I doubt you’d be successful)! The GNU GPLv3 allows for all of these things, as long as the License is respected and provided with copies and changes, and as long as all changes are completely open source and available to the public.

FOG can serve as a reliable DHCP server for you, offering more control and more options than Windows Server 2008 and below did (see our article on BIOS and UEFI Co-Existence).

FOG bridges the imaging gap for OSX, Linux, and Windows, and provides a management client for all three that can name them, join them to the domain, and run snapins on - all from a common web interface.

FOG can manage printers for you, allowing you to avoid cluttering up your domain controllers and group policy.

I use WOL to wake computers up on a schedule easily, and during breaks like spring break and winter break, I can easily disable it.

I use the fog client to push out Chrome updates regularly - with absolute ease. Using snapins also keeps group policy on computers and domain controllers less cluttered.

FOG logs logins for me, which I was previously logging using advanced scripting techniques that only I understood in my organization. Now, just using the web interface technicians can see login history for a computer or individual.

Fog supports wiping HDDs, and I can integrate ISOs into fog without much trouble.

Used to be, imaging a lab was a two to three person job for several hours with Ghost, and now it takes one single technician under 30 minutes - all of which are spent standing around and making sure things go smoothly. For example, we don’t have to name computers because fog does this. We don’t have to join to the domain because fog does this.

Please don’t disrespect CloneZilla in your report. Comparing it to FOG is unfair. It’s comparing apples to oranges. CloneZilla has strengths where FOG has weaknesses, and vice versa. For instance, if there are strict regulations on a network that a individual technician is not allowed to change, CloneZilla could be the winner in that scenario. If the network performs poorly, has problems, is slow, or non-existent, CloneZilla is the clear winner. If a technician does not have a server or old computer to dedicate as a FOG server, then CloneZilla is the winner. Also, CloneZilla is the most simple way to clone a FOG server! Where CloneZilla has weaknesses, FOG far excels. And where FOG excells is using your network to get work done - and fast. Bottom line is - CloneZilla is free open source software and has it’s place in the computer imaging industry and it should be respected for what it is.

@ITSolutions said in DNS Name Goes to Old FOG Installation:

Ubuntu moved the default location for web pages in 14.04 from /var/www to /var/www/html. FOG is designed to do a symlink back to /var/www, but maybe something broke in that.

I think that statement there is what’s going on.

So, if you use the host name, you are taken to 1.2.0 interface, but if you use the IP you are taken to fog trunk interface.

This means that the web files for 1.2.0 obviously still exist, and the trunk files are there too.

If it were me, I’d delete everything in /var/www EXCEPT for the html directory, and I would delete everything INSIDE of /var/www/html and re-run the installer. That should fix it.

So for instance if you saw some-folder inside /var/www you’d do rm -rf /var/www/some-folder That’s a recursive delete command. same goes for everything in the other.

You can list the contents of the directory, including hidden files, with ls -la

People that are new to fog don’t see the value in registering normally - and that’s OK. But fog comes to life with registered computers - automatic host naming, automatic domain joining, automated startups, shutdowns, reboots, software & script deployments, printer management, tracking of who logs into and out of said computers, inventory reports, imaging history, and many other things. Many of FOG’s features, you cannot use without registering.

And after you try out registering & using these features, you will start to understand how unnecessarily hard you were working before.

the WiKi SVN article somewhat promotes upgrading to the developmental revisions…

I really think that the other upgrading methods should be ditched, IMHO. But others here feel otherwise.

At the least, the Upgrade To Trunk article and the SVN article ought to be merged. I’ve thought about doing this, but the SVN portion would be huge compared to the others, and I just haven’t gave it much time nor thought.

And I’m not “In” enough to maintain the news section.

Sad truth is, although Tom is fuc**** awesome at what he does, he is largely a one-man-army and he has a full time job and wife and so on. He’s the driving force behind FOG.

JBob comes in 2nd, with massive improvements to the new FOG client.

The other developers aren’t active enough (IMHO) to be able to keep the news section updated.

And me,

I’m a forum troll, and I help people as I can, but I’m not “in” enough to keep it updated (IMHO).

I’m more than willing to try, but I may fall short sometimes…

Over the last few weeks, working with Tom, I was able to test changes back and forth over for Ubuntu 16 and Debian 8.

Both now install without modifications, without special commands.

Install Debian 8, just pull down fog and run the installer as normal. It works.

Install Ubuntu 16, just pull down fog and run the installer as normal. It works.

@Developers @Moderators @Testers

Just created this article:

https://wiki.fogproject.org/wiki/index.php/BIOS_and_UEFI_Co-Existence

@david201 You might be better off getting this out of Docker. Here are steps on how to migrate FOG. If you have the right switches enabled in the hosting OS, you should be able to mount NFS inside of the container. Otherwise, there are other ways to get the images & things out.
https://wiki.fogproject.org/wiki/index.php?title=Migrate_FOG

FYI, there is now a tool that can renumber your images for you, here it is:
https://github.com/FOGProject/fog-community-scripts/tree/master/RenumberImageIDs

These graphs are from the new FOG Reporting. They are updated every hour. Link to the full dashboard is in my signature.

Tried emailing chuck, he has not replied. For now, I’ve removed all of the fogproject.org references, and HTTPS is working directly (redirect does not work). This is fine until Chuck can help with the DNS records.

@sebastian-roth Right, the alias is fine, please leave it as-is.

I tried without the subject alternative name and got browser errors related to SSL. The front-end is in AWS CloudFront, which uses AWS ACM for ssl certs. I can’t make a cert with the fogproject SAN in it without the verification. Right now, it’s not set-up as I figured we wanted to get the redirect working right. If that can’t be done, no big deal.

@Sebastian-Roth if you can get an A record created for stats-api.fogproject.org with a value of 3.20.18.241 I can get the ssl cert and such fixed on my side (using lets encrypt). Once that’s all done, we can update the reporting script to use the new URL.

For the results to have a good redirect from stats.fogproject.org, I need the SSL cert to include that subject alternative name. Please create this record, it’ll allow me to create that SSL cert. These values below are not secrets, and they will timeout in 72 hours from now (sometime wednesday). if it’s not made by then I can get new values. This is part of how AWS verifies the cert your making is legit.

Name:
_395058431eb78e5f8f9cc2478adbdfa3.stats.fogproject.org.

Type:
CNAME

Value:
_ee8469a4f9a938de348ef383be83b11f.zbkrxsrfvj.acm-validations.aws.

If this can’t be done for whatever reason, I can use the original results URL and it’ll work fine, just redirects from stats.fogproject.org won’t work.

Here’s the changes on the cloud side if you were interested.

@Sebastian-Roth So when I try:

curl -X POST -H "Content-Type: application/json"  -d '{"fog_version":"testing","os_name":"testing","os_version":"testing"}' https://stats-api.fogproject.org/api/records

This is the result:

curl: (6) Could not resolve host: stats-api.fogproject.org

Yeah the back-end only takes entries, nothing else.

The frontend url is less important, as that’s not needed in the fog codebase anywhere. It’s just a place one visits to see results. I can get HTTPS setup for it.

Sounds good.

Thoughts on the external reporting DNS name?

Right now it’s: https://fog-external-reporting-entries.theworkmans.us:/api/records

This works fine, but it’s not a fogproject.org address.

If nobody has an opinion, I’m happy to leave it as-is forever, but I think it may be more appropriate if there’s an A Record created like fog-external-reporting-entries.fogproject.org. This can be set to the public IP of the server I’ve setup to record the entries, and also could be easily changed in the future if needed. I’m not immortal, nor is anyone else here so this is why I bring it up.

We really need to get it the way we want it before the next release.