Network Discovery: Workgroup scanning
In addition to retrieve any device assigned to AD inside a given domain\s, a workgroup scan may be added.
Do you think it's essential or redundant? Does the majority of your customers are using DC inside a secured domain\s?
Please provide examples and use cases
Thanks to you, Atera is better today than it was yesterday! The feature you requested has been implemented and released!
Read more:
https://support.atera.com/hc/en-us/articles/360031190514-Network-Discovery-
We appreciate and rely on your amazing ideas and suggestions! So please keep them coming!
-
Phillip Trimble commented
I am not sure if this is the correct feature request, but I would love to be able to push out the client in network discovery in workgroup networks like it is possible on Domain networks. A lot of networks are moving away from in house domains and this would be a nice feature.
Forgive me if I have perhaps overlooked this, and that it is already there. -
Sam James commented
Hmm just tested this.
Got the OS wrong on 99% of machines and doesn't really add a lot to the mix for the price. Also needs to be able to scan across subnets and grab all types of devices for something super useful - a full asset report of what is on which network. From wifi points to mobile phones - and to grow from that we can create alerts if any new devices are found unexpectedly.
-
Dave De La Haye commented
I have two issues with this current implementation. A) as many others have mentioned, it only works on DC's when many of my smaller clients do not have a domain as such. B) I thought this would be incorporated into the current licensing model. For small businesses like mine, the subscription is simply not sustainable, especially as the majority of my clients have a maximum of 10 users.
Also it only financially viable if on-boarding new clients every month. My business is not rapidly growing, so for the few new clients a month I might take on, I simply cannot justify the cost over a year. It might mean that I subscribe for a month take on clients and then unsubscribe again to save costs. It is a load of hassle I end up doing without and end up doing physical site surveys, which also have the added value of cementing a good relationship with my clients.
-
Manoj Thomas commented
It would be better to have the feature to discover all devices on the network by providing all IP subnets.
-
Simon Ainsworth commented
I tried this out in Beta and it works OK for standalone machines, however, we have customers with Synology NAS drive domains (essentially Samba) that aren't picked up or even available as a scanning agent.
-
Information Results commented
Our clients don't have a DC. So workgroup scanning is essential.
-
miles miles commented
just doing a trial of the network discovery. Did chuckle that it only runs on DC's - means it wont work for most of my clients.
-
Blaise Drayer commented
Would be great to use any computer for this. In my case we have AD on Synology servers so I don't have any DC on Windows to do this job.
-
Robert Naether commented
I have already mentioned this idea to the one of the dev team as most SMB no longer have DC within the companies local network and therefore the current Network Discovery solution is no good for the majority of MSP using ATERA. The last RRM I was using allowed network discovery on multiple agents allowing them to discover most network devices and if one agents was offline one of the others would take over to allow live updates. Hopefully Atera will find a solution.
-
andrea debedin commented
Network discovery to be used on a domain controller is a limitation.
Looking for workgroup-limited customers in advance.
But also: why do I have to prefere to install a network discovery role to a domain controller where I could give this role to a normal server? Great Feature (and a must-have) if implemented. Thanks in advance and good job! -
Simon Ainsworth commented
Yes, we need this, we really do! :) We primarily use NAS servers which don't have AD.
-
Tony commented
Leveraging NMAP or something similar, provide the ability to do network discovery and mapping from a non-domain controller machine. At least knowing what is there can help us provide a more complete picture of what's on the network and allow us to manage these items for our client.
-
Rune Gangstoe commented
Most customers don't use a domain controller.
We are handling small businesses with small locations, but with a lot of network equipment for running the machines needed.
-
STC Admin commented
Many of our clients only have three or four endpoints in their offices. They may be lawyers or small accountant firms. They may need to migrate toward a network with a DC, but for the initial onboarding, there is not a DC to utilize for ND. So we would find it very useful in those cases.
-
Jeff Newland commented
Some of my clients don't have domains so this feature would definitely be beneficial.
-
Aaron Elliott commented
lots of customers have non-AD joined machines, mostly for utilitarian purposes that should be included in the Network Discovery. SNMP devices should too.