Quantcast
Channel: AutoSPInstaller
Viewing all articles
Browse latest Browse all 2279

Commented Issue: STS#0 Template Not Creating Membership Groups with AutoSPInstaller [20605]

$
0
0
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: webguynj **

BTW, at a core level, I have solved this, but not sure how to address inside of ASPI.

SharePoint does not by default create SharePoint groups for a site. You need to do this explicitly.

```
$site = New-SPSite -Url $siteURL -OwnerAlias $ownerAlias -SecondaryOwner $env:USERDOMAIN\$env:USERNAME -ContentDatabase $siteDatabase -Description $siteCollectionName -Name $siteCollectionName -Language $LCID @templateSwitch @hostHeaderWebAppSwitch -ErrorAction Stop

#Add this code
$primaryUser = $site.RootWeb.EnsureUser($ownerAlias)
$secondaryUser = $site.RootWeb.EnsureUser($env:USERDOMAIN\$env:USERNAME)
$title = $site.RootWeb.title
$site.RootWeb.CreateDefaultAssociatedGroups($primaryUser, $secondaryUser, $title)
#End Add this Code
```
This should ensure that the Owners, Members and Visitors groups are created no matter what template is used to create the site collections


Viewing all articles
Browse latest Browse all 2279

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>