The Argos "pop-up" (officially the Argos Desktop Client) appears on a user's desktop and asks them to enter a project code after they print.
It only appears when all of these are true:
- The username/domain on a tracked print job matches the username/domain of an Argos desktop client connected to the Communication Service
- Both the user and the device are in interactive Argos groups
The desktop client and print/copy tracking can each work fine independently — the popup simply won't fire if the matching condition above isn't met.
Before you start: open the Communication Service Health Page in a browser:
-
http://YOURARGOSSERVER:7080/cs/health(from any machine), or -
http://localhost:7080/cs/health(from the server itself)
Argos 7.7+ shows the last 200 tracked jobs here. If you can, have the user send a fresh test print first so you're working with current data.
With the health page open, work through these four questions in order.
1. Is the desktop client installed and connected?
- Check the CS health page, or look for the "A" icon in the user's system tray.
- Red icon → client can't reach the Communication Service. Try restarting the Argos Communication Service, or open port 7080 on the server's firewall.
- Not installed yet? See Installing the Desktop Client, or your IT team's preferred method — Deployment Center or Group Policy.
2. Is the user in an interactive Argos user group?
- If not, the CS health page will show "automatic based on user settings" for their job (expand the "+" in the last-jobs section).
- Fix: in Argos Manager → Users, change the user group setting from silent to interactive.
- You can also check the Recycled section of Reports and Data in Manager for a test page marked "Auto-billed based on User Settings."
3. Does the tracked job's username/domain match the desktop client login?
- Both fields must match exactly for a popup to appear — this is especially common to check in Mac environments.
- Fix: merge the accounts in Argos Manager, then restart the Communication Service. Print driver user settings can occasionally play a role too.
- Not sure what's causing a mismatch? Include screenshots of the CS health page in your support ticket.
4. Is the device tracked and placed in an interactive device group?
- No prints showing in the last 25 jobs? Install the print tracking server component on wherever the job spools (print server or workstation), and confirm the Argos Agent Service is started there.
-
Using device integration or onboard tracking? This gets more nuanced:
- Integrated/onboard jobs show "service id xx" under "device service info" in the last 25 jobs.
- Windows-queue jobs for integrated devices are intentionally set to bill silently ("automatic based on device settings") to avoid double billing — this is expected, not a bug.
- Want windows-queue tracking instead and seeing "automatic based on device settings"? Move the device into an interactive device group in Argos Manager.
- If the device sits in the "Advanced Tracking" catch-all group, it's likely meant to be tracked via integration. If you're not seeing "service id xx" jobs, restart the relevant Argos Integration (or brand-specific "Argos Onboard for XXXX") service and check its device mapping.
- See also: Integration devices vs. Windows tracking.
Still stuck?
Open a ticket with Sepialine Support — include health page screenshots and the steps you've already tried.
0 Comments