Note: Server Hosts (IIS, Apache, Nginx) are third-party products and are not supported by Cisco, please refer to the support teams for respective products for questions outside the provided steps.
Warning: If AMP is configured with a Proxy server, all update traffic (including TETRA) will continue to be sent through the proxy server, directed to your local server. Ensure that the traffic is allowed passed the proxy without any modification while in transit.
Confirm your Hosting Server Operating System (OS).
Confirm your AMP for Endpoints Dashboard portal, download the Updater Software Package and configuration file.
Note: The steps below are based on the new IIS Application Pool to host the signatures, not the default Application Pool. To use the default pool, change the --mirror folder in the provided steps to reflect the default web hosting path (C:\inetpub\wwwroot)
Create a new folder on the root drive, name it TETRA.
Copy the zipped AMP updater software package and configuration file to the TETRA folder created.
Unzip the software package in this folder.
Create a new folder called Signatures inside the TETRA folder.
Update Task Creation
Open the command line and navigate to the C:\TETRA folder.cd C:\TETRA
Run the command update-win-x86-64.exe fetch --config="C:\TETRA\config.xml" --once --mirror C:\TETRA\Signatures
Open the Task Scheduler and create a new Task. (Action > Create Task) to run the updater software automatically with the following options where needed:
Select the General tab.
Enter a Name for the task.
Select Run whether user is logged on or not.
Select Run with highest privileges.
Select operating system from the Configure drop down.
5. Select the Triggers tab.
Select On a schedule from the Begin the task drop down.
Select Daily under Settings.
Check Repeat task every and select 1 hour from the drop down and select Indefinitely from the "for a duration of:"
Verify that Enabled is checked.
6. Select the Actions tab
Select Start a program from the Action drop down.
Enter C:\TETRA\update-win-x86-64.exe in the Program/script field.
Enterfetch --config C:\TETRA\config.xml --once --mirror C:\TETRA\Signatures in the Add arguments field.
Enter C:\TETRA in the Start in field
7. [Optional] Select the Conditions tab.
Check the Wake the computer to run this task option.
8 Select the Settings tab.
Verify that Do not start a new instance is selected underIf the task is already running.
9. Enter the credentials for the account that will run the task.
IIS Manager Configuration
Note: Skip to step 5 when Default Application Pool is configured.
1. Navigate to (IIS) Manager (Under Server Manager > Tools)
2. Expand the right-hand column until the Sites folder is visible, Right Click and select Add Website.
3. Choose a name of choice. For the Physical Path select the C:\TETRA\Signatures folder where the signatures were downloaded.
4. Leave Bindings alone. Configure a separate hostname and server name, chosen names must be resolvable by clients. This is the URL which you will configure in the policy.
5. Select the site and navigate to MIME Types and add the following MIME Types:
6. Navigate to the web.config file (located in the mirror folder), add the following lines to the top of the file.
Follow the steps under Policy configuration in order to configure your policy to use the Update server.
6. Continue to follow the steps under Policy configuration in order to configure your policy to use the Update server.
Navigate to the policy to use the Update Server and under Advanced Settings > TETRA select:
Checkbox for Local AMP Update Server
The hostname or IP for the update server in the format of <hostname.domain.root> or IP address.
Caution: Do not include any protocols before or any subdirectories after otherwise, this will result in an error while downloading.
[Optional] Checkbox Use HTTPS for TETRA Definitin Updates: if the local server is configured with a proper certificate and for the connectors to use HTTPS.
Navigate to the C:\inetpub\wwwroot\, C:\TETRA\Signature, or /var/www/html directory and verify the updated signatures are visible, the signatures are downloaded from the server to the end client by either waiting until the next sync cycle or manually deleting the existing signatures and then waiting for the signatures to download. The default is a 1-hour interval to check for an update.