Initial setup of bandwidth usage reports
To use bandwidth usage reporting, you need to set up 3 components:
All these components can be installed on a single server (on ISA Server computer), or can be distributed among 2 or 3 different servers. For example, you can use local MSDE or SQL Server database installed on ISA Server computer, or you can use remote dedicated SQL Server. Bandwidth Splitter reporting service and IIS web application also can be installed on ISA Server computer, or on SQL Server computer, or on any other server in your network.
|Warning. If you have ISA Server array with multiple servers, you must not use local MSDE or SQL Server for bandwidth usage stats. Use a dedicated SQL Server in this case.|
Supported SQL Server versions are: 2000, 2005, 2008, including Express editions.
Using the local MSDE or SQL Server database on ISA Server computer will naturally slightly increase server load, especially during report generation periods. It is recommended that you use dedicated SQL Server if you have more than 250 users. If you decide to use local database, it is reasonable to schedule report generation for night hours to avoid server overloading.
Bandwidth Splitter reporting service with management web application requires Internet Information Services (IIS) and .NET Framework 2.0. The .NET Framework 2.0 is usually installed via Windows Updates.
It is usually not recommended to install IIS on ISA Server computer (because of security reasons). So generally you should install this component on another server. If nevertheless you decide to use IIS on ISA Server computer (too small network to afford another server), make sure you secure it enough, and configure ISA rules to allow access to it only from internal network.
At this moment you should already decide whether you want to use MSDE or SQL Server, and where you are going to install Bandwidth Splitter reporting service with management web application. See the next sections for details on how to set up these individual components.