Agent deployment via waptdeploy and dnsdomain
Published: March 16, 2018 - 1:03 PM
Hello,
We rely on SRV records to find the addresses of the main WAPT server and repositories.
When creating the agent deployment package, we can fill in the "Address of main WAPT repository" and "Address of WAPT server" fields.
Since we are using SRV records, I left these two fields blank to use "dynamic" detection via querying SRV records in DNS.
The agent deploys correctly, but then we get the error message attached.
This is logical since the dnsdomain parameter is empty in the wapt-get.ini file.
Could you please tell me how to configure this field during deployment via waptdeploy.exe?
Or am I doing something wrong?
Thank you.
Best regards,
Thomas
We rely on SRV records to find the addresses of the main WAPT server and repositories.
When creating the agent deployment package, we can fill in the "Address of main WAPT repository" and "Address of WAPT server" fields.
Since we are using SRV records, I left these two fields blank to use "dynamic" detection via querying SRV records in DNS.
The agent deploys correctly, but then we get the error message attached.
This is logical since the dnsdomain parameter is empty in the wapt-get.ini file.
Could you please tell me how to configure this field during deployment via waptdeploy.exe?
Or am I doing something wrong?
Thank you.
Best regards,
Thomas