How to achieve/configure different Discovery Console settings for different Networks ?

[Mike_Freisleben]

Hi there,

we are facing the challenge, that we need to apply different Discovery Consolse settings to different networks.

We are working as managed service provider for a set of customers; the reasons behind this requirement are to extensive to be presented here.

How can this be achieved easily ? Any experiences on that ?

thanks in advance
MikeF

[Pratiksha]

You cannot achieve this through the Discovery Console alone; you need to configure Discovery Behaviors while properly linking the correct MID Servers. For this, the client must provide the IP ranges segmented by device type.

I recommend using standard Discovery, linking it to the appropriate MID Server, and creating credential aliases to ensure the right credentials are mapped to the Discovery schedule.

[MFeldmann]

Hi @Pratiksha ,

thanks for the input!

I'm a colleague of Mike's and we're currently using separate Discovery Schedules for each customer and are working on utilizing behaviors/capabilities to prevent specific entry points (snmp, wbem) depending on the schedule/customer. This gives us a handle on the main configurations in the Discovery Console.

But we're also looking for a way to prevent specific sub-setting for specific schedules, without disabling the main configuration as well.

As in:

• Only run Windows Clusters for customer A, but still run general Windows Servers & Computers for all customers
• Only run Web & Application Servers for customer B, but still run both general Unix & Windows Servers & Computers for all customers

As far as I can see we can only toggle these settings globally.

Is there a way to configure these settings differently for specific schedules?

Preferably without overwriting the OoB Classification of each affected sub-setting.

Regards

Mario Feldmann

[M Iftikhar]

Hi @Mike_Freisleben   ,

You can achieve this by setting up separate Discovery Schedules for each network/customer. Assign the right IP ranges and link them to dedicated MID Servers (using capabilities if needed).

If you require stricter isolation, consider domain separation, but for most cases, multiple schedules + MID Server alignment is the simplest and most effective approach.

Thanks & Regards,
Muhammad Iftikhar
If my response helped, please mark it as the accepted solution so others can benefit as well.

[MFeldmann]

Hi @M Iftikhar,

thanks for the input!

I'm a colleague of Mike's and we're already using separate Discovery Schedules with the plan to change up our current behavior/capability setup.

But as elaborated in my reply to Pratiksha, we're looking for a way to control which (specifically ssh/winrm/wmi) sub-pattern will be fired on a customer by customer basis.

As far as I can see Domain Separation has the same limitations as specific behavior/capability setups in this regard.

Do you know of another way to achieve this?

Regards

Mario Feldmann