Microsoft Key Management Service (KMS)
- 24 Mar 2022
- 1 Minute to read
- Print
- DarkLight
- PDF
Microsoft Key Management Service (KMS)
- Updated on 24 Mar 2022
- 1 Minute to read
- Print
- DarkLight
- PDF
Article summary
Did you find this summary helpful?
Thank you for your feedback
Microsoft Key Management Service (KMS) enables organizations to activate systems within their own network, eliminating the need for individual computers to connect to Microsoft for product activation.
Parameters
- MSSQL Server (required) - The DNS / IP Address of the Microsoft SQL Server your Microsoft Key Management Service (KMS) instance is using.
- To use a specific named instance, the value supplied should be in the following format: {server_host}\{instance_name}.
- If no instance is supplied, the default instance will be used.
- Port (optional, default: 1433) - The port used for the connection.
- Database (required) - The name of the database inside the SQL Server.
- Username (required) - A user name that has the Required Permissions to fetch assets.
- Password (required) - The user's password. The password must not include ";".
- For details on the common adapter connection parameters and buttons, see Adding a New Adapter Connection.
Advanced Settings
Note:
Advanced settings can either apply for all connections for this adapter, or you can set different advanced settings and/or different scheduling for a specific connection, refer to Advanced Configuration for Adapters
- SQL pagination (required, default: 1000) - Set the number of results per page received for a given SQL query, to gain better control on the performance of all connections for this adapter.
NOTE
For details on general advanced settings under the Adapter Configuration tab, see Adapter Advanced Settings.
Required Ports
Axonius must be able to communicate with the MSSQL Server via the following ports:
- Microsoft SQL Server discovery port - 1433.
- The specific port for the supplied named instance, if relevant.
Required Permissions
The value supplied in Username must have read access to devices.
- The best practice is to create a dedicated SQL local user for Axonius usage. For details, see Creating a Local Read-Only User for Microsoft SQL Server.
- If you are using a domain user, specify the domain and the user name in the following format: domain\username.
Troubleshooting
- "Login failed" - If you are using a domain user, in the User Name field, specify the domain and the user name in the following format: domain\username.
Was this article helpful?