The current method of installation using the .msifiles requires manual intervention at the server console to complete the setup.
Please allow the choice of installation type & password parameters to be supplied as options to the .msi package so that remote deployment and/or easy installation on server core is possible.
example: msiexec.exe /i wayknow.msi /pwType=custom /pw=MyPa$$ /installtype=all /reboot=no
We don't have this yet, but we have an in-between that may be sufficient for your needs. You can write a powershell script that installs the .msi and then calls "WaykNow.exe" from its installation directory to set configuration options from the command-line. There is a special "WaykNow.exe config" command that can be used to edit the Wayk Now configuration file (.json) without having to deal with the files directly. It is also much easier to invoke WaykNow.exe from a script. Here is the syntax (inspired from "git config")
Usage: WaykNow config [options] propertyName [propertyValue]
propertyName: Property name
propertyValue: Property value. If a value is specified, the property will be set to that value (SET). If no value is specified, the current value will be printed (GET). Can't be used with --unset
--global Use global config file rather than user config file.
--type <TYPE> Property value type : int, bool or str are supported.
--unset Remove the property name from the config file.
--help Print help.
For instance, if you want to configure a custom password, here is what it looks like:
WaykNow.exe config PersonalPasswordType 1
WaykNow.exe config PersonalPassword 123456
The properties map directly to the json properties inside the WaykNow.cfg configuration files, so just open the file to learn options can be modified.
The user-specific configuration file is located in %AppData%\Wayk\WaykNow.cfg, and the global configuration file is located in %ProgramData%\Wayk\WaykNow.cfg. WaykNow.exe is installed in C:\Program Files\Devolutions\Wayk Now\WaykNow.exe by default.
Is this enough to cover your use case?
Is it possible to edit a global .cfg file and push it into the installation folder immediately after the install to have it take effect on the reboot?
Also, as we've discovered, unless the reboot is immediate there may be problems with the TLS services, so could this file be pushed into place first and would the install keep it, or overwrite it?
Yes, you can edit the global configuration file immediately after installation, using the "WaykNow config --global" command. To edit the global configuration file, you need to run the command with elevated permissions, as it modifies a file in %ProgramData%.
The unattended mode introduces the first global configuration file, and it only uses a limited set of options. If you edit settings from Wayk Now, you should now see a lock to unlock editing global options (it will prompt for UAC). The options available after unlocking are those currently used by the unattended service.
Otherwise, just look at the different options available in %ProgramData%\Wayk\WaykNow.cfg and %AppData%\Wayk\WaykNow.cfg. The options that affect the unattended mode are mostly the server options, since the server is now inside the service and not in the main program.
The idea behind adding WaykNow config (with or without --global) was to simplify modifying configuration files without having to deal with the files directly, making it much simpler for automated installation. If the file does not exist, it should normally create the required directories and the configuration file. If the file already exists, it will load the previous file to edit it without overwriting what is already there.
We will keep improving the command-line configurability of Wayk Now in future versions.