![]() ![]() The only workaround so far has been to remove AMP from the machine, but that is not a solution. If it helps, we've already tried using the "Save to Disk" option within Screencastify, which doesn't seem to help, as it only allows for a sort of export to a location within the Windows filesystem, after the HTML5 filesystem has already been used.Īny update to this? My teachers are noticing this as their devices have updated to AMP connector 7.5. Has anyone else seen this with AMP or a similar antivirus product, and does anyone know which locations in the filesystem we might want to exclude from protection in order to resolve this? We're hearing reports that our Cisco AMP for Endpoints antivirus is spiking CPU usage while users run Screencastify, almost to the point of making their machines unusable while recording. ![]() According to its own documentation, it saves files by default to a proprietary HTML5 filesystem somewhere within the profile directory for Chrome (even when the "save to Google Drive" functionality is selected- it saves to that local HTML5 filesystem, first, and then uploads to GDrive once recording has stopped). Screencastify (as if you didn't know) is a Chrome add-on for making screen recordings. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |