UAG 3.2 deployment via Powershell from exported ini is not fully implemented. Semi working.

[jrodsguitar]

This is not a question about how to deploy a UAG via Powershell. That part is easy.

Scenario: Export the ini then use the ini to deploy UAG via powershell Try it. It does not work as expected. Obviously one must modify certain items such as IP address, source, etc, but the deployed UAG does not apply a few key items such as requestTimeoutMsec and bodyReceiveTimeoutMsec, ceipEnabled and several others.

Also the certificate thumbprint is in the incorrect format in the exported ini. This caused the entire [Horizon] section to not populate after deployment. See the "=" that should be a colon ":".

proxyDestinationUrlThumbprints=sha1=yy:yy:yy:yy:yy

The UAG is not production ready after deploying via powershell. It is a broken mess.

When does VMWare plan to implement this fully?

[BenFB]

Until they give us a way to set requestTimeoutMsec, bodyReceiveTimeoutMsec and ceipEnabled through the powershell deployment I wouldn't expect that to work. There are still a lot of settings that can only be configured post deployment unfortunately. The only settings that can be specified are documented in Using PowerShell to Deploy VMware Unified Access Gateway.

VMware is due to release a UAG update this quarter. I hear this might be a big release which is why I suspect markbenson​ hasn't been very active on here lately. I have a few bug reports and feature requests for the UAG that I'd like to know what the right way to report them is.