Note - If you do not fill in every section below, your post won’t be answered - you must provide the steps you have followed so far and the actions you’ve already taken. Make sure to remove this notice from your post too.
Screenshots of text are prohibited. Always copy and paste text as text.
Make sure you search before posting! Duplicate posts for the same issue may not be answered.
OS Name/Version: Windows Server 2025
Product Name/Version: 2.6.3.2 - 20251022.1
Problem Description:
When creating a new instance from the controller, instances do not follow defaults set in the deployment defaults. Settings such as Core.Login.AuthServerURL or Core.Security.EnablePassthruAuth do not seem to take effect, and will be provisioned with their standard defaults of 127.0.0.1 and false respectively. However if the instances is deployed either from the target directly or from the target by managing the target from the controller, the defaults I set do take effect.
Steps to reproduce:
- Set deployment defaults on both target and controller
- Deploy an instance to the target from the controller
- Deploy an instance to the target from the target
- Check the config file to verify the controller-deployed instance does not get the specified defaults and the target-deployed instance does get them.
Actions taken to resolve so far: Verified that settings name/tags were correct by deploying instance from the target with the expected behavior. Editing the above values was the solution to another issue of being unable to manage instances from the controller.