We have made a special setting in deploy.image menu for the computers of the room. Then login and password are not requested to access to deploy menu.

#login params param mac0 ${net0/mac} param arch ${arch} param hostname ${hostname} goto host_${hostname} || goto autres :host_bug :host_win10-3 :host_i207m01 :host_i207m02 :host_i207m03 :host_i207m04 :host_i207m05 :host_i207m06 :host_i207m07 :host_i207m08 :host_i207m09 :host_i207m10 set username userlogin set password userpassword params param username userlogin param password userpassword param qihost 1 isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme goto fin :autres login params param username ${username} param password ${password} param qihost 1 isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme :fin

@p4cm4n You could probably use a snapin-pack to deliver the Chrome MSI as well as a powershell script. The powershell script could do a small loop with a maximum of say three iterations. Each time, it can try to install Chrome and then check if it’s installed. If the correct version is installed, exit the loop.

If the imagesize is empty, FOG only shows me the option to capture or deploy all image. If the imagesize is not empty, FOG shows me the options: all image or only one partition

@trialanderror I get where you’re coming from, but I agree with Tom that this for free software would be too much of a nightmare to do LTS support on. I mean, there isn’t even a support team. I’m glad they don’t spend a ton of time going back to old codebases and backporting it. The installer does a good job of not blowing stuff up and the db schema typically upgrades fine too.

I say “good” because it isn’t totally transparent about what’s going on, so you do actually have to be a bit familiar with the upgrade process to make sure that you don’t do anything that could lead to loss of data.

@wayne-workman and @george1421 this has been added for 1.6. I’m not going to try adding it to 1.5 as it is a bit of work to add the tests and the return information is at best rudimentary in 1.5.

I can work on adding a feature like this but it’s a lot of code and checks that have to go in on groups, and hosts. Perhaps, images would be better suited for ou/domain joining though i would prefer to see ou/domain management in its own format potentially as its own plugin. This, in my eyes, makes the most sense as OUs typically go with the domain being associated. The method used for the current ou system works by a single domain though you can keep in mind that hosts can be manually assigned domain/ou information. The “global” setting is just a quick way to set default information. It is by no means the only domain that can be used.

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