For my three server installation (2 X WFE and 1 App), where I ran AutoSPInstaller scripts against the WFE1, then the App Svr and then WFE2 - the default URL was linked to the loopback IP address in WFE1, which was correct. However, after WFE2 and the App Svr were completely installed and tried to launch Central Admin - the system pointed to the correct server but then errored out.
When I checked the server's Hosts file for WFE2 and the App Svr, they both had the same entry as the first server...
SPS10WFE1 127.0.0.1
To get it to work properly, I had to delete this line in WFE2 and App Svr to launch Central Admin from them.
Though I had selected "true" to include the URL in the Intranet zone, there were no other entries for the AAM's.
Comments: Resolved with changeset 109137: Changes in this release:
- In InstallUpdates function, updated SP2013 SP1 filename to reflect re-released kb2880552; also display March 2013 PU warning only if SP1 isn't detected
- CreateWebApp function will only try to create site collections if nodes are found within
- ConfigureTracing now adds all managed accounts into the Performance Log Users group
- Enhanced AddToHOSTS function to better deal with localhost etc.
When I checked the server's Hosts file for WFE2 and the App Svr, they both had the same entry as the first server...
SPS10WFE1 127.0.0.1
To get it to work properly, I had to delete this line in WFE2 and App Svr to launch Central Admin from them.
Though I had selected "true" to include the URL in the Intranet zone, there were no other entries for the AAM's.
Comments: Resolved with changeset 109137: Changes in this release:
- In InstallUpdates function, updated SP2013 SP1 filename to reflect re-released kb2880552; also display March 2013 PU warning only if SP1 isn't detected
- CreateWebApp function will only try to create site collections if nodes are found within
- ConfigureTracing now adds all managed accounts into the Performance Log Users group
- Enhanced AddToHOSTS function to better deal with localhost etc.