WAPT 1.5 deployed via GPO
Published: March 26, 2018 - 10:04 PM
Good evening,
I've noticed an issue on two sites I manage with WAPT. For example, in one site with the server name https://wapt-srv.lmaccassin.loc,
when manually running waptdeploy, it doesn't point to that address but to https://wapt.
To work around this, I had to create a host named wapt (IP address 10.171.40.31) in my Windows Server 2012 R2 DNS, with an alias srv-wapt pointing to the host.
My question is: is the address hard-coded in waptdeploy? Because doing this allowed me to unlock the waptagent installation via GPO... Is it possible to have a feature that allows me to regenerate waptdeploy with the correct server parameters?
I've noticed an issue on two sites I manage with WAPT. For example, in one site with the server name https://wapt-srv.lmaccassin.loc,
when manually running waptdeploy, it doesn't point to that address but to https://wapt.
To work around this, I had to create a host named wapt (IP address 10.171.40.31) in my Windows Server 2012 R2 DNS, with an alias srv-wapt pointing to the host.
My question is: is the address hard-coded in waptdeploy? Because doing this allowed me to unlock the waptagent installation via GPO... Is it possible to have a feature that allows me to regenerate waptdeploy with the correct server parameters?