Tom Elliott

The FOG Team is proud to announce the immediate availability of the nineth release candidate for FOG 1.3.0. This release candidate addresses issues that were raised by users from their use of the eighth release candidate. A changlog is available for this

The FOG Team is proud to announce the immediate availability of the eigth release candidate for FOG 1.3.0. This release candidate addresses issues that were raised by users from their use of the seventh release candidate. A changelog is available for this

The FOG Team is proud to announce the immediate availability of the seventh release candidate for FOG 1.3.0 in addition to v0.11.5 of the FOG client. This release candidate addresses issues that were raised by users from their use of

The FOG Team is proud to announce the immediate availability of the sixth release candidate for FOG 1.3.0. This release candidate addresses issues that were raised by users from their use of the fifth release candidate. A changelog is available for this

The FOG Team is proud to announce the immediate availability of the fifth release candidate for FOG 1.3.0. This release candidate addresses issues that were raised by users from their use of the fourth release candidate. A changelog is available for this

The FOG Team is proud to announce the immediate availability of the fourth release candidate for FOG 1.3.0. This release candidate addresses issues that were raised by users from their use of the third release candidate. A changelog is available for this

The FOG Team is proud to announce the immediate availability of the third release candidate for FOG 1.3.0. This release candidate addresses issues that were raised by users from their use of the second release candidate. A changelog is available for this

The FOG Team is proud to announce the immediate availability of the second release candidate for FOG 1.3.0. This release candidate addresses issues that were raised by users from their use of the first release candidate. A changelog is available for this

The FOG Team is proud to announce the immediate availability of the first release candidate for FOG 1.3.0. Overall, there have been many updates since 1.2.0's release back in July of 2014. This release candidate addresses many issues from 1.

Hello all, I know it was not too long ago that I created an article relating to control of the replication information. All of that data remains, but I wanted to give some new update to the current replication information as well. I have

Hello all, I know it was not too long ago that I created an article relating to control of the replication information. All of that data remains, but I wanted to give some new update to the current replication information as well. I have

Hello all. All of you whom have been working with the current development builds of FOG probably are aware of the Image and Snapin replication features. We initiated these so that you can replicate your images between nodes, but improved it so it can

Hello all. All of you whom have been working with the current development builds of FOG probably are aware of the Image and Snapin replication features. We initiated these so that you can replicate your images between nodes, but improved it so it can

I have added code to the FOG Source in an attempt to limit the deletes and writes to the database. I'm writing a news post for the purpose of making sure people are made aware of this change. In the past, changes to an

I have added code to the FOG Source in an attempt to limit the deletes and writes to the database. I'm writing a news post for the purpose of making sure people are made aware of this change. In the past, changes to an

Hello all, While I'm sure, and hoping, many are not running trunk and the new client together. There was a problem with a function call, and this should now be fixed. It also fixed a potential mac address problem causing pretty much the same

Hello all, While I'm sure, and hoping, many are not running trunk and the new client together. There was a problem with a function call, and this should now be fixed. It also fixed a potential mac address problem causing pretty much the same

Everybody, FOG has been hosted more or less by out of our own pockets. We do appreciate all the donations to assist in keeping our project alive and well. With that said, donations aren't always as fruitful which is totally understandable. For this reason,

Everybody, FOG has been hosted more or less by out of our own pockets. We do appreciate all the donations to assist in keeping our project alive and well. With that said, donations aren't always as fruitful which is totally understandable. For this reason,

All, I realize the last few init's for our imaging system has been......broken. I know most probably did not realize this. I can tell you the "broken" images came around Revision 3345. I thought it was fixed in 3396, but I

All, I realize the last few init's for our imaging system has been......broken. I know most probably did not realize this. I can tell you the "broken" images came around Revision 3345. I thought it was fixed in 3396, but I

New Things are coming I know it's been a while since this page was last updated. I'm sorry for that, and I speak for the whole of the FOG Team. We really are just regular people with regular lives. A lot of free time

New Things are coming I know it's been a while since this page was last updated. I'm sorry for that, and I speak for the whole of the FOG Team. We really are just regular people with regular lives. A lot of free time

The FOG Project team is proud to release the latest of FOG as version 1.2.0. With this release comes many new features including the ability and support for Linux and multiboot resizable imaging. Thanks in particular to Curtis Larsen of the FOG

The FOG Project team is proud to release the latest of FOG as version 1.2.0. With this release comes many new features including the ability and support for Linux and multiboot resizable imaging. Thanks in particular to Curtis Larsen of the FOG