
I've mentioned before that I found a script for adding Squidguard blocklists as ISA URL- and Domain-Sets. I thought it was about time that I put it up for others.
The required command will be:
where:Code:cscript dest2004.vbs <policy element> <file_name> <element type>
* <policy element> - name of Domain name Set or URL Set
* <file_name> - name of file to add
* <element type> - dom for Domain name Set and anithing else fro URL Sec
Squidguard lists can be picked up from all over the show (I believe that the strandard ones are at http://www.squidguard.org/blacklist ). Due to the size of these lists, it can take a while to import them and it can also have an effect on the performance of ISA if you add too many.
I have also attached some pre-made policy elements than can be imported into ISA 2004. This is a quicker way to get you up and running. Most of the sites are from the Squidguard lists with a few of my own added in![]()
Nice list![]()

Just updated the policy elements... realised I'd missed the bloody Lineflyer/Linerider URLS!
There's also some social networking stuff in there![]()
That's pretty poor. When do you start having performance problems?Due to the size of these lists, it can take a while to import them and it can also have an effect on the performance of ISA if you add too many.

The import takes a long time if you import ALL the categories (46MB of plain text spread across 134 files).
The performance issue is slightly more complicated... there's not a massive performance hit once ISA is running but after adding several thousand entries into multiple entities, restarting ISA and applying changes to ISA will take noticeably longer. I don't know why - it's just a documented fact!
Here are some more banned domain and url list that i have built up over time. Some of the address might be that same as the above post

Should really get around to writing a script to merge these XML files... oh the power!
Also the lists at www.urlblacklist.com are worth subscribing to.


Restarts will take ages because ISA foolishly rebuilds the "searchable" copy of the list at the drop of a hat.
Our product takes a while to restart if you have to do a "hard" restart, but we added a "soft restart" a while ago for most common operations.
ISA should NOT get any slower in general performance unless you run out of RAM. Basically the check will be a binary search which does not increase in linear complexity, so even 10 million sites means only a handful of string compares (which are the "hard" bits).
HTH,
Tom
Presumably to the point where it's unstartable as Windows thinks it's taking too long and it's dead/broken?Restarts will take ages because ISA foolishly rebuilds the "searchable" copy of the list at the drop of a hat.
Has anyone tested dest2004.vbs with ISA 2006?
There are currently 1 users browsing this thread. (0 members and 1 guests)