@JulienF I will still work to add a potential for “securing” the aspects that can be secured.

As far as your NFS route, you only have a single subnet to worry about. You could create a secondary “subnet” for FOG imaging if you needed, or just restrict NFS to use that single Subnet (making it no longer publicly (globally) accessible).

@Junkhacker i will inspect the postdownload script section usage (well, documentation search in some topics is hard for fog system, for me at least). but atm we have a lot more disturbing problem, mystery that keeps me away from sleeping. topic is “missing image” 🙂

@x23piracy unfortunately a standard Active Directory contains usually just: hostname, and sid, along with a few other details such as OS version. FOG 2.0 doesn’t rely on MAC addresses as a primary identifier anymore, but still requires some additional information that’s not stored in AD to perform proper host matching. So long story short; no we will not support AD importing for the foreseeable future due to some technical limitations.

Ninja feature.

Default capture method is now in the “FOG Configuration Page->FOG Settings->General Settings category.”

@george1421 i actually don’t think this is as massive of a rewrite/change as you imagine. Tom put a lot of flexibility in the code. I honestly think this could probably all be done with a plugin.

i mean, it’s beyond MY skill level. but someone could do it.

@ITCC this would definitely be a feature request. Power Management takes the approach of “If the user is away, they get logged off, and the machine is shut off”. You may be better off to use either GPO or snapins to achieve this. For example, schedule a CRON snapin that just checks if any users are logged on, otherwise it shutsdown.

@ablohowiak said in Database Maintenance:

What tables would be useful to locate old hosts?

hosts and hostMAC

I can help with the SQL if you have questions. Whatever you come up with, we can probably add it to our existing list of maintenance commands with a little description for each one:
https://wiki.fogproject.org/wiki/index.php?title=Troubleshoot_MySQL

@Wayne-Workman

yes, just to display hosts that have printers & what printers they have assigned to them

I’m not looking for a ‘live’ report of what printers they do have connected

@Tom-Elliott said in change color of icon "upload":

if you don’t want user’s to accidentally overwrite an image, why not just set the image to “protected” and/or change the files so they’re immutable?

This is the proper answer. 1.3.0+ allows you to protect the image from accidental deletion and accidental rewrite.

In 1.3.0+ the terminology is much more clear. In 1.2.0 and below, it was “upload” & “download”. Myself, all of my co-workers, my cousin, and many people on the forums all found this very confusing. So for 1.3.0 and higher, it was changed to “Capture” & “Deploy” and now we see a whole lot less confusion about it.

@jc35 I would recommend you upgrade your FOG Server in the near future to take advantage of these features plus the many others that 1.3.0+ has to offer. You might want to look at this article if you don’t want to disturb the old server and want to start fresh: https://wiki.fogproject.org/wiki/index.php?title=Migrate_FOG

Alright, I’ll look into that.

Thanks, guys!

@Tom-Elliott
@george1421

Thank you for your answers.

I will give it a try next time I need some new challenge!

one thing that i’ve taken to doing is putting keywords in the description of the image. when i want to see a group of related images, i search for the keyword that relates them

Thank you Tom! I understand! I will figure sth. out to work for my setup.

@sourceminer Hello, I never tested using a channel but using a private message works fine with test token.
You can also create your bot : https://my.slack.com/services/new/bot

0_1485790486968_Sans titre.jpg

Here is my conf :
0_1485790863612_Sans titre3.jpg
0_1485790596846_Sans titre2.jpg

@alv000h Excellent work.

@Tom-Elliott said in Add support for FSCK before Image Creation / Image Management(web UI):

Should they like to see the feature for “everybody” post the script and description of what it’s doing and why you feel it’s useful.

This is what fog-community-scripts is for.

I like to solve them so I know which Feature Request’s have been completed. No this does not mean it needs a question flag.

I like it.

I like this idea.

Last checkin date (if any)
and three statuses: No Client, Attempting Checkin, and Client working.

The statuses would come from if the client authenticates successfully or not. An attempt would at least let you know it’s trying.

This stuff can be two extra columns in the hosts database. last checkin date and fog client status. Those two extra things can be displayed in “List all hosts” and sorted.

@Tom-Elliott I’m not pressing hard saying we need this, I’m just saying it would be pretty nice.