Memberships [ 1 ] [+]
Activity Stream [+]
Ideas Contributed [ 8 ] [+]
It would make it so much easier to troubleshoot off of these reports; our client is also requesting it.
It used to be I could run one report at SO level to see which clients had used their N-Central user reports. Now I can only see if my own people have connected. In order to see if a client connected, I have to run a separate report for all clients.
We often have devices that have two NICs. One NIC will get IP Address from DHCP server and the other NIC will have a static assigned IP Address. Devices are never imported into the manage views automatically we will manually import devices into the views. What we would like to have is a scorecard, something that can compare existing data and give back a percentage of probability that the device already exist. Ideally, ...more »
When I run one report for all clients to see what version of software they all have (in this case, VSphere), the report does not indicate the client name for each device. So I have to manually figure out which device belongs to which clients. This should be a standard field, I think, when we can run reports that cover more than one client.
We need a way to designate some machines as not needing AV Defender. We have many clients who have software on a device that conflicts with AVD so they use something else on that device. I have not been able to find a way to designate these machines as not needing AVD, so we get a lower score on the Antivirus section in the Executive Summary report because of it.
I'd like to be able to give a range of times when I'd like a report run (for my financial clients, any time between midnight-8 a.m.; for non-financial clients, maybe between 8-noon) vs saying exactly when it needs to run. Currently I have to manage and keep track outside of report manager when these reports are run, because we had one month where they didn't run at all and the NRC said it was because there were too many ...more »
We would like a setting where we can say after a specific period of inactivity, the connection will end. We routinely have excessively long connections showing up on our client's remote control summary, including one time where it said one of our techs (who travels with his laptop between client sites daily) had been connected to a client's device for over a month.
Most of our clients are financial institutions who really want to get a report to find out WHY we connect to their devices. We would like the option to require our techs to fill in this information, and be able to include it in the Remote Control Summary.