>automation?
I spent some time with Chef back in the days of 10.5 (and maybe 10.6). Unfortunately, I was not able to get it to work (Web Adaptor Installer Quits If Site Already Exists · Issue #116 · Esri/arcgis-cookbook · GitHub ; also, if IIS has more than 1 default binding (e.g. port 80 is bound to HTTP, port 443 is HTTPS, and port 443 is also bound explicitly to "abc.example.net" with a different SSL certificate), then the installer fails).
My firm once paid an ESRI tech advisor to walk us through installing 10.7 and it involved a lot of manual workarounds. As an example, my documents include the following steps:
After AGS finishes making a new site, change the service's log-on user to datacenter\esri_admin. Then, give that account full control over the c:\program files\ArcGIS,c:\arcgisserver, and c:\python27 folders.
...many steps later...
Remove the auto-created arcgis account from Windows.
Similarly, for Web Adaptor, we found that after WA is installed and the browser window pops up:
If the browser's address bar says localhost, change it to the machine's fully qualified domain name (e.g. stoutweb1.datacenter.local).
>ever supported
That's true. My company has never used Portal before. We were hoping to keep the amount of extra Portal-induced work to a minimum. Having to tell people that we can't clone VMs any more seems a bit severe.
