The SiteAudit OnSite runs on 64-bit Windows platforms and virtual machines. Supported operating systems are listed in the chart below. Physical hardware performs better than virtual machines. It is imperative to meet or exceed the minimum requirements for physical hardware when using a virtual machine.
Microsoft framework .NET 4.8 is required and can be downloaded on the same page as the OnSite installation media or can be downloaded from Microsoft at https://dotnet.microsoft.com/en-us/download/dotnet-framework/net48
The following platform requirements are guidelines and considered to be the minimum that should be used based on the number of printers being monitored. These requirements are sufficient for most environments. But depending on usage, it may be necessary to increase the amount of RAM. To run the reporting web site (RWS) IIS v10 or later is required.
|
Guideline: Number of printers to monitor
|
Windows Operating System
|
Machine Running SiteAudit DCA
|
MS SQL Instance
|
|
10000 - 25000
|
2016,
2019, 2022
|
64 GB
RAM
|
SQL
Server 2016/2017/2019/2022
|
|
|
|
i7 8th
Gen quad core or better
|
SQL
Server should run on a separate server
|
|
|
|
10 GB
Free hard disk space
|
|
|
25000 - 50000
|
2016,
2019, 2022
|
128 GB
RAM
|
SQL
Server 2016/2017/2019/2022
|
|
|
|
i7 8th
Gen quad core or better
|
SQL
Server should run on a separate server
|
|
|
|
|
|
Data Storage
The amount of data stored for a device depends on its make and model. Environments with diverse fleets of printers—ranging from single-function black and white printers to multifunction devices with multiple consumables—can vary widely in stored data, typically between ~0.5MB/mo. to 5MB/mo. For instance, single-function printers may report only a total count and have a single toner, while multifunction devices can support numerous sophisticated counters and print sizes (e.g., A4 scan, A3 scan, A4 b/w scan, A4 color scan, A4 duplex b/w scan, scan to email, scan to network, scan to OneDrive, etc.). Additionally, these printers often support various protocols and security-related features, influencing overall data storage needs.
It is crucial to ensure adequate space for data growth, particularly during upgrades where SQL log files may expand significantly. We recommend configuring the SQL recovery model to Simple recovery and periodically shrinking log files to effectively manage their size.
Disk Size & Network Traffic
Both disk usage and network traffic generated by SiteAudit are low and manageable. This solution has been successfully implemented across diverse global environments. While it's important to acknowledge potential data growth and network traffic considerations, these factors typically pose minimal issues.
Please note that this information is provided as a guideline for making deployment decisions. It is based on historical and observational data from typical environments with varied printer types (such as single-function, multifunction, label, networked, and local printers), multiple counters, address spacing, IP addresses, and other relevant factors. Actual results may vary accordingly.
