Creating a WebApp via PowerShell is mapping the site to wrong AppPool

Question

I have a weird issue with creating WebApps using the below script. Seemingly when I create my WebApp everything is working and looking fine. I can look in IIS and see that it is correctly configured, I can see in SP Config that the AppPool is correctly configured. BUT when I stop that pool the site is still loading and working fine. Stopping another specific AppPool (probably first created pool) will stop the site.

If I create the TestSite via the CA then it behaves properly and the site stops when stopping the assigned AppPool so it must be something with the script that differs from how the CA does things.

Can someone point me to where this could be wrong?

New-SPWebApplication -Name "Testsite" -ApplicationPool "TestAppPool" -ApplicationPoolAccount (Get-SPManagedAccount "SPDOM\setupadmin") -DatabaseServer "sp2010" -DatabaseName "TestDB" -HostHeader "testsite" -Url "http://testsite.spdom.loc" -Port 80 -AuthenticationMethod "Kerberos"

Answer 1

I finally found the culprit, the first web app had * bindings. Removing them fixed everything.

Start IIS, select the Sites node to discover the site with the wildcard binding and remove it.

Answer 2

If the application pool already exists, just specifying the application pool will suffice. It will use the application pool account that is already in place for that application pool.

New-SPWebApplication -Name "Testsite" -ApplicationPool "TestAppPool" -DatabaseServer "sp2010" -DatabaseName "TestDB" -HostHeader "testsite" -Url "http://testsite.spdom.loc" -Port 80 -AuthenticationMethod "Kerberos"