portal entry

What is the “it” you’re restarting, Eugene? You say “a server” but do you really mean the box? Or perhaps  CF or IIS? Sometimes people say one thing but really mean the other. Would help to know for sure.And either way, you say you need to do that reset of IIS settings, but you don’t clarify what happens if you don’t? Does your app not work? Some site? all sites? Some page?But I really can’t see a CF restart affecting iis this way at all, as you seem to be implying.  (And is it Adobe support you’re calling? If so, this could be their contention as well. Have they said that? Or might you mean Microsoft?)The only connection between CF and IIS of this sort that I can readily see (relating to CF somehow affecting IIS authentication) would be if you had run the new cf2018 auto lockdown tool. That does many things,  and though I’d not expect it to affect IIS auth, perhaps it does.Let us know about the above and perhaps we can get to resolution for you. 

Comment by Charlie Arehart

What is the "it" you mean you're restarting? You say "a server" but do you really mean the box? Or perhaps  CF or IIS? People often say server but mean otherwise. Just would help to know. And either way, you say you need to do that reset of iis settings, but you don't clarify what happens if you don't? Does your app not work? All apps? Some page? But I really can't see a Cf restart affecting iis this way at all, as you seem to be implying. (And is it Adobe support you're calling? If so, this could be their contention as well. Have they said that? Or might you mean Microsoft?) The only way I could see a connection between CF and IIS of this sort (relating to CF somehow affecting IIS authentication) is if you had perhaps run the cf2018 auto lockdown tool. That does many things,  and though I'd not expect it to affect IIS auth, perhaps it does. Here again, are you saying the settings is for all sites or some one? Getting clarification on these questions may help us find resolution for you.

Comment by Charlie Arehart

I'm also having an issue with CF2018 on IIS v10, I cannot find the wsconfig tool.  I am very new to setting up ColdFusion and even newer at dealing with IIS.  My entire program was coded in CF9 (using IIS), but when they stood-up my development server they used Windows Server 2016 with IIS v10 which you can't use with CF9, so I installed the development edition of CF2018 and now I can't find the wsconfig tool. I've only been programming for about a year and a half, I have a lot to learn, and I need lots of help getting this installed.    

Comment by srouse72

Before I answer srouse72's question, I'd like to ping Eugene on his original one. @Eugene, did you ever consider what I had written in reply to you, the day after you posted? Could you update us on the status of things? Especially now that others like srouse72 are replying to the question, seeking help for other issues? And @srouse72, I'll say first that what you bring up really has nothing to do at all (I don't think) with what Eugene was asking about. I suppose you just have been googling around seeking anything possibly related, and found this. I don't say that with malice, more a lament, for you and folks in your position. To be clear, you ought to have just created a new question here. You can do that, separately from replying to an existing one. :-) But while it's off-topic, since you've asked (and given that I've made the suggestion above for future such questions), I'll go ahead and answer. If you are indeed the one who installed CF, then on Windows you will find the web server config tool under Start>Adobe>ColdFusion>Web Server Configuration Tool. If you don't see it there, then some other user installed CF (or you were logged in as some other user when YOU installed it). In that case, you can also get to it from the file system, at coldfusion2018/cfusion/runtime/bin/wsconfig.exe. (You could also have found that by doing a search for wsconfig against the CF folder. You would have found it, and a cfconfig.jar in the runtime/lib folder, among perhaps others.) But then I'll also ask: why are you wanting to get to it? If it's because you added a new site in IIS and it doesn't work? If IIS was configured to have "all sites" go to CF, then from your CF9 experience you may reasonable expect that when you add a site, that site should "just work". but it doesn't--in CF10 and above. And you may find folks on the web saying that the solution is to create a new connector, with the wsconfig tool, to point that new site to CF. But that's not the ONLY solution. Assuming you did configure IIS to have "all sites" go to CF, then instead it's simply that each site also needs a jakarta virtual directory. You will see that your working sites have one, and if you declare the same one pointing to the same folder they do (likely coldfusion 2018/config/wsconfig/1), then your site may now "just work", and you don't need then to "create a new connector". Now, there may be arguments for creating a new one. That goes way beyond the scope of this Q & A. But now you can either run the tool if you want, or just try the shortcut. Finally, since you mention being new to all this and needing "lots of help" getting things working, I will say that while you can keep asking questions here in the portal (or the CF Forums), you can also turn to folks who can offer the sort of help you need. I do it, remotely, securely, and quickly. I also point to others who do it (including myself) at <a href="https://www.cf411.com/cftrouble" rel="nofollow">https://www.cf411.com/cftrouble</a>. Hope that's helpful. Let us know how it goes.

Comment by Charlie Arehart