Before you install File Reporter, review the following table to understand how different technologies might affect how you proceed.
|
Technology |
Notes |
|---|---|
|
Windows and Networking |
The Engine runs on a Windows operating system and uses basic TCP/IP networking inherent to the operating system. |
|
Microsoft Internet Information Server (IIS) |
File Reporter is accessed and managed via a web browser. The Web Application is an ASP.NET application that runs in conjunction with IIS. The installer and configuration utilities automatically configure IIS and manage most aspects of the installation for you. The Engine and Web Application must run on the same system in this release of the software. |
|
DNS |
In order to access the File Reporter Web Application with a browser, the web site name as registered with IIS must be used. In other words, the raw IP address does not work. You need to create a DNS entry for the name in the environment, or the entry needs to be added to the hosts file on every machine accessing the File Reporter system. |
|
Database |
File Reporter utilizes a Microsoft SQL Server or PostgreSQL database as the back end data store. The database must be accessible from the server running the Engine. |
|
Active Directory and Windows Server |
For reporting on Active Directory and Windows file systems, File Reporter makes use of a proxy object and group in Active Directory that is used by the system as part of day-to-day operations. You should be familiar with the Windows network that you will be reporting against with File Reporter as well as with basic Windows file system and Active Directory terminology and operations. |
|
Messaging Broker |
To enable messaging between File Reporter components that are needed for file content scanning (ManagerFC and AgentFC) or Microsoft 365 scanning (Agent365), File Reporter utilizes the RabbitMQ message broker. |