Ping & jitter
Choose the destination, packet count and timeout. Inspect latency, loss and variation from the endpoint’s perspective.
AMBARIX SMS / REMOTE DIAGNOSTICS
Diagnose remotely.
Keep evidence local.
Reach endpoints across your organization’s network. Run focused diagnostics and save the results on the technician’s laptop.
Controlled release · Windows endpoint agent · Windows & macOS technician workspace
HOSTED BY AMBARIX
Identity & licensingOrganization roles · Device enrollment · Session authorization
Access authorizationOne-time enrollment
CUSTOMER NETWORK
Technician laptopLocal workspace
Saved evidence
Saved evidence
↔
SMS endpointNative diagnostics
On-demand capture
On-demand capture
Direct encrypted commands, results & files
An existing customer route connects the technician and endpoint. Ambarix does not relay the diagnostic session.
On demandDiagnostics start when your technician requests them.Organization accessRoles and licences govern each enrolled endpoint.Local evidenceReports and packet captures save to your chosen folder.
FOCUSED CAPABILITIES
What you need to
investigate the connection.
A compact diagnostic toolkit with clear controls over access, capture scope and saved results.
Native packet capture
Select the endpoint adapter and capture bounds. Receive PCAPNG evidence directly using Windows Packet Monitor.
Identity-bound access
Organization membership, endpoint licences and short-lived authorizations govern who can start a diagnostic.
Local diagnostic history
Review command requests and response details in the technician workspace. Save reports alongside capture files.
Customer network routes
Use an existing permitted route across sites, including routed LAN, MPLS or customer VPN connections.
Controlled software access
Organization administrators enroll devices against licence capacity and distribute authorized release packages.
FROM ACCESS TO EVIDENCE
Three steps to a diagnostic session.
Enroll the endpoint.
Your organization administrator creates a one-use enrollment token. The installer binds the Windows client to your licence.
Open SMS Technician.
Start the laptop workspace and sign in through Ambarix. Choose the authorized endpoint for your session.
Connect and save locally.
Enter the endpoint’s customer-network address, select the diagnostic, and save the returned evidence on your laptop.
CLEAR BOUNDARIES
Hosted access.
Customer-local diagnostics.
The web portal keeps the access and licensing records needed to operate the service. The technician workspace handles diagnostic content.
Read the data-handling statement →Does Ambarix store our diagnostic files?
The application provides no Ambarix upload or storage route for diagnostic reports or packet captures. Reports are written on the technician laptop. Packet-capture generation uses temporary files on the endpoint, with cleanup after processing.
Is there background telemetry?
The SMS diagnostic client does not collect background telemetry. Control requests are used for sign-in, enrollment and session authorization. Diagnostic requests are initiated by the technician.
Do both devices need to be reachable?
Yes. Your organization supplies the route and permits direct TLS traffic from the technician to the endpoint on TCP 47831. The service does not provide a cloud data relay.
Where do I download the software?
Sign in to the customer portal and open Downloads. Your organization needs an active licence and an authorized role, and the release must be enabled by Ambarix.
Can one organization access another?
The control service checks organization membership and object ownership on each protected operation. Endpoint authorizations also bind the organization and exact device identity. Access testing is part of every release review.
Bring the investigation to your network.
Start with your organization’s access and an enrolled endpoint.