The Windows Client must be configured/customized post installation through the config.properties file. For options where it makes sense, it would be beneficial to configure the Windows Client at time of installation through the use of command line arguments passed to the MSI. This simplifies the packaging of the Windows Client (through SCCM for example) and reduces the need to maintain n amount of config.properties files.
Example: naaf-winclient-x64-release-<version>.msi /quiet DISCOVERY_HOST=aaf.test.local DISABLE_LOCAL_ACCOUNTS=true TENANT_NAME=top VERIFY_SERVER_CERTIFICATE=false EVENT_NAME=windowsPoC
by: Tim S. | over a year ago | Configuration
Comments
Tim, we are doing what we can to reduce the reliance on the config file. It is our target to place configuration information in the console. Not everything can be moved (logically)
The question I have about your suggestion is that if I read it correctly you would like command line arguments to replace the config file settings. This is a rather permanent solution for items that could change. If we simply consume the settings from an install then that implies that a new install would be required to change any settings. Is this what you are requesting or am I missing some piece?
Troy
Totally understood that not everything can be done in the console. The command arguments shouldn't set anything to be permanent but would be another way to define config properties (maybe as part of the install process, the command line arguments are parsed and written to theconfig.properties file).
Any settings defined as part of a command line argument could be changed later in the actual config file.
I have used SCCM and ZenWorks workstation configuration management. I believe it would be more difficult for an administrator to do two steps (command line and write to the config file) than it would be to simply drop a file in a location post install. It seems to me this would be causing additional work.
Am I missing some consideration?
The way I would invision the process working is that the installer itself handles the parsing and writing of the command line arguments to the config file.
Then after the installer is done with parsing and adding a manual turn is needed to complete the information (as is stated above)...?
This just seems like additional work for all.
I think I am still missing some key reason that this adds value.
Please help me understand.
Tim, can you please comment on the above?
Troy, I see where you are coming from in your replies. In my opinion, if no one besides me is asking for this/really a pain point, then it is likely not worth the effort.