I shadowed a vendor install ProClarity Application Server the other day
and he tweaked SQL Server and IIS in a couple ways. The guy couldn't
give specific reasons. They are just best practices apparently and so
are on his checklist. Can anybody shed light on these three items:

1. Turned ON Remote Connections on SQL Server Surface Area utility.
What is remote here? Remote to the server or remote to the network?
2. In IIS extentions: Are their security risks to allowing "All Unknown
ISAPI"?
3. In IIS extentions: Why does Proclarity need WebDAV?

I think the answers to these questions have a lot to with SQL Server &
IIS as well as ProClarity. But if this is the wrong forum, I apologize.
Please direct me.

Thanks,
David

1. Remote = remote from the server, not the network. (if you have only local
access, like the client tool installed on the same computer, turn it off)
2. yes, its why this feature is disabled by default, try to avoid turning it
on. Instead, select each ISAPI you want to allow to be executed by your self
to keep the control on which program runs under you IIS.
3. I don't know :-) I presume that Proclarity use the webdav protocol to
manage his document library. (moving, renaming, locking etc...)


<davidb1835 (AT) gmail (DOT) com> wrote

Thank you! I will deal with the ISAPI settings. I guess my vendor
allows 'All ISAPI' for installation but doesn't follow behind and lock
the server back down.

-David


Jeje wrote: