The Actifile agent can be easily installed using an RMM, a logon script or even by the end user (given a tenant install key). The following collection of links and data provides the MSP or IT manager with all necessary prerequisites and considerations for the different types of deployments.
Windows Server (2012, 2012 R2, 2016, 2019)Windows 10 (All versions except IOT)Windows 8 (All versions)Windows 7 (All Versions) – Support DeprecatedMac OS 10.14.xMac OS 10.15.xMac OS 11.0-11.5
ChromeEdge (Chromium and Legacy)FirefoxSafariOpera
Most MSPs would use their RMM to deploy the Actifile agents to the endpoints. This facilitates automation of the installation and management of the various installation keys.
Sometimes an RMM isn’t available. In these cases the following tools are great to make deployment easier.PDQ Deploy – The free version supports most common deployment scenarios. Has an easy to use UI.PSTools PSEXEC – Tried and tested tool from Microsoft’s Sysinternals. Command Based tool does need basic batch file writing/editing. Logon Script – Sample installation script (AD logon script) shows how to check if Actifile is deployed and deploys if it isn’t.https://actifile.com/wp-content/uploads/2020/04/Installation.rar is a nifty batch file written by an MSP (Momentum Z – used with their permission) that is sent to a user and which automates the installation. Remember to change the install key in the key file.
NEW: https://actifile.com/wp-content/uploads/2021/01/deployActifile.ps1 Powershell script that can be used to download and install Actifile on clients computers. Can be use as a logon script – it checks if already installed and quits. Logs the result into %tmp% directory. Downloads the MSI from Actifile into %tmp%.
Troubleshooting a failed agent deployment: https://actifile.com/docs/troubleshooting-an-agent-installation/
Removal of the agent needs the same installer version that was used to deploy. For customers it isn’t a problem as they usually have 1 installer. But for MSPs the problem is that it isn’t always easy to track which version was used to install to which customer and which device.
So we’ve created a Powershell script to remove Actifile. Intended for RMM use, it checks for proper Admin privileges, stops the services and processes, unmounts the filters, and runs the uninstaller using WMI (so don’t have to keep any version of the installer). It creates a log file (at $Env:TMP ActifileUninstall.log), and stuffs error messages into the log.
The uninstall script is at: https://1drv.ms/u/s!AnGFvQ5rPFi4gedlJlMTErLENLSf7g
The main uninstall command used in the script leverages WMI uninstall method:
$vPackage = Get-WmiObject Win32_Product -Filter “Name=’Actifile Agent'”
But that isn’t sufficient as the service protects itself from removal (and will popup a request for the uninstall key). To get around that, the script first disables the services and unmounts the drivers (leveraging the admin credentials).
See at https://actifile.com/system-updates/
Administration manual (Pages 11-13): https://actifile.com/docs/actifile-administration-manual/How to use the silent install functionality: https://actifile.com/docs/silent-install/Mac Installation: Mac Agent Download and Installation – Actifile
(Important) Prevent AV/EDR caused slowdowns: https://actifile.com/docs/antivirus-edr-collision-performance-issues/Enabling the tamper resistance functionality: https://actifile.com/docs/actifile-tamper-resistance-uninstall-key-functionality/Switching agents between tenant accounts: https://actifile.com/docs/switching-agents-between-tenants/
https://app.actifile.com/Home/DownloadAgentMsiMac Agent Download and Installation – Actifile
Powered by BetterDocs