This content has been marked as final. Show 1 reply
With previous version, secure admin was enabled by default if you installed the enterprise profile while the developer profile would default to no secure admin. Things have changed quite a bit with 3.1, but the approach I use works regardless. What I usually do is just install with any default settings and once it is installed, the first thing I do is delete the default domain (domain1) and recreate it with the exact settings that I want. You can script pretty much everything you need with the asadmin command.