- Print
- DarkLight
- PDF
WISdom Prerequisites
Download the WISdom Installation Requirements document here
The WISdom services require a machine with the following components and port access to support the data collection:
- Windows Management Framework (WMF) 5.1
- .NET Core 8
- Access to all the servers managed by WISdom on the following ports:
- SQL Server Port (1433, or other defined SQL Ports)
- SQL Browser if named instances are used – Port 1434
- WMI Ports
- 135
- 49154 - In most cases this RDP port is available and will be used
- Cases where 49154 is not available, a port range may be required/recommended
- 49152-65535
- Cases where 49154 is not available, a port range may be required/recommended
- Performance counters – Port 445
- Outbound firewall rules must allow access to AWS S3 over HTTPS.
Monitoring Service Account
The WISdom monitoring service is a Windows service that runs with a Windows domain account.
- The account will require the “Log on as a batch job” privilege, as it will be used to execute the scheduled tasks used for executing the WISdom components.
Monitoring Virtual/OnPrem Machines and SQL Instances
Windows Monitoring
The Monitoring Service Account may be used, or different Window account may be configured and utilized for the collection.
- Local or Domain Account with:
- Remote WMI access on the servers it will be used against
- Remote DCOM access on the servers it will be used against
SQL Instance Monitoring
To collect data from a SQL Instance, the Monitoring Service Account, a different Windows account, or a SQL account may be used for collection. If a SQL Account is used and a Windows account does not have access to the Host, then the Host Server WMI data will not be collected. The permissions required by the account are:
- For SQL versions prior to 2022, Sysadmin privileges
- For SQL Server 2022 and above, must be a member of both the ##MS_ServerStateReader## and ##MS_DefinitionReader## roles
Monitoring Azure
The account that will connect to an Azure connection may be the Monitoring Service Account, a different Windows account, or a SQL account. For Managed Instances and Azure SQL Databases, Host metrics will be limited or not be accessible. The permissions required by the account are:
- A member of the ##MS_ServerStateReader## role
- ALTER ROLE ##MS_ServerStateReader## ADD MEMBER <Service_Account/Collection_Accoutnt>
- A member of the ##MS_DefinitionReader## role
- ALTER ROLE ##MS_ServerStateReader## ADD MEMBER <Service_Account/Collection_Accoutnt>
Proxy Configuration
If you need to use a proxy for outbound communication, you must set the HTTPS_PROXY environment variable before starting the MSI installer or the Collector service. Note the proxy must support HTTP/2.