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

[Lakhsmi Hanchat]

HI,

Can you help me on providing work instructions document for enabling Discovery on enduser devices

[SNN1]

Hi Robert,

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

[robertgeen]

You should be fine as discovery will go through the identification and reconciliaton process (and I believe the SCCM integration is setup to do that as well). Just check and make sure that the SCCM data has name, serial number, IP address, and mac address data associated to it (honestly name and serial number are the most important). If it has that then you should be fine come time to do discovery. You can also look at the SCCM import job and you should see it making calls out the the CMDB API and if you see that then you are definitely good to go.

The only suggestion I would have is you may want to look at setting it to only use SCCM for installed software so you don't get inconsistent data that leads to duplicates (there is a flag in the discovery properties for that). Thanks.

[SNN1]

Thank you for quick response.

If I understood correctly, You mean both servers and end user data can run parallely with SCCM.

SCCM data has name/Serial number, IP and mac address is not getting populating in Windows server or computer CI,  Under server CI related list  network adapters have IP and Mac address populated from SCCM to network adapter table.

and  only use SCCM for installed software so we don't get inconsistent data that leads to duplicates.

Below are the properties in discovery, Which is the one you are referring

Windows software is SCCM managed: If "yes", Discovery will not populate software for computer CIs also managed by SCCM.

Yes | No

Discover software packages: Enable the discovery of software packages.

Yes | No

My assumption is discovery can pull IP,mac etc, Am i right?

Thanks & Regards,

SNN

[robertgeen]

WIndows software is managed by SCCM is the one I was referencing.

Yes I am saying they should be able to co-exist as long as you at least have name and serial number being populated which it sounds like you are. The only thing you will want to do is make sure other attributes aren't flip flopping and if they are setup reconciliation rules to make discovery or SCCM the truth for them. Either way you should be good to go now. If you have your answer please mark an answer as the correct one so others can reference it later on. Thanks.