How to install and run mid server with other than the window admin

[sapna_sagar]

How to install and run mid server with other than the window admin means with different user??

[iadityas · Accepted solution]

Hi Sapna,

1) MID Server - The Windows account used other than Local Admin account must be also part of Admin group and it has nothing to do with ServiceNow User profile.

2) The ServiceNow User profile is only used for MID Server installation and that one must have mid_server role associated to it.

3) For SCCM integration, you would need to mention MID Server, java program primarily for connectivity. SCCM Data Sources will need credentials for SCCM SQL Server along with Database details. If you wish to identify recorded created in SCCM staging tables with which ServiceNow User profile, do mention Run As in Scheduled Imports otherwise if left blank it will show system/guest.

Please let us know if you got any more queries or mark question answered correct for the benefit of others. Thank You!

[sapna_sagar]

Thanks,,,it is really helpful.

can u help me little more about identifier:

1.   when this identifier actually triggered/called?

2.   ciDATA gives source data or target data??

[iadityas]

Hi Sapna,

To quickly understand how this works, I recommend what this short video.

Identification and Reconciliation Feature Part 1 - YouTube

For Discovery specific CI Identifiers are explained in detail in below Docs link

Discovery identifiers

[sapna_sagar]

Video is not talking about script. My question is when above Script will triggered. What is triggereing Order of this script??

[iadityas]

Hi Sapna,

Data population scripts added with the Integration - Microsoft SCCM plugin populate the related data in the CMDB for each target CI discovered by the SCCM ID & Class Name identifier.

SCCM integration uses CI identification to update CIs created from data imported from SCCM with a resource ID. A Discovery Identifier called SCCM ID & Class Name returns the resource ID of a computer from SCCM and stores it in a table called Source [sys_object_source]. When resource IDs are first imported, either from SCCM or Discovery, ServiceNow populates the Source table with IDs for each CI it identifies. In subsequent imports, if an incoming ID matches that of an existing CI, ServiceNow updates the information for that CI in the CMDB. If the incoming resource ID does not match that of an existing CI, ServiceNow creates a new CI and populates it with the resource ID.