I do not believe that is possible but am extremely curious what your use-case is for wanting to script this process. This process only happens once after the installation has happened. Furthermore, AMI instances of Tableau Server cannot be upgraded so after purchase (restriction of the license process), so there would be no need to do any upgrades to be presented with the prompt again.
I agree with Nathan, what's the reason behind this?
what is AMI?
I concur thoroughly
Amazon Machine Image
Outside of this administrator account creation step, we have automated all other tasks to spin up a new Tableau server and publish our users/groups/projects/datasources/workbooks/etc.
If we want to stand up a new Tableau server some reason (e.g., change the AMI to increase our license limit, add a new development environment, etc.), we yearn to make that process as simple as possible.
Is it a big deal to add this account manually? No.
Because it's the only thing keeping us from executing a single command to automatically create a new server, publish our objects, etc., it was worth looking into.
Thank you for the speedy response!!
The only way I have seen this done is to create a backup after adding the admin account. You can then do a restore no-config as a last step to get the admin user added from the backup
Excellent - thank you.
This will work perfectly.
Correct me if I'm wrong (I haven't tried it) but could you use tabcmd initialuser ?
I tried that, however, I get the error below. Any clues?
(I am running the tabcmd as the administrator on the box.)
 DEBUG 2016-06-22 14:32:12,672: =====================================================================
 DEBUG 2016-06-22 14:32:12,672: ====>> Starting Tabcmd 9.2 at Wed Jun 22 14:32:12 UTC 2016 <<====
 DEBUG 2016-06-22 14:32:12,672: Build 9200.15.1211.2326
 DEBUG 2016-06-22 14:32:12,672: System.out encoding: Cp1252
 DEBUG 2016-06-22 14:32:12,672: Console codepage: 437 (OEM - United States)
 DEBUG 2016-06-22 14:32:12,672: Codepage identifier code: 437
 DEBUG 2016-06-22 14:32:12,672: Default locale: en_US
 DEBUG 2016-06-22 14:32:12,672: Display language: English
 DEBUG 2016-06-22 14:32:12,704: run as: tabcmd initialuser --username Administrator --password ******** --friendly Tableau Admin
 DEBUG 2016-06-22 14:32:12,782: No session file found: C:\Users\Administrator\AppData\Local\Tableau\Tabcmd\tabcmd-session.xml
 ERROR 2016-06-22 14:32:12,782: Uncaught exception NullPointerException: null
 ERROR 2016-06-22 14:32:12,782: See the logs for the stacktrace.
 DEBUG 2016-06-22 14:32:12,782: Top level exception caught:
Huh...good call-out Gerardo and nice test Andrew. I'm guessing the test failed because of this note in "How to Use tabcmd" - "When you use tabcmd, you must establish an authenticated server session" but exactly how you authenticate to an uninitialized server seems to be the issue. I am now really curious as to what the use-case is for using this Tabcmd option...
I've reached out to the rest of the Technical Support Team internally to find out if someone has that info - I hope I can satisfy our curiosity!