Summary
This article describes a process for automating the deployment of LeanSentry agents in an OnPremise environment.
NOTES:
- For information about automating deployment of a SAAS version of LeanSentry, please see this article.
- This article describes the deployment of LeanSentry agents, AFTER you have already deployed the LeanSentry OnPremise system itself. For more information about deploying LeanSentry OnPremise, see your OnPremise portal.
Obtaining the required files
You'll need the following files from your OnPremise installation:
c:\LeanServer\Dashboard\Assets\Installer\NewInstaller
- InstallProduct.exe
- InstallProduct.exe.config
- LeanServer.AutoUpdater.Shared.Util.dll
- LeanServer.AutoUpdater.Updater.dll
c:\LeanServer\Dashboard\Assets\Installer\OnPremise
- InstallLSUpdater.exe
- InstallLSUpdater.exe.config
- lsupdater.cab
- RecordingService.cab
- AgentService.cab
Place all these files into the same directory from where the agent installation will take place.
Installing the agent
To install the agent on each server, you'll need to copy the files and run the following commands on each server. Note that these commands install both the LeanSentry Monitoring service AND the LeanSentry Agent diagnostic service.
InstallProduct.exe RecordingService.cab /local "/p:ClientKey=KEY;ServerName=SERVERNAME;ControlEndpointHostName=CONTROLENDPOINT;ControlEndpointAllowUntrusted=true;DisableUpdate=true;AccountName=ACCOUNTNAME;AccountPassword=ACCOUNTPASSWORD;AddSelf=true;GenerateServiceAccount=false"
InstallProduct.exe AgentService.cab /local "/p:ClientKey=KEY;ControlEndpointHostName=CONTROLENDPOINTHOSTNAME;ControlEndpointAllowUntrusted=true;DisableUpdate=true;AccountName=ACCOUNTNAME;AccountPassword=ACCOUNTPASSWORD;AddSelf=true;GenerateServiceAccount=false"
The following parameters must be replaced in the command lines above to install:
KEY |
The environment-specific access key given during installation. |
CONTROLENDPOINT |
The onpremise VM hostname (to which the data will be sent). |
ACCOUNTNAME |
Omit if using autogenerated local accounts to run the monitoring service. Otherwise, specify a valid local or domain account to run the service as. |
ACCOUNTPASSWORD |
Omit if using autogenerated local accounts to run the monitoring service. Otherwise, specify a valid local or domain account password to run the service as. |
GenerateServiceAccount |
true: will autogenerate local service account. |
SERVERNAME |
The friendly server name to assign to the server, instead of the machine name. Must be unique in domain/environment. |
Comments
0 comments
Please sign in to leave a comment.