→ 🚀What's New? Join Us for the Fall Product Launch! Register Now !

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Lars_Vopicka
Engaged Sweeper
We do have a lot of OUs that are being scanned. Within those OUs are child OUs with Li/U/nix-Servers. Those non Windows Servers show up as Erros in LS interface.

I could certainly disable each of those machines from being scannd by editing the blacklist, but what if new ones are added, or those Servernames are being reused by Windows Systems.

Therefore an exclude OU parameter would be very useful.

example:

OU17-OU17a
-OU17b
-OU17c-OU1a
-OU1b
-OU1c (all UNIX clients)
-OU17d


--> scan OU17 but exclude OU17-OU17c-OU1c


Cheers Lars
3 REPLIES 3
ChrisS
Engaged Sweeper III
Dear Admin,

I too think this option is totally needed. We have a "disabled OU" for users and computer that we must keep for legal reasons. We don;t however want it scanned by Lansweeper.

The jpg the mrdaytrade has uploaded would look like exactly what we need.

p.s. we have Lansweeper scan Multiple domains, so it would also be handy if we could enter an OU for each of those domains.



Is this something that you are putting into a next version?
Hemoco
Lansweeper Alumni
ChrisS wrote:
I too think this option is totally needed. We have a "disabled OU" for users and computer that we must keep for legal reasons. We don;t however want it scanned by Lansweeper.

We are considering introducing OU exclusion in one of our future updates.
mrdaytrade
Engaged Sweeper III
I second this.