Hi paulbeck
I've customized the autospinstaller 'cause I had the same problem.
What I did:
Addition to the AutoSPInstallerInput.xml:
Inside the <EnterpriseSearchServiceApplication> changed the following part:
Another thing I've changed was, that I had to add the search service account to the local administrator group during the search configuration and removed it later on. This is something I also customized in the AutoSPInstaller and the everything work really fine.
Thanx to everybody who already did great jobs an the existing scripts!
I've customized the autospinstaller 'cause I had the same problem.
What I did:
Addition to the AutoSPInstallerInput.xml:
Inside the <EnterpriseSearchServiceApplication> changed the following part:
<IndexComponent>
<Server Name="localhost" IndexPartition="0" />
</IndexComponent>
then I made an addition/change to the AutoSPInstallerFunctions.ps1 inside the "If (!($IndexingComponents) ....)" statement: Add the following lines:
$indexComponent = ($appConfig.IndexComponent.Server | where {MatchComputerName $_.Name $env:COMPUTERNAME})
$indexPartition = $IndexComponent.IndexPartition
Changed the following line:
New-SPEnterpriseSearchIndexComponent –SearchTopology $clone -SearchServiceInstance $searchSvc -IndexPartition $indexPartition @rootDirectorySwitch | Out-Null
I've tested it with two Search Servers each running a separat indexPartition and it worked fine.Another thing I've changed was, that I had to add the search service account to the local administrator group during the search configuration and removed it later on. This is something I also customized in the AutoSPInstaller and the everything work really fine.
Thanx to everybody who already did great jobs an the existing scripts!