InstallAware

am setting up everthing correctly in the installer, but when I install on another machine (with IIS of course) the virtual folder is installed but the pool is not. I have to manually go in to IIS, get the properties on the new virtual folder, then manually click the "Create Application" button. Again, I am setting up the pool specifications on my end correctly, they just get lost along the way.

I found an earlier post on apparently this same topic that never had any resolution:

---
MichaelNesmith
I believe choosing Medium in the Application Protection section will create a new application pool for that virtual folder. Is this not the case?

andrejzr
Unfortunately this is not the case. When I install the WEB site on Windows 2003 server, the Application Pool is still set to the DefaultAppPool.
---

I am using XP Pro with IIS5.1 and Installaware 6.5, so maybe the above problem is something else, but it sure sounds the same.

I recall this worked correctly in an older version of Installaware. Please let me know what I am doing wrong! This is driving me nuts.

I am really not sure what the problem here is. The post of mine you are referring to is for an older version of InstallAware, which could not create custom application pools. The current version of InstallAware should not have problems with this.

Is anybody else running into this issue?