FOG Hangouts

@mgoh You could probably update the size with a sql command if you wanted. Not really a need to do it though.

@brakcounty I’d suggest doing some internet searching before asking general linux questions.

https://duckduckgo.com/?q=ubuntu+ufw+default+rules&t=ffab&ia=web

First result and second result both have the answer.

@mgoh If you don’t have a DB backup, or a recent snapshot of your fog server, you’ll need to recreate the image definitions manually. You must recreate them exactly as they were before:

• The image path must be exact and is case sensitive.
• The image OS and image type must be set exactly as well.

@gjo on the host itself, you can look in the fog client log. You can also look at the “PC properties” and see it’s domain status. in Active Directory Users and Computers, you should see the new computer object. A note on this you might not be aware of, FOG will rename the system to whatever name you have set in the FOG Server for that host, it does this just before domain joining.

When I was doing a lot of imaging, we would set the hostname during Host Registration.

@londonfog Not sure but I don’t think there are API calls for the iPXE menu stuff. I suggest you look into using a SQL query/insert or you might be able to code your own plugin to get what you want.

The count on working branch and dev-branch as of today is 718 fog servers.

@gjo sysprepping is typically run just before image capture. This process will generalize your image to work on multiple models as well as solve some other issues with key management servers, wsus, and is the Microsoft supported way to build an image.

Re: admins, I think a fog plug-in may exist that may help. Memory is fuzzy on this.

Re: fog client, your image has to have the fog client for domain join to work. This means it must be installed on the Golden system from which you take an image.

@BSZAdmin @george1421 Doesn’t look like partition file 3 is missing. I guess it’s the decompression (done on the fly) dying - for reasons I cannot see yet. This would cause this kind of error message.

You can manually try to extract a copy of that file in the server and see if it failes as well. Be aware you need enough disk space on the server to test.

If this works well then I am wondering if it’s faulty RAM in the host machine you want to deploy to. Have you deployed to different machines?

All fog users are basically admins. I’m unaware of how to figure out who’s logged in currently. There may be some details in the apache logs, not sure though.

To join computers to the domain, your image must contain the FOG Client. And, you’ll need to enter credentials into the FOG Server that have the permission to join a host to the domain. Also, your image needs to be properly sysprepped, or configured very carefully if you’re not sysprepping.

@michelbragaguimaraes Not sure if fog supports the new style of slack integration, but last I checked, slack still allows creation of the old style web hooks. Have you tried that?