When setting up the input XML to have the MySites hosted in a Host Named Site Collections scenario (so not in its own webapplication), the AutoSPInstaller script will fail to create the User Profile Service Application.
This is due to the function CreateUPSAsAdmin being called in which a scriptblock is written to a temp file which contains the command New-SPProfileServiceApplication (line 3228). This command correctly receives the managed path needed to be used for the MySites, but nowhere before this it actually checks if the managed path already exists. By default in a HNSC scenario there is no 'personal' wildcard inclusion managed path on the webapplication, thus it will fail here because it doesn't exist.
Would be nice to add a little check before this line to make sure the managed path exists and if not, create it. Of course in a HNSC scenario using the syntax: "New-SPManagedPath "personal" -HostHeader".
This is due to the function CreateUPSAsAdmin being called in which a scriptblock is written to a temp file which contains the command New-SPProfileServiceApplication (line 3228). This command correctly receives the managed path needed to be used for the MySites, but nowhere before this it actually checks if the managed path already exists. By default in a HNSC scenario there is no 'personal' wildcard inclusion managed path on the webapplication, thus it will fail here because it doesn't exist.
Would be nice to add a little check before this line to make sure the managed path exists and if not, create it. Of course in a HNSC scenario using the syntax: "New-SPManagedPath "personal" -HostHeader".