How does MID Server domain seperation work?

[suyogkamath2006]

We have requirement to update all CI's using discovery for existing records.

I have the configured the MID Server user in TOP domain with visibility to all domains.

However in the Identification phase of discovery it does not find the CI from other domains(Although there is match on serial number/hostname/ip etc)

This only works if i configure the MID Server user in the same domain as that of the CI.

What should be the strategy for cases in shared environment with multiple customers where I do not want to end up creating hunderd's of users based on company domain

[doug_schulze]

You've made it work as I understand the domain separation to work with discovery.. Its based on the company domain..

[suyogkamath2006]

Hi Doug,

I would like to know the case where MID Server user has visibility to other domains but still doesnt update the CI

Instead it creates a new one in the same domain where the user belongs to.

Our case is that we have 100's of company domain's and i would like to configure the MID Server user in such a way that it

updates all CI's where the MID Server user has visibility.

We do not want to end up creating those many users per company domain

Have you seen such case and what is your recommmendation

[doug_schulze · Accepted solution]

No, domain separation works on the user, you have configured it correctly. You cannot have a midserver run as a global user and update a CI in a sub-domain, you will have to create the users in each company

[suyogkamath2006]

Thanks Doug for the quick reply.

Now i have clarity on how domain separation works on user level.

But it would have been really good if we could have had this functionality in place as you mentioned

single user in global domain with visibility to all domains - that case we would save a lot of effort to maintain these users which are required for integration/configuring discovery etc