The SP 2013 App model requires the use of Host Named Site Collection which in turn means the web application that will host the App domains must not have a host header. Line 1789 in AutoSPInstallerFunctions.ps1 forces the HostHeader option of New-SPWebApplication. I put an if block around it to check if the $webApp.name was equal to my portal name and if so call New-SPWebApplication without the -HostHeader option which worked for me.
As I am writing this, I'm thinking that another way to determined whether or not to call New-SPWebApplication with the -HostHeader option could have been to compare the $webApp.url to $xmlinput.Configuration.ServiceApps.AppManagementService.AppDomain -or- add a new configuration item under WebApplication named hostHeader that accepts either a true/false or an actual hostHeader that could be left blank.
Joe
Comments: Resolved with changeset 99077: AutoSPInstallerInput.xml:
- Updated version number to 3.85
- Changed default name of some databases for improved grouping and readability in SQL Server Management Studio
- New property UseHostHeader under WebApplication for toggling of host header creation in IIS
- useClaims is now "true" by default for better compatibility with SP2013
- New property HostNamedSiteCollection under SiteCollection enables creation of host-named site collections
- IndexLocation property renamed to CustomIndexLocation, and is now blank by default (to use the default value for SP2010 and SP2013 respectively). You can specify another path which will be created automatically, but make sure it's on a valid drive letter.
- Miscellaneous syntax updates
AutoSPInstallerFolderStructure.txt: Added the location of the \sxs source files for the offline installation of .Net Framework 3.5.1 on Windows Server 2012
AutoSPInstallerFunctions.ps1:
- Changed offline .Net Framework 3.5.1 installation on Windows 2012 to use DISM instead of Install-WindowsFeature for true offline experience
- ConfigureFarm function now includes section to stop the Default Web Site, in order to avoid conflicts with web apps that use port 80 and do not specify a host header
- AssignCert function now handles IIS sites with no host header specified
- CreateWebApp function supports web apps with no host header specified; also streamlined the web app and site collection creation scenarios
- For host-named site collections, add the host header to the local HOSTS file pointing to 127.0.0.1 if $xmlinput.Configuration.WebApplications.AddURLsToHOSTS is true
- Support for no-host-header in CreateUserProfileServiceApplication function
- We now grant Full Control for the general service app / app pool account to the User Profile Service to resolve a known issue with the Newsfeed in SP2013, and grant ShellAdmin rights to the MySite content DB for the Portal app pool account
- In StartClaimsToWindowsTokenService we now update the C2WTS to run under the general app pool account instead of default local system (avoids Health Analyzer issues)
- CreateEnterpriseSearchServiceApp function now better handles the search index location / root directory, and supports provisioning the admin component on multiple servers in SP2013
- Updated Get-FarmServers function to reflect some renamed elements
- Function AddToHOSTS now accepts a hostname as a parameter (to support host-named site collections)
-
As I am writing this, I'm thinking that another way to determined whether or not to call New-SPWebApplication with the -HostHeader option could have been to compare the $webApp.url to $xmlinput.Configuration.ServiceApps.AppManagementService.AppDomain -or- add a new configuration item under WebApplication named hostHeader that accepts either a true/false or an actual hostHeader that could be left blank.
Joe
Comments: Resolved with changeset 99077: AutoSPInstallerInput.xml:
- Updated version number to 3.85
- Changed default name of some databases for improved grouping and readability in SQL Server Management Studio
- New property UseHostHeader under WebApplication for toggling of host header creation in IIS
- useClaims is now "true" by default for better compatibility with SP2013
- New property HostNamedSiteCollection under SiteCollection enables creation of host-named site collections
- IndexLocation property renamed to CustomIndexLocation, and is now blank by default (to use the default value for SP2010 and SP2013 respectively). You can specify another path which will be created automatically, but make sure it's on a valid drive letter.
- Miscellaneous syntax updates
AutoSPInstallerFolderStructure.txt: Added the location of the \sxs source files for the offline installation of .Net Framework 3.5.1 on Windows Server 2012
AutoSPInstallerFunctions.ps1:
- Changed offline .Net Framework 3.5.1 installation on Windows 2012 to use DISM instead of Install-WindowsFeature for true offline experience
- ConfigureFarm function now includes section to stop the Default Web Site, in order to avoid conflicts with web apps that use port 80 and do not specify a host header
- AssignCert function now handles IIS sites with no host header specified
- CreateWebApp function supports web apps with no host header specified; also streamlined the web app and site collection creation scenarios
- For host-named site collections, add the host header to the local HOSTS file pointing to 127.0.0.1 if $xmlinput.Configuration.WebApplications.AddURLsToHOSTS is true
- Support for no-host-header in CreateUserProfileServiceApplication function
- We now grant Full Control for the general service app / app pool account to the User Profile Service to resolve a known issue with the Newsfeed in SP2013, and grant ShellAdmin rights to the MySite content DB for the Portal app pool account
- In StartClaimsToWindowsTokenService we now update the C2WTS to run under the general app pool account instead of default local system (avoids Health Analyzer issues)
- CreateEnterpriseSearchServiceApp function now better handles the search index location / root directory, and supports provisioning the admin component on multiple servers in SP2013
- Updated Get-FarmServers function to reflect some renamed elements
- Function AddToHOSTS now accepts a hostname as a parameter (to support host-named site collections)
-