Re: Feature Pack 1 RELEASED!
- From: "Deus, Attonbitus" <Thor@xxxxxxxxxxxxxxx>
- To: "[ISAserver.org Discussion List]" <isalist@xxxxxxxxxxxxx>
- Date: Wed, 08 Jan 2003 14:17:54 -0800
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
At 01:42 PM 1/7/2003, you wrote:
>http://www.ISAserver.org
>
>
>Hi Tim,
>
>Use the one that fits your needs. Works the same as URLScan when its
>installed on the Web server itself, except that settings on the ISA
>Server apply to *all* published servers. This might be a bit of
>challenge if you're publishing OWA, FP, and whatever other types of
>servers you want to publish, all requiring different URLScan.ini
>configs.
>
>The first thing I need to do is see if there are any differences between
>the OWA settings for the ISA URLScan.ini and what we use when we install
>it on the Web server. The next test is to determine whether we can the
>settings for the various server roles into a single URLScan.ini file
>(OWA, FP, Microsoft Project, SharePoint, etc) and use that. However, I
>suspect if you have a wide array of server roles that you need to
>support, you're best off configuring URLScan on each Web server.
>
>Would like to hear conflicting opinions, though :-)
I get it now... Yes, it is just like the URLScan you load on a regular
server in that only one config is active at a time- From seeing the
multiple .ini files, I thought that ISA was possibly using different
configurations simultaneously based on the type of Web Publishing done- as
if it knew what rules were created from the OWA Web Publisher and would use
the urlscan_owa.ini for those sites, while using the urlscan_iis.ini for
regular Web Publishing sites (at the same time.)
I see know that the urlscan_owa.ini and urlscan_iis.ini files are just for
reference and backup- during install, if you tell it to use the standard
URLScan for IIS, it will copy the urlscan_iis.ini over to urlscan.ini. If
you tell it to go ahead and use the OWA-based filter, it will copy the
urlscan_owa.ini file to urlscan.ini. So, it is only using urlscan.ini for
its filtering options.
Tim
-----BEGIN PGP SIGNATURE-----
Version: PGP 7.1
iQA/AwUBPhyjkohsmyD15h5gEQIwHQCeI2+XXOqiFxoOgp3KRS2okf5K8nsAoJN2
7bZhvlnvcTbz/WicFBtmt9sp
=7rvG
-----END PGP SIGNATURE-----
Other related posts:
