Custom builds
ActivityPulse supports two build types. This public guide covers the branded build only. The unbranded build uses a different installation path, service name, and process names so that antivirus products treat the two builds as separate applications.
If you are deploying the unbranded build, the exclusion paths and process names are different from the branded build above. Sign in to the customer portal and refer to the in portal Help Documentation for the specific exclusion values needed for your unbranded build. The portal documentation is kept current with the version of the agent issued to your organisation.
The unbranded build is intended for organisations that have already given their people the notice, policy and consultation the law requires. The agent itself is the same software regardless of build type. Only the installation footprint differs.
If your organisation has been provided a custom agent build, the process names, installation path, and registry key differ from those listed above. Your onboarding pack includes the exact exclusion values for your build, or contact support and we will supply them.
Verify Exclusions Are Working
After configuring exclusions:
CMD
# Restart the service
net stop ActivityPulseAgent && net start ActivityPulseAgent
# Verify both processes are running
tasklist | findstr /i ActivityPulse
Check the portal. The agent should show as “Online” within 60 seconds. If the agent is still being blocked, check your antivirus quarantine log and threat history for any remaining detections.
Need Help?
If you’re experiencing antivirus related deployment issues, contact our support team at [email protected].
Please include:
- The antivirus or EDR product and version
- The specific detection name
- The threat log entry (screenshot or text)
- Your deployment method (GPO, Intune, SCCM, or manual)