Before deploying our Agent we recommend checking for any previous
DNS filters that must be removed to avoid conflict. Please set your
DNS addresses back to default settings once the previous DNS filter
is removed. We also have a list of known software conflicts here
(you will need Support access to read this article, reach out to
support@zorustech.com if you have issues accessing the Support
Portal): Software Conflicts
Port 7789 is essential for our agent to properly function, please
ensure this is open on your firewall outbound for our agent to
communicate with our policy servers. Ports we filter
If Threatlocker is in your security stack please ensure it is in
Learning mode when deploying or setup our Built-In Policy we have
with them: Threatlocker Configuration
We recommend excluding your Domain Controllers/DNS servers from the
Zorus Agent Deployment. We only officially support Windows Server
environments when used as a workstation. If you need DNS protection
for Windows Server environments that are designated as a DNS server
such as a Domain Controller we recommend implementing Zorus Network Filtering.
If deploying Zorus Network Filtering ensure conflicting DNS
addresses are removed from your Router, Firewall, Domain Controller,
and Endpoints. As well as the DNS cache is cleared before setting
our DNS servers as the forwarder.
Agent Deployment:
Here we host our scripts and articles on deploying the Zorus agent
through your RMM for the Windows Agent or MDM for the Mac agent
currently in Beta: Zorus Agent Deployment
We have a list of integrations with our portal for both RMM and PSA
Billing and how to set those up here: Portal Integrations