Initial Setup

• Run RemoteAgentToolkit.exe.
• This will generate a configuration.json file in the same directory as the agent.
• Close the RemoteAgent.Toolkit.exe 

Set the location and Project of the MS Server to connect to

Open configuration.json in Notepad and configure the following settings:

"ProjectId": 1,
"ServerUrl": "http://servername",

Authentication

The Remote Agent Toolkit supports two types of authentication. MS API Auth Token and Client Certificate.

MS API Auth Token

An API token is generated by an MS engineer and will be provided. 

1. Open configuration.json in Notepad and configure the following settings:
2. "ServerAuthToken": "tokenValue..xxxxxx",  
3. Save and close configuration.json.

Client Certificate

Client Certificate auth is involves creating a certificate on the client and sharing that certificate with the MS Server to ensure only traffic originating from the client machine can talk to the MS server

1. Enable Client Certificate Auth 

1. Open configuration.json in Notepad and configure the following settings:
2. "UseAuthCertificate": true,  
3. Save and close configuration.json.

2. Generating and Sending the Certificate

1. Run RemoteAgent.Toolkit.exe again.
2. This will create a local certificate file, e.g., ManagementStudio-Agent-Trust-xxxx.cer.
3. Close the agent.
4. Send the ManagementStudio-Agent-Trust-xxxx.cer file to the MS server team.

3. Configuring the Server

On the server, place the ManagementStudio-Agent-Trust-xxxx.cer file in the EdgeServerCerts folder inside the project’s storage directory.

Retrieve the certificate thumbprint:

Double-click ManagementStudio-Agent-Trust-xxxx.cer and go to Properties to find the thumbprint.

Edit appSettings.json:

1. Add the thumbprint to the CertificateAccounts section in appSettings.json:
2. e.g. "CertificateAccounts": "apiaccount|57452bd965592xxxxxxx"
3. Replace "apiaccount" with the account that the Agent will be logged in as.
4. Save the changes.

Restart the MS Application Pool.

4. Running the Agent

Back on the Agent machine, run RemoteAgent.Toolkit.exe again. The Agent should now log into MS and run and any scheduled connectors or events.