Laptop and desktop discovery in service now discovery

[SNN1]

Hi All,

We are implementing discovery in our instance, Need some information in desktop and laptop discovery.

As I understood, We need to provide A domain user with local administrator access on the target Windows hosts in credentials table which discovery will discover Windows servers and will populate in CMDB.

So in order to discover desktop and laptops what credentials need to be configured and to which table will these be updated.

And should these in client environment to discover, please suggest what is the best practice to update laptop and desktops.

any help will be highly appreciated.

Thanks & Regards,

SNN

[dcwilson]

The requirements for the credentials are the same for any device being discovered via WMI.  Your environment will determine if you can use the same account for both servers and end user devices.  If possible, I recommend using the same account purely from a troubleshooting perspective if you ever face authentication issues; since by default all credentials in the credential table are attempted until one is found that works, it's a pain to find which credential is causing the problem in the debug logs.

One caution about SCCM integration updating the CMDB...if a device is still in SCCM but not on the network (ie when it was removed from network the step to remove from SCCM was skipped) SCCM will update the device in the CMDB making it appear as if it is still active on the network.  

In a previous environment we ran discovery on end user devices once in the morning and again in the afternoon because we operated from 7 am Eastern to 9 pm Pacific, we choose times when users would be online but when the least amount of traffic was moving, didn't have any issues with it.

We actually had SCCM integration and Discovery going, SCCM is dependent on the client being installed properly so there is no fool proof method to ensure CMDB accuracy. There were many times Discovery found an end user device on the network that wasn't in SCCM.

[SNN1]

Hi Wilson,

Thank you for your response..

Could  you please let me know if you faced any issues while using both SCCM and Discovery for end user systems like creating duplicate CI's etc 

Let us know if we need to make any custom changes not to mix the data from both sources...

Thanks & regards,

SNN

[SNN1]

Hi Wilson,

We already have Windows servers and Desktops in CMDB popluated through SCCM, We are implementing discovery now 

 ServiceNow discovery is going to be the source of truth for Server and network devices.  SCCM is going to be the source of truth for end user devices.

So what is the best practice to go ahead:

a.) reconcile with windows devices discovered by SCCM that exist in CMDB OR

b.) remove server data discovered by SCCM and also make changes to the SCCM-ServiceNow integration, so that these devices are filtered out before data is pushed by SCCM into CMDB.

Please let us know the best way..

Thanks & Regards,

SNN

[SNN1]

Hi All,

Any code to stop windows servers to CMDB from SCCM, Only need to populate computers data

Regards

SNN

[vinitha3]

Please refer this link - https://community.servicenow.com/community?id=community_question&sys_id=3d107629db06abc0107d5583ca96...