Closed Feature: Managed Pathes are only handled when webapplication is created [18908]

Hi there Firstly, I would like to thank you for such a tremendous tool for coping up with the details of a proper SharePoint installation and configuration.Thank you really much.A small issue occurred when we did a few cycles of running the installer because of an error we got during creation of some site collections (our bad). It came to us that managed pathes are only added to the SP when the WebApps freshly created. In our case we forgot to add a managed path in the first run, got an error, changed the xml to contain the managed path, re-run the script and got ther error once more.From a little examination of the AutoSPInstallerFunctions.ps1 file we got insight:The SetupManagedPaths function, where all the removing and adding of those pathes is made, is just called when a WebApp is created (in function CreateWebApp, line 1805). In case the WebApplication is in place already, the script just jumps into the else clause and writes this ("WebApp already provisioned") to console.Wouldn't it be better if the call to SetupManagedPaths would be place after the If Else checking the existence of the WebApp? Perhaps placing the call in the line before the If($useSSL)...Thanks for your attention.sincerily yoursJan Peter Steinweg
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)
-