```
<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: webguynj **
I've been digging a bit deeper into this - The only line in the script that creates the Site Collections is #2619 In the installer Functions ps1. the exact line is:
$site = New-SPSite -Url $siteURL -OwnerAlias $ownerAlias -SecondaryOwner $env:USERDOMAIN\$env:USERNAME -ContentDatabase $siteDatabase -Description $siteCollectionName -Name $siteCollectionName -Language $LCID @templateSwitch @hostHeaderWebAppSwitch -ErrorAction Stop
* @TemplateSwitch is define earlier as: $templateSwitch = @{Template = $template} or as @{}
* New-SPSite shows the Parameter for Template as -Template <SPWebTemplatePipeBind>
Maybe there's something I don't understand about PowerShell parameters, but how does this work.
Also in any case - Why would New-SPSite with correct parameters be failing to create the site Groups?
Is there a way to turn on more -verbose logging in AutoSPIntaller?