remFREE can request a screenshot from supported managed endpoints.
Screenshot capture provides a quick visual snapshot of the current desktop without starting a full remote-control session.
When screenshots are useful
A screenshot can be useful when you need to answer a simple visual question such as:
- Is an application open?
- Is an error message visible?
- Is the user at the login screen?
- Did a graphical change appear?
- What does the current desktop look like?
For a one-time visual check, a screenshot can be simpler than opening a complete remote session.
Screenshot capture is a job
The screenshot request is handled as a managed remFREE operation.
The endpoint receives the request, performs the supported capture operation, and returns the result.
This provides a lifecycle around the request instead of treating screenshot capture as an invisible side effect.
Screenshot versus remote control
A screenshot is a point-in-time image.
Remote control is an interactive session.
Conceptually:
Screenshot
=
capture one state
Remote Control
=
continuous video
plus keyboard input
plus mouse input
Use screenshots when a static visual is enough.
Use remote control when interaction is required.
Platform differences
Desktop capture behavior depends on the operating system and active graphical session.
Windows and Linux do not expose screen capture through identical mechanisms.
The remFREE agent therefore uses platform-specific capture providers where required.
Session context
On systems with multiple graphical sessions, the endpoint must determine which session is appropriate for capture.
This is especially important on Windows, where the service session and interactive user sessions are intentionally separated.
Privacy and access
Screenshots can contain sensitive information visible on the user's desktop.
Treat screenshot access as a privileged support capability.
Administrators should use it only for legitimate support and operational purposes.
Troubleshooting screenshot failures
If the endpoint is online but screenshot capture fails, investigate:
- graphical session availability
- endpoint permissions
- operating-system capture restrictions
- helper/session-provider status
- display environment
- job error output
An online heartbeat confirms agent communication.
It does not guarantee that a valid graphical session is available for capture.