@Wayne-Workman unfortunately we will not add this. The ssl directory where your private keys are stored, and should never be accessible via the web GUI. That presents a massive security risk as a single bug in the web GUI could provide anyone with access to your private certs; arguably the most sensitive data on the server.

As the saying goes, security and convience are usually at opposite ends of the spectrum; and this is one thing we will not compromise on.

Exporting your keys as root using ssh is the preferred, and only way, we will support.

@ripau It is an interesting idea but I do think it would be a lot of effort to impliment. I think this sort of thing would be great as a plugin in FOG. Plugins can create & use extra tables and hook into all of the FOG Server’s existing functionalities but using the new code that comes with the plugins.

You could probably change the assigned printers dynamically based on who the FOG Client says is signed in. The plugin would have to take who’s signed in and make an LDAP query to the AD server to see what groups that user is in, then figure out somehow what printers that user gets.

One problem though - the fog client is not so hot at removing printers. I and many other people have had a lot of problems with it. In a best-case scenario, a computer gets imaged and when it boots up, the fog client installs printers that never need uninstalled. Eventually, the next imaging in the future wipes all that out and then installs the correct printers, rinse, repeat.

@x23piracy Installer switch --oldcopy and/or .fogsettings parameter copybackold=…

@sebastian-roth true we could do that and have gained a field back for other use like asset tags that @Wayne-Workman mentioned but mostly because it stops information from being stored wrongly. (I know… how hard could it be to put site/room into one field.) I’ll have another think about merging them.

FOG Groups are much more advanced than Active Directory groups IMO. They allow for more flexibility - but that extra flexibility they allow requires the Admin to be organized and intensely aware of the details involved when using groups. (really, just an understanding of relational databases)

@Jim-Graczyk All pages rely on “index.php”. The Default if node is not in the query string, or if node=home will direct to the dashboard. This is intentional as most people this shouldn’t impact too much. That said, this shouldn’t be a hard request to incorporate, but if you’re blocking the dashboard as being view-able, where should we redirect if a choice hasn’t been made?

@jjcjr Ok just for clarity you are following the instructions from my first post? If so yes you need LOCAL in there or in your my.cnf file you need to set the … <something> path to empty.

I wasn’t aware of postinit scripts :(. Looking at postinit now, it seems that it would need network mount to work through default router (the firewall) and we tried to minimize what we are enabling through the firewall. XenServer PXE boot (testing host) doesn’t support classless static routes either so we had to let TFTP through to make this work.

Maybe we could reconfigure our “single fog server - multiple subnets/vlans” setup? We have tried to create multiple network adapters on the same FOG server and to have clients from each network to communicate with the server through IP address in the same subnet but we were not able to set up this to work and I’m not sure if FOG supports this as I have seen that FOG requires network interface to be specified in some places.

@moses said in Per-group timezone settings via FOG client:

It would be nice if we could set the client’s time zone on a per-group or even per-client basis.

You don’t have a server on your network that’s working as ntp source on each of your sites?

In working branch, I’ve now included a History Report. It’s likely not perfect, but at least the information is presented to the GUI now. It allows for CSV and PDF exporting as well.

@dpotesta50 Look back at Sebastian’s post. It contains links to information on how to do this.

@x23piracy I don’t think it’s worth the trouble or dev cycles.

@jj-fullmer said in USB ethernet adapter mac(s) for imaging multiple hosts. (Universal Imaging Nics) (Wired Nic for All Wireless Devices):

current host or get a host by a given uuid, mac, or hostname.

You should fork the fog-community-scripts repository and add this stuff to it. Just label it the powershell cli or something, give it some snazzy name.

For the Python project, I’m calling it fog-cli.

I had to ask a question about the plugin and i also crosspost the link here because it was the original thread related to plugin question:

https://forums.fogproject.org/topic/10877/windows-keys-plugin-and-hosts-product-key-field-coexistence-who-wins

@joe-schmitt I like this idea very much.

@taspharel it was good that you started that discussion and it sounds like that we maybe can expect that feature in the future. Thank you.

@george1421 webif should be a known short for web interface 😄

@wayne-workman Good to know.

The people who would be looking at this wouldn’t have that sort of access, so I guess I’m feature requesting that it be made available in the GUI. 🙂

https://www.microsoft.com/en-us/Useterms/OEM/Windows/10/UseTerms_OEM_Windows_10_English.htm

In case anybody’s overly concerned. Here’s the OEM EULA. Notice, it states that you are allowed to transfer the license to another user so long as it’s with the device and the software is installed and the product key is given with it. There are no rules on what you can/cannot document. That’s like saying you can’t pull the serial number from the bios.

Just trying to get people to calm down. We know the device and software are owned by the person. We know how to obtain the information. We don’t know how the user intends to use it after it’s been stored, but that’s out of our hands. We cannot control what the admins/users do with the key once it’s know, but that’s out of our control to begin with. There’s plenty of ways for users to get that information to begin with, I don’t see anywhere in the EULA where it states we cannot store a copy of it for ourselves.

@sebastian-roth

0_1505338885213_FOG bandwidth.JPG