As I have come to notice alot of times there are too many chefs in the administration kitchen. Often there are requests that are filled but never documented. In such cases it is always best to check an environment out before you start to make changes of your own. In one particular instance manipulating FTP sites in IIS 6.0 can be particularly problematic. Ever since IIS 6 was released a new feature called isolated FTP came as a welcome feature but in typical Microsoft fashion is lacked some basic user functionalities. How can you identify a isolated FTP site? or change an established isolated FTP site to a regular site?
You might think why go through all of this trouble when it would be easier to delete and recreate? In some cases this is not always appropriate. After all this is someone else’s server and often just deleting things causes more problems that fixes.
Problem: identify or change an IIS 6 isolated FTP site
Fix: First open IIS manger and navigate to your FTP sites folder. Note the identifier of the FTP site in question. The identifier is usually some random but unique 9 digit number. Next, open your IIS metabase explorer. If you don’t already have the IIS metabase explorer you can find it here. Navigate to <server name> -> LM -> MSFTPSVC -> <identifier number>. At this point the panel on the right should be showing to much information, the vital information will have to be reveled. On the menu bar select ‘view’ and enaable both ‘Inherited Data’ and ‘Secure Data’. The right hand panel should now show much more information. The particular value of intrest to us is:
The Data will determine the type of FTP site it is:
You can of course change these values but do so with care.