Jeremy Otten

+1 for that. Hope you add new features fast.. the last added features where from April... that 3 months ago..

You have Microsoft Azure support.. where is the Office 365 support then?

Now we can fill in one ESX(i) server or a vcenter server. But when someone has no vcenter.. and two seperate ESX(i) servers they have to use two seperate managers to monitor them

No more explaination needed.. now only to 2013 is supported

At this moment we use groups to see logical seperation between our customers that we monitor. But when we select Roles.. for AD, Vmware or whaterver management.. we do not see a logical seperation.. When customers have alot of the same (standard) server names.. we cannot see which server is for which customer.. As you set this product in the market as an MSP product (also) more logical seperation should be possible...

9 out of 10 times what we do now.. it the username.. what we do not know is the computername.

Now i have to go to a local installed Maager.. do Managed devices (for Example).. and then One by One open devices.. and TYPE in a certain Group.. This is not of this time.. It should be that we only have to install an agent.. connect it to our server.. and then to the management... multiple select / group sorting... policy application etc.. centrally.. with Bulk Actions and all.. Please add this.. the product needs it.

You tell us we can monitor everything on any device from anywhere.. But with the vmware addon you cannot even readout the hardware/health status of esx(i) which is very simple because the API is already there.. you just have to read it out.. that all.. Now we do not know if a disk has failed.. and when the second disks fails.. down goes the ESX(i) server...