Since the release of N-central 2020, the script no longer works as a new parameter is required called REGISTRATION_TOKEN. This is because SolarWinds introduced the idea of Registration Tokens when installing the agent - a Registration Token is specific to a customer and can have a range of expiry options (the default is 30 days). The new format to install the agent needs to be:
SOAgentSetup.exe /s /v" /qn CUSTOMERID=<customer_id> CUSTOMERSPECIFIC=1 REGISTRATION_TOKEN=token_guid SERVERPROTOCOL=HTTPS SERVERADDRESS=<server_ip> SERVERPORT=443"
To create a permanent GPO solution, additional work would be needed in N-central to remove or extend the expiry of the Registration Token, otherwise the GPO would stop working after 30 days. The REGISTRATION_TOKEN value would need specified in the GPO along with the Customer ID and domain name (e.g. 405 625e5618-4c21-54de-72a4-2d2e6285ea87 BAYTREE).
Since the release of N-central 2020, the script no longer works as a new parameter is required called REGISTRATION_TOKEN. This is because SolarWinds introduced the idea of Registration Tokens when installing the agent - a Registration Token is specific to a customer and can have a range of expiry options (the default is 30 days). The new format to install the agent needs to be:
SOAgentSetup.exe /s /v" /qn CUSTOMERID=<customer_id> CUSTOMERSPECIFIC=1 REGISTRATION_TOKEN=token_guid SERVERPROTOCOL=HTTPS SERVERADDRESS=<server_ip> SERVERPORT=443"
To create a permanent GPO solution, additional work would be needed in N-central to remove or extend the expiry of the Registration Token, otherwise the GPO would stop working after 30 days. The REGISTRATION_TOKEN value would need specified in the GPO along with the Customer ID and domain name (e.g. 405 625e5618-4c21-54de-72a4-2d2e6285ea87 BAYTREE).