With my XML for AutoSPInstaller I create 6 Web Applications - 4 of these are created using the STS#0 template. Each has XML like this:
```
<WebApplication type="Other" name="Site Name" applicationPool="ConnectApplication Pool" url="https://SiteName.corp.company.com" port="443" UseHostHeader="true" AddURLToLocalIntranetZone="true" GrantCurrentUserFullControl="false" useClaims="true" useBasicAuthentication="false" useOnlineWebPartCatalog="false">
<Database>
<Name>Content_SiteName</Name>
<DBServer />
<DBAlias Create="false" DBInstance="SERVER\INSTANCE" DBPort="" />
</Database>
<ManagedPaths />
<SiteCollections>
<SiteCollection siteUrl="https://SiteName.corp.Company.com" HostNamedSiteCollection="false" Owner="Company\james" Name="SiteName" Description="Site Name" SearchUrl="https://portal.corp.company.com/search" CustomTemplate="false" Template="STS#0" LCID="1033" Locale="en-us" Time24="false" />
</SiteCollections>
</WebApplication>
```
I'll also Clarify and say that all 4 other sites are categorized as WebApplication type "Other" - not sure if that has any bearing.
Under Site Settings > People and Groups - None of the site Have the usual SharePoint security groups created for them.
* _SiteName_ Owners
* _SiteName_ Members
* _SiteName_ Visitors
Instead There is only one security group listed - __Excel Services Viewers__ - Why it picked this I have no idea
After AutoSPInstaller is done If I create a Site Collection manually using STS#0 (Team Site) It does get the security groups. Also, if I delete the site collection and recreate it, it gets the expected groups.
I can supply the complete XML config file if it helps.
Comments: ** Comment from web user: brianlala **
```
<WebApplication type="Other" name="Site Name" applicationPool="ConnectApplication Pool" url="https://SiteName.corp.company.com" port="443" UseHostHeader="true" AddURLToLocalIntranetZone="true" GrantCurrentUserFullControl="false" useClaims="true" useBasicAuthentication="false" useOnlineWebPartCatalog="false">
<Database>
<Name>Content_SiteName</Name>
<DBServer />
<DBAlias Create="false" DBInstance="SERVER\INSTANCE" DBPort="" />
</Database>
<ManagedPaths />
<SiteCollections>
<SiteCollection siteUrl="https://SiteName.corp.Company.com" HostNamedSiteCollection="false" Owner="Company\james" Name="SiteName" Description="Site Name" SearchUrl="https://portal.corp.company.com/search" CustomTemplate="false" Template="STS#0" LCID="1033" Locale="en-us" Time24="false" />
</SiteCollections>
</WebApplication>
```
I'll also Clarify and say that all 4 other sites are categorized as WebApplication type "Other" - not sure if that has any bearing.
Under Site Settings > People and Groups - None of the site Have the usual SharePoint security groups created for them.
* _SiteName_ Owners
* _SiteName_ Members
* _SiteName_ Visitors
Instead There is only one security group listed - __Excel Services Viewers__ - Why it picked this I have no idea
After AutoSPInstaller is done If I create a Site Collection manually using STS#0 (Team Site) It does get the security groups. Also, if I delete the site collection and recreate it, it gets the expected groups.
I can supply the complete XML config file if it helps.
Comments: ** Comment from web user: brianlala **
After finally reviewing this in detail I'm pretty certain it's not an issue with AutoSPInstaller. After all, as you identified, we merely call native a SharePoint cmdlet (New-SPSite) and specify the template. I would try running this same cmdlet yourself after the farm is built, obviously substituting the variables with your own values, and see if groups get created or not.
BTW @templateSwitch gets parsed by PowerShell as "-Template <SPWebTemplatePipeBind>", but if no template has been specified, the -Template parameter is omitted. Standard stuff.
Brian
