Best posts made by Joe Schmitt

We have created a dedicated repository for community scripts: https://github.com/FOGProject/fog-community-scripts. All scripts in this repository are under the MIT license, and contain a brief README describing basic usage.

@zefanja Just thought I’d let you know that linux auto updating is now working like a charm. Now my work will be to give everything a little polish and double check Mac OS auto updating.

@Fog_Rob each FOG server has a unique identity that a client will “lock into”. Since you changed physical servers, your clients are expecting your old server’s identity.

See this wiki article for how to make your new sever have your old one’s identity

https://wiki.fogproject.org/wiki/index.php?title=FOG_Client#Maintain_Control_Of_Hosts_When_Building_New_Server

I’ve verified that the issue started with 0.11.5 on mono systems. It’s an issue with a library that I use requesting a specific version of mono to be present. I’ll start working on a patch.

@tesparza the file you are running doesn’t appear to be the installer. It appears to be a self extracting archive that contains the installer. Once you give it a path, it should place all of its install files there, including a DXSETUP.exe, which would accept /silent.

My suggestion is to either find a different version of the installer, such as an MSI, or to take the extracted files and create a snapinpack out of them.

@Omar.rodriguez, alright that’s what I suspected when I saw all of the macs. The problem is your installations share the same virtual mac addresses. You can fix this problem by telling FOG to ignore those macs. To quote @Tom-Elliott from https://forums.fogproject.org/topic/8315/response-error-multiple-hosts-returned-for-list-of-mac-addresses

The fix for this is to add that mac address to the FOG Configuration Page->FOG Settings->FOG Client - Host Register->FOG_QUICKREG_PENDING_MAC_FILTER, you can add the whole mac address or a part of the mac address. Using the “partial” address (usually the first 3 or 4 hex pairs) means it is going to filter anything that matches the partial part. This is comma separated. e.g. (00:01:0F,00:02:03:04,00:05:ab:af:ad:ac).

@dureal99d thanks for making this! Glad to see snapin packs are actually being of some help to people.

Is AD disabled on this host?

I’ll re-iterate my message. I’d wait until we fix v0.8.0

Bug confirmed and isolated. Ticket has been made here:

https://github.com/FOGProject/fog-client/issues/22

Basic explanation:
For some reason the samba LDAP domain is returning an error code of 1355 instead of 2 or 50 (which correspond to OU errors). On OU errors the client will try using a null OU. I just have to add 1355 to the cases of OU errors.

fog server’s ssl certificates -> fog server’s certificates

Thought so. Its a bug with some debug code I had…

v0.9.3 fixes this, however SVN is not yet updated to include this version. For now can you download it from here: https://github.com/FOGProject/fog-client/releases/tag/0.9.3 and see if it fixes your issue?

@DarkEnergy
Just a quick note, with the forums, if you put a space after the @, @NAME it won’t notify the person. So @ Jbob would not work, but @Jbob would

@plegrand

No release date is planned. For now keep using the legacy client. The next release of the client will be v0.10.0 which will include OSX + Linux compatibility.

@Raj-G the printer tool can be downloaded form here: https://github.com/FOGProject/fog-client/releases/tag/0.11.9

SVN has just been updated with v0.9.3

Ubuntu is … a hassal and is kind of expected to haver some hiccups. I’d recommend using Cent OS or Fedora. Or if you are more comfortable with Ubuntu, 12.04 LTS is great, its actually what one of my development servers run on.

@jrm , I am not sure what you are referring to. We have no official linux client released. What you found is probably a debian client made by one of our users. As to what @Wayne-Workman is referring to, we do have a linux and osx client in the works. However, it is not ready for release yet.

@wernercd it is worth noting, with the new client rebuilding it is no longer needed. And if for some reason you still need to, there’s automated build scripts available: https://github.com/fogproject/fog-client#building

@Asthea not that I am aware of. You could spawn a new thread that makes a local timetick event. Or you could make it as a Service, which would prevent any web portal freezing altogether.