well my experience is as a hosting provider, and as such I have installed CF on dozens and dozens of servers over the years and deal with it on a daily basis, so I can say with 100% certainty that using wsconfig is absolutely not required to enable CF on new sites. Hosting control panels for example do not use WSCONFIG, they simply add the handlers to IIS for the new site.
On Thu, Sep 6, 2012 at 9:00 PM, Carl Von Stetten <[email protected]>wrote: > > Russ, > > My experience with Windows 7/Windows Server 2008 R2 and ColdFusion 9 > Standard Edition has been that when a new site is added in IIS, **none** > of the ColdFusion connectivity works without some intervention (and I'm > not just talking about the CFIDE vdir). The only thing that has > consistently made IIS and CF "play nice" has been to re-run WSCONFIG. > Typically I will run WSCONFIG and remove the "All Sites" connection, > restart IIS, then re-run WSCONFIG to re-add "All Sites". I have > occasionally just added the individual new sites as well. > > The point is, for me, that running WSCONFIG has been absolutely > necessary to get new IIS web sites "wired up" properly. Your experience > may be different. > > -Carl > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:352436 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
