@szeraax That is a very good idea, but we have a five digit asset tag number that needs to be part of the name.

@george1421 I’m not sure I understand about deleting the hosts, so I would delete them sometime before imaging was completed?

These systems have a feature called Host Based Mac Address so that they can have a unique address, however it requires OS support. So in FOG that would mean Kernel support I believe. I can turn on Host Based Mac Address and get a unique MAC when booted into Windows. Of course since I don’t have support in FOG it registers the dongle address, then during first boot and before rename and domain join it now has a different MAC address. This is causing the computer to (re)register itself with a generic name.

Anyway. Anybody know if Host Based Mac Address support is planned?

I also read something about imaging via System UUID, this might be promising, anyone know how that might work?

@netbootdisk You can create a universal image within the firmware style. The disk and hardware interface is different between uefi and bios. The disk format is less of an issue. We use MDT and two VMs (one bios and one uefi) to create a consistent golden image for each firmware style. That way each golden image is consistently the same.

We use http://www.sivann.gr/software/itdb/ with a few minor UI/language mods. Works a treat!

We’d used Spiceworks in the past, but it’s dynamic/scanning nature tended to mess things up. This sometimes added great confusion as to what the actual truth was.

With a completely manual database, at least we know any changes would’ve been done by a human and not some script editing our records. FOG’s inventory is still good for cross-checking the asset db records though!

@dloudon96 If it has worked before I doubt this thread is helping to fix things for you. Please open a new topic (there is no restriction) and post all your details - error message (picture of screen), steps you tried, things that changed before it stopped working, …

Doing these checks for “All hosts” is a relatively large hit on performance which is why I don’t show them. We do this for text only elements with the only exception being module status. Snapins an Printers work similarly to powermanagement in that you don’t see which snapins or printers all hosts have associated.

@sebastian-roth Fixed.

Darn forgot to add a link
https://www.raspberrypi.org/blog/pi-3-booting-part-ii-ethernet-all-the-awesome/

@tom-elliott yes, you are right it loads the _32 version. I tried to load many of the kernels i could from kernel updates, with no luck. The kernels and image seems to load fine, and the menu is ok. But after when it realy tries to work, running the commands for registration, or deploying (partimage), it crashes because lack of memory.

New script using smartctl. Grabs firmware now as well.

#!/bin/bash hd=$(lsblk -dpno KNAME -I 3,8,9,179,202,253,259 | uniq | sort -V | head -1) #FOG expects the string in the following format ##Model=ST31500341AS, FwRev=CC1H, SerialNo=9VS34TD2 disk_info=$(smartctl -i $hd) model=$(echo "${disk_info}" | sed -n 's/.*\(Model Number\|Device Model\):[ \t]*\(.*\)/\2/p') sn=$(echo "${disk_info}" | sed -n 's/.*Serial Number:[ \t]*\(.*\)/\1/p') firmware=$(echo "${disk_info}" | sed -n 's/.*Firmware Version:[ \t]*\(.*\)/\1/p') hdinfo="Model=${model}, iFwRev=${firmware}, SerialNo=${sn}" echo $hdinfo

This works for NVMe and SATA. Note that SATA drives use a ‘Device Model’ where as NVMe drives use ‘Model Number’. This could lead to issues if other drives report it differently.

@mrayzies Good to hear. If you look at my very first post you can see a ref link to the current versions of the post install scripts. You might get some ideas on how to update yours.

@george1421 said in Location Plugin - enhancement of behavior:

Issues that will need to be addressed is location cidr addresses eclipsing other addresses.

Exactly, I thought about this too. And when there is overlap, as Joe said, we just pick the best match. If there’s a tie, just pick the first one in the tie.

Bumping this, it’s a good idea still.

@wayne-workman Thank you. Yes, I will get to this sometime today or tomorrow

@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)