Memberships [ 1 ] [+]
Activity Stream [+]
Ideas Contributed [ 6 ] [+]
It would be very nice for us to be able to add a description to each exception we add to our MAV protection policies. This would be especially helpful where we want to share a single Protection Policy with several customers. This way we can indicate which exceptions are pertinent to which customers. Then if that customer ever leaves us, we can remove any exceptions where they are listed in the description field.
We have some customers who have their hands in multiple businesses. They are liking the dashboard access with Take Control. However, they don't like having a separate login (username/password) for each business they are involved with. It would be nice if we could create a "Client user" and then specify which companies they have access to & what permissions they get for each company. I know that an alternative solution ...more »
Client should (perhaps selectively) be given access to the Take Control reports. This creates an audit trail that increases the customer's confidence & comfort level in yielding up remote access to their I.T. support (us). If they can at least see who connected to what machines & when, it increases the odds that they will be comfortable with us having remote access, thus increasing the odds of them signing up for Take ...more »
We have a client who really likes using Cobian backup. It would be nice if the dashboard would monitor its successes & failures in the backup category.
When a customer ever stops using our monitor or MSP services, we need to uninstall the agent from their PCs. 1. This is a good practice for keeping things clean. 2. We don't want competitors who may follow us to find out what technology we're using. They need to build their own businesses themselves. It would be very helpful in these situations, if the agents would auto-uninstall themselves after we have deleted a client, ...more »
In my opinion, the dashboard is hardly branded. If I send clients to my FQDN, which is a CNAME pointing to the dashboard.systemmonitor.us, they have to use unencrypted http, or their browser will throw a certificate error. In either case, this is a bad practice for security. The alternative is to send them to https://dashboard.systemmonitor.us. This is resolves both of the above security issues, but now the URL is no ...more »