HI , We have to embed the client config files and the masthead in the client msi package, and then we can use that package for installtion, for this request i have found the link below but it can only embed the the masthead not the config file, please help me in adding the config file as well in the msi package, please share the command or the links?
Do we have any other command by which we can use the BES Client MSI Editing Tool to add the config file.
I also recommend having a policy action deployed in the actionsite that will set all of the desired default settings for all clients that are missing any of the desired values that can be applied to all clients regardless of how that client got installed.
I realize this doesn’t solve the problem of configuring a custom relay, or tagging, but it does solve issues where clients for some reason don’t pick up the CFG default settings like they should or are deployed in such a way that makes that difficult.
The idea is that you would modify this item to have whatever you think the maximum / minimum values should be for all clients, conservatively, and then deploy it targeting all computers as a MO in the action site, and clients will process it very early on and get the desired settings and speed up provisioning and just ensure that all clients come through with these settings configured.
The action is designed such that if the client is already configured through some other means, like a CFG file or others, then those already configured settings will not be touched. It is only if settings are completely missing that they will be added.
Also the idea is that this should only run a single time, not repeatedly, such that you could change settings later and those changes would not be touched either.
HI James,
This is really helpful to manage the client settings in the longer term.
Currently my issue is that we are configuring the agents in a region where the endpoints only have connectivity with the relays of that region and if we not use the CFG file then these agents will not report and also we have so many such regions where we have to perform this.
I have also gone through the Brad linkedin solution to use ORca tool to embed all the settings inside the MSI, but in that option also we cannot add both the relay server settings. In my region I have to have settings for both the relay servers and then also the failover server but here i am not able to add secondary relay servers settings for a MSI.
And also if we use the BESClientSetupMSI.exe then also we cannot add the secondary relay entries.
Do we have any option some how that we can embed all the settings Relay 1 Relay 2 and other settings directly inside the MSI and then we can use that MSI. If we have such option then it will also help us in prestaging the MSI package for MCM too.
If you follow Brad’s LinkedIn post listed above, it has instructions for adding any client setting to the MSI package. The example is for _BESClient_RelaySelect_FailoverRelay, but you can repeat this and add any client setting to the MSI package