This chapter describes how files are managed, stored, transferred and downloaded within PxM. The following topics are included in this chapter:
3.12.1. Manage files
Files are created when device tasks are executed through PxM and can be viewed on the Manage files page. Device tasks are defined within the template, but not all tasks produce a file. See Template library.
Available device tasks can be:
Added to profiles and run via the PxM Client.
Scheduled to run at specified times through a profile.
Executed immediately through the Device detail page or profile.
The information presented in the table includes:
|Timestamp||Date and time the file was created.|
|Device||Device name the task was created against.|
|Size||Download file size.|
|Type||File type relating to the task run.|
|Message||Additional information about the file.|
|Missing?||If the checkbox is ticked, it means the file is no longer available but the entry still exists in the PxM database to record that it once existed.|
|Actioned by||Name of the PxM user who executed the task.|
|Allows you to download and save the file.|
3.12.2. Disk usage and freeing up disk space
The disk usage bar(s) provides a breakdown of how the disk space is being used and the amount of free space available.
All files are stored locally on the Osirium Server as default unless an external disk has been configured, in which case all device files and Session Recordings will be stored on the external disk. See Use external filestore.
When disk space reaches 80% full, an amber warning message will appear on the Web Management Interface. When it reaches 90% full, you will get a red error message.
To free up disk space:
- Delete kits copied to the server. These can be found at root level.
- Delete any extracted kits which can be found in /data/kits.
- Increase PxM’s disk size. See FAQ Increasing Osirium’s Disk size using Logical volume.
- Add an external disk if you don’t already have one. See Use external filestore
- If you already have an external disk, then extend it. See FAQ Extending the external filestore disk used in Osirium.
3.12.3. Transferring files to and from devices
PxM controls the movement of files in the following ways:
126.96.36.199. Single sign-on to SFTP clients
When inluded in the device template, the SFTP tool can be added to profiles associated with the device. This allows users in the profile to single sign-on from the PxM Client to an SFTP client, allowing the movement of files.
188.8.131.52. Privileged task automation for file upload and download
When included in the device template, tasks for uploading and downloading files can be added to a profile or carried out on the device in the Web Management Interface.
184.108.40.206. Restricted access to RDP drive mapping and RDP clipboard for Windows Servers
When a remote desktop tool is included in a template, RDP drive mapping and RDP clipboard can be enabled.
Select Allow RDP Drive mapping to expose the PxM Client drives in a user RDP sesssion, allowing users to copy files from the PxM Client to the RDP session.
Select Allow RDP clipboard to allows users to copy data to the clipboard.
For more information on these methods, see Configuring a Profile.
3.12.4. Downloading a file
To download a file, click on the icon at the end of each row and save the file to a preferred location.
To download multiple files, highlight a number of files, then right-click and select from the context menu. You will be asked if your downloads have started. Click Yes, if all the files selected are being downloaded. The files will be downloaded individually.
If you have selected multiple files and only 1 file is downloading, then click No. The following Note window will appear.
Amend browser settings to ensure pop-ups are not blocked before continuing.
The PxM user access role can only download files if they are given permission to the Download file(s) task through a profile.
3.12.5. Deleting a file
Deleting a file permanently removes the file from PxM.
To delete a file from the Manage files page, right-click on an individual file and then click Delete.