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.

[Jennifer Schoe1]

We worked this issue as well, in speaking with ServiceNow support. Patterns only get updated if you update from the store, Search Sys_Plugins.list > ALL, search *Patterns and pick up updates there when they are released. We checked New York documentation and it shows only supported up to Sharepoint 2013.  So we modified the pattern. It should not get overwritten unless we choose to update them from the store.

Modified the Sharepoint Pattern located @Pattern Designer>Discovery Patterns> Search Name *Sharepoint (open cmdb_ci_appl_sharepoint) Pattern click identification for sharepoint and open pattern steps.  Add 3 steps for version 16.0 (which technically encompasses version 2016-2019)

Copy Step 16  to a new step for get Role SPS v16 "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\16.0\WSS"

Copy Step 10 to a new step for get build "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office Server\16.0"

Copy Step 2 to a new step for get registry key "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office Server\16.0"

I hope this helps someone! Upvote if it does.

[bhopkins]

Thanks Jennifer. That looks like the correct steps. I didn't update this question because I hadn't gotten any responses but ServiceNow themselves actually provided us with an updated pattern awhile back as an update set. We moved it around during testing until it eventually got released and cloned down. I do remember it looking very similar to the changes you mention here.

[Jennifer Schoe1]

We have confirmed that this pattern update is actually not released. Even New York patterns confirm only support through 2013. I have submitted the update in the idea portal to have this fixed. For now, anyone who wants to discover these versions will have to complete these steps. 

[bhopkins]

Right. Definitely gives most end users a way to have this work. Thanks for providing the steps. ServiceNow did it custom for us, I guess, so hopefully it comes in one of their 'in between major update' updates within the new pattern store.