@psyfer9983 There isn’t a tutorial on what you ask, because poking about in the windows registry using a non-windows OS is not typically a good choice. But with that said, I can give you the match and can of gas. What you do with them is up to you.
So once you have the bash script you need, you can call it during the post install actions after the image is placed on the target hard drive and before FOS exits and reboots. The first link shows you how to update/attach scripts to the postinstall script (which can be used for driver deployments).
@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.
@astrugatch all -S does is setup the vhost file so it will redirect to requests to https. The -c specifies which private key to use. If you need the installer to create keys for you, you can use the -K switch, and if you need a new CA you can use -C switch.
The installer already creates the keys for you by default, and the fog client looks for the servers CA key for validating the client is talking to the proper server.
If you want to use your own self signed cert, I might recommend using the servers CA so it works with that being the only difference you use.
As we do create the keys, if you’d like to use the fog generated key, the installer can just be ran with the -S argument. The only thing is recommend for that case is to import the ca cert so you dont have the self signed error. Machines with the fog client installed should see the green padlock as we do import the ca as I said earlier.
@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.
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’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.