Record the session on the target

When the Force session recording policy is set to Yes, a remote control session is automatically recorded and uploaded to the server at the end of the session. This recording is done on the controller by default. During a collaboration session, a recording that is performed by a controller might not contain the full remote control session if session handover takes place. To ensure that a full session recording can be maintained, server policies can be configured to record the session in the target instead of the controller. The recording can also be saved to the target system after it is successfully uploaded to the server. For more information about the handover feature, see the BigFix® Remote Control Controller User's Guide.

Record the session in the target system
Determines whether the recording of the session is done on the target system instead of the controller, when the Force session recording policy is set to Yes.
Keep session recording in the target system
Determines whether a copy of the session recording, that was done on the target and successfully uploaded to the Remote Control server, is also saved to the target system.

For more information about the policies, see Server session policies.

Note: When the target cannot contact the server to upload the recording, it keeps it in a queue. It later tries to contact the server. If it is successful, it sends a list of the session IDs that correspond to the recordings, to the server. The server checks each ID against the session history and if it does not find a session history for a particular ID it reports this issue to the target. If Keep recording in target is set to NO, the target deletes the recording. If the property is set to Yes, the target removes the recording from the queue but keeps the recording on its own disk. The following scenarios could cause the server not to find the IDs.
  • The BigFix® Remote Control Server was restored from a previous backup, or the server was reinstalled with a clean database and no record of the Session ID exists in the database.
  • The target was configured to connect to a different server. For example, it was pointing to Server1 and now it is redirected to Server2 but this server has no matching Session ID for the recording.