TPMfOSD called them “Software Modules”. MDT called them “Packages”. This is for configuration steps or software installations that might be installed on the target machine immediately following a Bare Metal or Reimage task. How do we get similar functionality out of BigFix OSD?
In particular, many of our clients require a custom configuration in the clientsettings.cfg when installing the BigFix client. Depending upon their network location we have to manually specify initial Relays to contact (which we currently detect by probing with ‘wget.exe’ against a known relay list). Depending upon the organization managing the client we also pre-populate some custom client settings in the clientsettings.cfg during the BES client installation.
Is there a way to manage something like this with BigFix OSD? I see in the Profile that we can specify a version of BES Client to install, but I don’t see a way to handle additional configuration settings in a generic way.
From a reimage perspective you should be able to keep all of your client settings in transition. So you should never have to manipulate these settings.
From a bare metal perspective, do you just want to codify the client settings or are you looking to deliver packages??
My immediate problem is deploying a set of BES Client Settings. The post from @vtripodi looks like it will help with that. In a more generic sense I would like to be able to deploy software configurations / packages; being a capability present in both MDT and TPMfOSD, I’m suprised BES OSD doesn’t appear to include it.
I know we could have Policy Actions set up to deploy given changes through the BES client, but I would still like the flexibility of doing it through OSD instead.
If you can package your settings so that you can add them to the MDT task Sequence in the MDT bundle and use the modified Bundle to carry out the operations.