This project is read-only.

STS0 Template Not Creating Membership Groups with AutoSPInstaller

Jan 6, 2014 at 10:11 PM
Edited Jan 6, 2014 at 10:24 PM
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="Comapny\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>
Under Site Settings > People and Groups - None of the site Have the 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.
Jan 7, 2014 at 7:07 PM
Hey,

You will have to post this issue on the AutoSPInstaller codeplex page and not here.

It looks like for some reason SPWeb.CreateDefaultAssociatedGroups is not being run in the code.
You can run this manually to create the default groups.
http://msdn.microsoft.com/en-us/library/microsoft.sharepoint.spweb.createdefaultassociatedgroups.aspx

Thanks,
Ivan
Marked as answer by IvanJosipovic on 1/7/2014 at 11:07 AM