Settings and activity
14 results found
-
3 votes
Jose Cerna
shared this idea
·
-
516 votesJose Cerna
supported this idea
·
-
840 votesJose Cerna
supported this idea
·
-
968 votesJose Cerna
supported this idea
·
-
1,480 votesJose Cerna
supported this idea
·
-
13 votes
An error occurred while saving the comment Jose Cerna
supported this idea
·
-
4 votesJose Cerna
supported this idea
·
-
310 votesJose Cerna
supported this idea
·
-
3 votesJose Cerna
supported this idea
·
-
9 votesJose Cerna
supported this idea
·
-
26 votesJose Cerna
supported this idea
·
-
4 votesJose Cerna
shared this idea
·
-
9 votes
An error occurred while saving the comment Jose Cerna
commented
I am new to Atera, and still getting to know all the features. We use devices attributes in intune like group tag. We already have dynamic groups for users and computers in Azure so those syncing to Atera would help. However it would be amazing as an example have Atera move a device to a site based on attributes or group. Then use either one to trigger an actions like a script.
Jose Cerna
supported this idea
·
-
303 votesJose Cerna
supported this idea
·
This is so important, specially for those of use that have multiple sites.
Currently you can only choose one monitor type, this should also change.
Let me give you the scenario, you have web service that is on premise. You want to monitor ports 80 and 443 but also it's health status page. Right now you would need to make at least two monitors.
Then you want to ensure people on all your subnets plus WAN can still access it. So you would need at least 1, in my opinion 2 monitoring agents per site/subnet plus 2 more for external Wan access.
This would ensure one monitor for that service but we would get a yellow notification when one of the sites can't reach it. Since we have two monitoring agents, we would hopefully know if it's fully down or just one agent is down.
This would save so much time specially when deploying or making changes to firewall, DNS, dhcp etc. As we would know if we broke something right away.
The last one would be a nice to have. For laptops that use wireless, since some clients only have laptops, setup a rule if they are off our network to stop monitoring.