Preparing a Host for WISdom Data Collection Installation
Before installing the WISdom data collection services, ensure the host machine is properly configured. This includes meeting OS and application prerequisites, enabling secure connectivity to the Fortified WISdom API, and allowing access to all monitored SQL instances.
📄 Download the full WISdom Installation Requirements (PDF).
System Requirements
Operating System
- The host OS must be equal to or newer than the OS of any monitored servers.
- ⚠️ Microsoft does not support WMI or performance metric collection from a lower-version OS.
Required Software
- Windows Management Framework (WMF) 5.1
- Included in most modern Windows Server and Desktop editions.
- .NET Desktop Runtime 8.0.x
- 📥 Download .NET Desktop Runtime
- Look in the right-hand column, second block down --> Find “.NET Desktop Runtime”.
- 📥 Download .NET Desktop Runtime
Network & Firewall Configuration
To ensure uninterrupted data collection and communication with the Fortified WISdom cloud, configure the following:
Inbound Access to Managed Servers
| Service | Port(s) |
|---|---|
| SQL Server (default) | 1433 |
| SQL Browser (If named instances are used) | 1434 |
| WMI | 135, 49154† |
| Performance Counters | 445 |
† If port 49154 is unavailable, open the dynamic range: 49152–65535
Outbound Access to WISdom Cloud
- Allow HTTPS traffic to:
https://collectorapi.fortifiedwisdom.com
The Azure API above consists of two IP ranges in different regions for redundancy.
| Region | IP Range |
|---|---|
| US East 2 | 20.85.14.224/29 |
| US Central | 20.236.234.64/29 |
Antivirus Exclusions
To prevent performance degradation, exclude the following directories from antivirus scans:
%Installation Folder%\CollectorResults%Installation Folder%\UploadReady%Installation Folder%\ESUploadReady
Default Installation Path:
C:\Program Files\Fortified\Wisdom\
Collection Host Server Sizing Guidelines
To ensure optimal performance of the WISdom service, server sizing should be based on the number of data collection endpoints. Depending on your network architecture (e.g., geographic region, domain, or subnet), you may need to deploy multiple virtual machines (VMs) for distributed data processing.
Use the following guidelines to size your virtual machine (VM) for optimal performance of the WISdom service:
| Managed Servers | CPU Cores | RAM | Storage |
|---|---|---|---|
| 1–50 | 4 | 8–16 GB | 50 GB |
| 51–200 | 8 | 16 GB | 75 GB |
Managing more than 200 servers on a single VM may lead to performance or data collection issues. Consider scaling horizontally by adding additional VMs.
💡 Scalability Tip:
For better fault tolerance and load distribution, you can deploy two smaller VMs instead of one large instance. This approach can enhance resilience and simplify maintenance.
WISdom Collection Service – Account Requirements
To ensure proper operation of the WISdom Collection Service, the hosting machine must use a service account that meets one of the following criteria:
1. Windows-Based Service Account
- The account must be a Windows user account, preferably a domain account or a Global Mananged Service Account (gMSA) for centralized management and scalability.
- It is strongly recommended to use this service account for all data collection activities.
➤ See Collection Account Requirements for more details.
2. Log on as a Service
- The account must be granted the “Log on as a service” right to allow the WISdom service to run as a Windows service.
3. Local Administrator Rights
- The account must have local administrator privileges on the server where the WISdom service is installed.
- These permissions are essential for:
- Accessing necessary system resources
- Ensuring reliable data collection
- Supporting service stability and performance