Via agent

Please read the requirements before downloadingDownload4.3.48.7445 - Latest StableDownload (64-bit) | Download (32-bit) | Includes ManualUpdater ToolPlease note that the 32-bit version will be discontinued in the forthcoming v4.4.x agentInstallationThe Windows agent can either be deployed via a Wizard, script or via a custom MSI.If you intend to use imaging software to deploy the agent please discuss the use of installation scripts with your service provider. Duplicating agent installations can lead to unexpected results.UpgradingThe USS Agent software supports automatic or manual updates via Configuration Profiles.If you are trying to update from an old version prior to v4.3.38 then you must update to at least v4.3.38 using the Custom repo first and then upgrade to the latest from there.The auto-upgrade feature uses the Microsoft MSI subsystem however it can be influenced by third party security software that alters permissions on files, folders, startup menu and tray applications, such as FSLogix.Change LogTo see the latest changes to the software, please review the Change Log. How did we do? Related Articles Deploying USS Windows Agent via Microsoft Intune Windows agent - force download of anti-malware database Download Chromebook agent -->

Product DocumentationGlobal Vantage PointsEndpoint AgentsInstallingUninstall or Delete an Endpoint AgentWhen an Endpoint Agent is installed on a device, the agent registers with the ThousandEyes platform and is then listed on the Endpoint Agents > Agent Settings page, under the relevant account group (the account group the Endpoint Agent installer was downloaded from).This article covers the processes to either delete or uninstall the Endpoint Agent.Data that has been uploaded to the ThousandEyes platform by the agent will remain in the platform, regardless of whether the agent that generated the data is deleted from the platform, the device the agent was installed on, or both.Delete an Endpoint Agent from the PlatformWhen an agent is deleted from the platform, either manually or via Agent Status Settings, the agent remains on the host device, but it will only check in with the platform during startup and will stop submitting data thereafter.To delete an Endpoint Agent:Expand the relevant agent tab.Note: To retain the current agent, while deleting prior instances, use the Last Contact time from the Endpoint Agents table toDeleted Endpoint Agents are recoverable within seven days from the trashcan icon. The trashcan icon does not appear on the Agent Settings page if no Endpoint Agents are available to be recovered.Uninstall the Endpoint AgentIf an agent is uninstalled from the host device, it continues to stay in the platform until it gets manually deleted, or automatically cleaned up via Agent Status Settings.To uninstall the Endpoint Agent from a macOS device:On the device, open the Applications folder.Drag the ThousandEyes Endpoint Agent application to the trash, or right click on the application and select Move to Trash.Remove the extension from Google Chrome:a. In a Google Chrome browser, locate the Endpoint Agent button in the browser toolbar. b. Right click on the button and select Remove from Chrome….You need to have administrative privileges to remove the extension from Chrome. If the enterprise is managing Chrome then you will see a message (greyed-out) saying that the extension is "Installed by your Administrator".Remove the Endpoint Agent from the ThousandEyes web application:a. Navigate to Settings -> Agents -> Endpoint Agents. b. Expand the relevant agent tab. c. Click the elipsis icon. d. Select Delete. e. Click Delete to confirm.Once the Endpoint Agent has been removed, no more data will be collected.To uninstall the Endpoint Agent via the command line, use the following command:rm -fr /Applications/ThousandEyes\ Endpoint\ Agent.app/To uninstall the Endpoint Agent

Since restoring backup is accompanied with MC restart. In v4.1.0 the entry includes MC version as well.Sync job or Job Run was started or stopped.sign up / login / logoutfailed login attemptincorrect passwordblockUser actions for accessing MC UI. Action 'failed login attempt' means user entered an invalid username. After 10 failed login attempts, user is blocked and event 'block' appears.generate reset password tokenreset password'generate reset password token’ action means that super admin generated reset password token for blocked user via MC UI or generated reset password link for user via srvctrl.'reset password' appears when password is reset from MC UI via reset password link.restore backupBackup is restored by a user or from terminal via srvctrl. This event is followed by MC restart with two events stop/start accordingly.invalid api tokenAction of an API request with an invalid token. failed agent connect attemptThe agent failed to connect to MC because of invalid bootstrap token.rename agentThe agent is renamed by admin from MC UI. restart agent attemptThe agent was restarted from MC UI. It says 'attempt' cause MC only sends shutdown signal and does not control the startup of the agent.stop initial synchronizationInitial synchronization with Reference Agent was manually stopped by a user. Related articles Storage folder Manually collect debug logs from Resilio Connect Event logs filters Monitoring files activity with Splunk Daily and weekly job summary

Purchasing agent status features from Tenfold, please notify Tenfold so we can discuss integration options.If leveraging agent status with Tenfold, the station must be logged in prior to signing in as an agent via Tenfold.One-X Communicator has a known limitation where reason codes may not be reflected properly when leveraging a third-party integration. Avaya Agent for Desktop does not have this limitation.Avaya Agent for Desktop may require that reason codes are configured via Site Administration (Avaya utility) to display reason codes properly.To perform an installation, you will need the following information.CM IP AddressEnter the IP Address of the C-LAN interfaceCM Switch NameSwitch name of the CMLogin Feature Access CodeCM Access Code required to log inLogout Feature Access CodeCM Access Code required to log outBusy Reason Code and Aux Code ListsCM Busy Reason Codes and Aux Codes to add to be reflected in Tenfold’s UI via Agent StatusSkill ExtensionsAll Agents need to be a part of a skill or skills for Tenfold to monitor the login/logout eventsDialing RulesPlease share any prefix information that is needed for dialing external numbersTrunk accessThe code that is required to make an external callTSAPI serverAES virtual IP or IPs associated with a geo-redundant configurationTSAPI streamTSAPI stream namesTSAPI usernameTSAP User IDTSAPI passwordPassword for TSAPI userContext Store API URL (if applicable)If authentication is required, we will need the certificates.ImportantCompleting the TCC x Avaya AES Prerequisites document is required prior to Integrating TCC.Tenfold requirementsTenfold Cloud Connect is an On-Premise agent that connects your PBX with Tenfold Cloud. The agent

And OS-agnostic. It can be performed on the following services: RKE1 (Rancher Kubernetes Engine version 1)RKE2a Kubernetes service in a cloud providerany other CNCF-certified Kubernetes running on x86_64 architecture A production-ready Kubernetes-based deployment of Trento Server requires Kubernetes knowledge. The Helm chart is intended to be used by customers without in-house Kubernetes expertise, or as a way to try Trento with a minimum of effort. However, Helm chart delivers a basic deployment of the Trento Server with all the components running on a single node of the cluster.3.2 Trento Agent requirements # The resource footprint of the Trento Agent is designed to not impact the performance of the host it runs on. The Trento Agent component needs to interact with several low-level system components that are part of the SUSE Linux Enterprise Server for SAP Applications distribution. The hosts must have unique machine identifiers (ids) in order to be registered in Trento. This means that if a host in your environment is built as a clone of another one, make sure to change the machine's identifier as part of the cloning process before starting the Trento Agent on it. Similarly, the clusters must have unique authkeys on the clusters in order to be registered in Trento.3.3 Network requirements # The Web component of the Trento Server must be reachable from any Trento Agent host via HTTP (port TCP/80) or via HTTPS (port TCP/443) if SSL is enabled. The checks engine component of the Trento Server must be reachable from any Trento Agent host via Advanced Message Queuing Protocol or AMQP (port TCP/5672). The Prometheus component of the Trento Server must be able to reach the Node Exporter in the Trento Agent hosts (port TCP/9100). The SAP Basis administrator must access to the Web component of the Trento Server via HTTP