UAG powershell deployment & server name

[LarryBlanco2]

Is anyone out there deploying the UAG server via PS and the acocmpaning INI?   aside from the VM name is anyone using the "uagName" option and naming their UAG server something specific?   Even thought I give it a specific name such as "UAG1.DOMAIN.COM" it ignores that setting and it just assigns a random name to it such as "uag-f97ccc1c-269c-4b5b-9a89-59e1b134d0df"

In the INI I have:

name=UAG1

uagName=uag1.domain.com

It takes "name" and that is what pops up in vcenter but the dns name for itself is the randon uuid.   The reason I ask is beacause it is what shows up in the view admin as the conenction server.  Since our enviroment is load balanced, it would be nice to know how evenly the connections are being distributed.

Thanks,

LB

[BenFB]

I've been deploying using powershell and the ini file since the 2.x Access Point days. On prior versions of the UAG it would just set the hostname to "localhost"

I did some digging and found the "uagName" option in an example on the official UAG documentation site.

Using PowerShell to Deploy the Unified Access Gateway Appliance

It's not in the Communities documentation on deploying the UAG which is linked to in the above.

Using PowerShell to Deploy VMware Unified Access Gateway

[LarryBlanco2]

Yeah...  Maybe I'll just open a case and see what they say.   it's ignoring whatever I put in there..  Or maybe the PS script is not taking that option.   It might just be the PS script itself and not communicating that INI entry to the uag server upon configuration.

LB

[BenFB]

I tested this afternoon with 3.3.1 and confirmed the same result. VMware Tools is reporting "photon-machine".

[LarryBlanco2 · Accepted solution]

As per VMWare:

--

Hello Larry,

Thanks for sharing the details with the screen shots.

We have seen the similar behaviour when we try to deploy UAG with PS using INI file.

Would recommend to use UAG UI to change the host name to reflect as per the needs. This behaviour is seen when we use INI file with PS deployment.
The behaviour is same when we try any version. PS is unable to grab the UAG hostname parameter to update the hostname on the deployed VM.

We are taking this forward with the engineering team to fix the behaviour seen. Until they fix this in upcoming releases, please use the UAG UI to update the right hostname.
--

So manually editing the name is the only way to do it now up until it is addressed by engineering.

Larry

[BenFB]

Thank you for following up. I'm hesitant to ever make changes to a UAG after it's deployed so I'm just leaving it alone for now until they fix it.