Send files, fetch logs, and use remote terminal
Transfer a file using the permitted device paths, verify its result, and open a consent-based terminal where the deployment supports it.
Before you start
- Open the intended device and inspect its agent connectivity.
- Files requires the relevant file-transfer capabilities. Terminal is shown only when that deployment enables remote terminal.
Screenshots show the Rapport interface with example data. Use your organization’s devices and values. Select an image to view it at full size.
Open Files and confirm the device OS
From the device, choose Files; on narrow screens it may be under More. If the device has not reported an OS, explicitly choose Windows, macOS, or Linux before entering paths. File path rules differ by OS.
What you should see: The form displays paths and examples appropriate to the device.
Send a file to the device
Choose the local File, review Saved on the device as, and include the file name after the destination folder. Use Browse to choose a permitted folder when the agent supports it, then click Send file. Transfers are limited to 100 MB.
| Field or control | What to do |
|---|---|
| Windows destination | C:\ProgramData\DexIQTransfers and allowed subfolders. |
| macOS destination | /Library/Application Support/DexIQTransfers and allowed subfolders. |
| Linux destination | /var/lib/dexiq-transfers and allowed subfolders. |
Fetch a permitted log file
Under Fetch, enter the complete File path on the device, choose a provided example or browse to the file, and set Max size (MB). The default is 10 MB; use a positive value no greater than 100 MB. Click Fetch file and wait for a completed transfer before choosing Download.
| Field or control | What to do |
|---|---|
| Windows readable roots | C:\Windows\Logs, for example C:\Windows\Logs\CBS\CBS.log. |
| macOS readable roots | /var/log and /Library/Logs, for example /var/log/install.log. |
| Linux readable root | /var/log, for example /var/log/syslog. |
Read the transfer result before retrying
In Recent file transfers, verify status, path, size, and the returned error if it failed. A completed send can report SHA-256 verified when the saved bytes match the source file. A fetched file exposes Download after a valid result is available. If the submission outcome is uncertain, inspect this history before sending again.
What you should see: You have a recorded destination and integrity result for a send, or a downloadable result for a fetch.
Open a remote terminal if available
Select Terminal and choose Open session. Follow MFA and policy approval prompts. When the request is Awaiting approval, an eligible administrator uses Approvals and the tab connects automatically after approval. The person at the device must also approve the session.
Close the session and review its record
Use the shell only once the session is live. Click Close when finished; while waiting for approval, use Cancel request to withdraw the attempt. Review Activity → Terminal sessions for session records. The product logs open/close, attachment identity, and byte counts; terminal content is not recorded.
What you should see: The live connection is explicitly ended and its session metadata can be inspected.
If something doesn’t work
The path is rejected.
Enter a full OS-appropriate path inside the displayed readable or writable root, include a file name for sends, and check whether device policy narrows the roots further.
Browse is unavailable on this device.
An older agent or a policy without file-list capability can fall back to typed paths. Enter a permitted path; reload after an agent or policy update to retry browsing.
The transfer failed or its receipt is uncertain.
Read Recent file transfers and the agent error before retrying. Confirm size, permitted path, and the device connection; an uncertain submission may already have reached the server.
Terminal waits for approval.
Check organization approval and device-user consent separately, and keep the terminal tab open while waiting. Cancel request if you no longer need the session.