1

Closed

Central Admin Not Installed When Using FQDN

description

I've been running my multiserver installation script setting the Provision= attributes to NetBios server names with only a few issues. While attempting to solve one of my issues I decided to change all the Provision= attributes to FQDN's and Central Admin is not getting provisioned.

Joe
Closed May 10, 2013 at 1:17 PM by brianlala

comments

jspadea wrote May 7, 2013 at 2:03 PM

I pulled down the latest version of the script (4/22/2013) and it solved the central admin problem. However, I noticed that in AutoSPInstallerFunctions.ps1 there are 11 locations that are still using:

$_.Name -eq $env:computername

instead of:

MatchComputerName $_.Name $env:COMPUTERNAME

Without replacing those 11 instances the search components won't get installed.

Joe

wrote May 10, 2013 at 1:17 PM

Resolved with changeset 100404: Changes in this release:

AutoSPInstallerFunctions.ps1:
  • InstallCumulativeUpdates function now parses opatchinstall*.log for result code to determine if the patch application worked, was not needed, etc.
  • InstallCumulativeUpdates also no longer requires the SP2013 March 2013 PU patch to be present in \Updates (e.g. in case it was already applied or slipstreamed)
  • Added try & catch to the section of CreateEnterpriseSearchServiceApp that issues a request to searchfarmdashboard.aspx so script doesn't blow up if it fails or times out
  • Consistently used the MatchComputerName function throughout script to better support FQDNs