Can you confirm that your Configuration.Install.SKU in the XML actually appears as <SKU>Foundation</SKU>?
Brian
Hey Joseph, OK so unless there's something wrong with the way AutoSPInstaller uses New-SPSite (missing/bad parameter etc.), this would seem to be more of a PowerShell / cmdlet issue than one that arises purely from using AutoSPInstaller... have you tried creating a site collection using pure PowerShell?
Brian
Actually I see what you mean now. As Foundation support is still experimental, I have only tested scenarios where the config xml file already exists and haven't implemented the functionality to automatically generate the config xml file as the script normally does with Enterprise or Standard. I will be fixing this in the near future.
Brian
This Element has a child Node, and shouldn't be closed off there.
<AdminComponent Provision="localhost">
<ApplicationPool Name="SharePoint Search Application Pool" />
</AdminComponent>
You are correct!
I apologize for the false alarm. I was migrating my v3.96 XML to v3.98 and, in haste, made an incorrect observation.
I'll activate the issue. Any idea how your registry got set this way in the first place?
Brian
I am trying to find out. These servers were new build provided by my client's Managed Service Provider.
I am not sure of the scale of the problem and I found these Registry Keys more by luck than anything else so this could also just be used to document the potential problem if anybody else runs into it.
Thanks for a fantastic script.
<Services>
<SandboxedCodeService Start="false" />
<!-- The UpdateAccount attribute will set the Claims To Windows Token Service (C2WTS) to run under an account other than the default Local System (the general spservice account), and thus avoid a Health Analyzer warning. However it might break things like PowerPivot and Excel Services so best bet is to leave it "false". -->
<ClaimsToWindowsTokenService Start="false" UpdateAccount="false" />
<SMTP Install="false" />
<OutgoingEmail Configure="true">
<SMTPServer></SMTPServer>
<EmailAddress></EmailAddress>
<ReplyToEmail></ReplyToEmail>
</OutgoingEmail>
<IncomingEmail Start="localhost" /> <!-- These had "true" values -->
<!-- DistributedCache (SharePoint 2013 only) - Start should never be set to "false", only either "true" for ALL servers (usually not recommended either), or a comma-delimited list of specific servers (maximum 4 cache host servers per farm). -->
<DistributedCache Start="localhost" /> <!-- These had "true" values -->
<!-- As a general rule WorkflowTimer - Start should never be set to "false", only either "true" for all servers, or a comma-delimited list of specific servers.
Normally you would specify the same servers to provision WorkflowTimer as you would FoundationWebApplication below. -->
<WorkflowTimer Start="localhost" /> <!-- These had "true" values -->
<!-- As a general rule FoundationWebApplication - Start should never be set to "false", only either "true" for all servers, or a comma-delimited list of specific WFE servers.
*Note* if you want to remotely install dedicated WFEs in your farm (i.e. RemoteInstall Enable="true") you should name the servers here, in a comma separated list - e.g. Start="WFE1,WFE2,WFEx" -->
<FoundationWebApplication Start="localhost" /> <!-- These had "true" values -->
</Services># ====================================================================================
Function AddResourcesLink([string]$title,[string]$url)
{
$centraladminapp = Get-SPWebApplication -IncludeCentralAdministration | ? {$_.IsAdministrationWebApplication}
$centraladminurl = $centraladminapp.Url
$centraladmin = (Get-SPSite $centraladminurl)
Try
{
$item = $centraladmin.RootWeb.Lists["Resources"].Items | Where { $_["URL"] -match ".*, $title" }
If ($item -eq $null )
{
$item = $centraladmin.RootWeb.Lists["Resources"].Items.Add();
}
$url = $centraladminurl + $url + ", $title";
$item["URL"] = $url;
$item.Update();
}
Catch
{
# Modified by vii 2015-02-13
Write-Host -ForegroundColor Yellow " Error in Function AddResourcesLink: param title: ($title), param url: ($url)"
}
} - Checking for stuck Search Host Controller Service (known issue)...
Error in Function AddResourcesLink: param title: (Search Service Application), param url: (searchadministration.aspx?appid=a08e8fd7-b8d5-469e-84e2-7a136b4a0b11)