MSP Centralized Management
under review ( scoping )
BramTech
I'd love to see a section within the MSP Dashboard that allows for Global Management of client sites/policies/block pages. Ideally this would include a list of all sub-organizations with the ability to set/change policy and block page assignments without having to impersonate each organization to do so.
Carl Levine
under review ( scoping )
Deon
The ability to add all of our tooling domains to a global "Local Domains" list would greatly reduce reporting noise, greatly reduce the number of requests DNSFilter must answer, and greatly reduce admin time.
10-15 of our top 20 domains by query are related to tools that we use to perform remote access, security and various other parts of the services we provide to our customers.
This just needs to be identical to the Global Allow/Block lists.
Allow the MSP to supply the DNS servers we would like to utilise - Say, if we want to use 1.1.1.1 and 1.0.0.1 for all of our tooling (huntress.io as an example), we should be able to.
Steve Staden
Deon: Appreciate the feedback and it's a good idea. I added you to this item around the noisy domains for reporting - https://dnsfilter.canny.io/feature-requests/p/filter-noisy-domains-in-reporting.
Steve Staden
Merged in a post:
Allow login session to work with multipule sub-organizations at the same time
Jesse
When opening multipule suborganizations via seperate tabs in a single login session, all tabs or windows update to the last selected MSP suborganization.
requesting an enhancement that would make it possible to work with different suborgs across the single login session.
Steve Staden
Merged in a post:
MSP suborg managed on one page
David
Would be great to be able to view all managed MSP deployment site on one page
Mikey @DNSFilter
Merged in a post:
MSP - Provide central management/reporting for Roaming Agents
Scott Thomson
As a MSP we need some better options for global management of Roaming Agents. In particular, its currently difficult for us to perform 'stale device management' as it appears our only option is to review customer-by-customer/site-by-site to identify installs that have not been seen in recent history.
Andrew
Along these same lines, we need to be able to REMOVE roaming clients, particularly if off-boarding a customer.
As an example, we off-boarded a customer, triggered a DNSAgent uninstall through RMM for all computers then the next day removed our RMM. 3 computers were not on at the time we uninstalled DNSAgent so they could not remove the agent, but then when turned on 3 days later the computers were cut off from the internet thanks to DNSAgent (and we disabled their DNSFilter account).
I would envision this working so that when the DNSagent queries DNSFilter for a query including the clientIT, the response has a flag set that triggers at least a DNSagent disable if not a DNSagent uninstall command.
Martin
Would be great is we can set Site policy defaults including default blocking page.
Pat DiPersia
Annnnnd. . . We need a data column showing last contact date. Last check in date is NOT last contact date I've come to find out. You will see machines that are active, but last check in date could be a month old.
Darrin Piotrowski
Pat DiPersia: More details too. Not just last traffic received over/under 15 minutes.
Mikey @DNSFilter
Hello voters! We are looking more closely at what a true MSP Dashboard means for our customers. Do you have any specific features you wish to see "centralized"?
David
Mikey @DNSFilter: The ability to allow / block list a URL across all clients would be very helpful. The use case I see would be this: a ticket comes in reporting a phishing email. We check the URL and it's not blocked by DNSFilter yet. We want to immediately block this for all of our clients, but unless each client used a global policy, we'd have to go through each policy to block the malicious URL.
Mikey @DNSFilter
Thanks David. I'll keep this in mind as we progress.
Chris
David: Yes, definitely this! The case for Allow across all clients is when we identify a legitimate newly registered domain that is still being blocked by our default policy but multiple clients may hit it (like if they have a common vendor with a new site). Also the ability to view logs across all clients and sites in one view. If we have a concern with a particular domain for one client, we may want to quickly query across all our clients to determine if other clients are reaching out to that same domain.
Aaron
Mikey @DNSFilter: I'll echo a prior merged comment; we need a way to view ALL roaming clients on a single page without needing to go client-by-client. We like to check up on things to make sure everything is running, online, up to date. Filters to only show offline devices (truly offline, not 'not checked in' (why that is a different thing, I do not understand)) etc would be great. And yes we need a way to actually initiate an uninstall FROM the portal, and those commands need to queue even after the site is removed so computers don't break afterward.
Mike
Option to make a default template for new clients with those settings too.
Load More
→