SharePoint 2016 Discovery/Service Mapping

[Blaine Hopkins]

Anyone having success discovering or mapping Sharepoint 2016? I'm not surprised there is nothing for Sharepoint 2019 yet but a bit surprised that there is nothing for 2016.

In the past, we had cmdb_ci_appl_sharepoint records and Sharepoint service maps but they are no longer populating when we upgraded to Sharepoint 2016. The map, I'm sure, is no longer working because of the upgrade. The cmdb_ci_appl_sharepoint table still has records but those records only go up to version 15 which corresponds to Sharepoint 2013.

When reading through the discovery pattern(s) for Sharepoint, their identification patterns only have logic for 12 (2007), 14(2010), and 15 (2013).

Is ServiceNow expected to release an update to encompass Sharepoint 2016 discovery? I would expect so for such a common platform. Is there a roadmap anywhere that shows pattern expectations? If not, and we customize the pattern to fit 2016, will a ServiceNow update to the pattern in the future override our customized pattern or does it do a skipped modification until we do a code compare and push their version?

Thanks.

[Eduard T]

Hi Blaine,

Slight off topic question. How did you start mapping the sharepoint service? I started with the same URL the user would access:  https://<host>/sites/<sitename> but this only adds an IIS server on the map when in fact there are 2 webfront servers, 2 application servers and one db server. Would be grateful for any hints that you have. Thanks a lot!