Has anyone built out a CMDB Class for DFS/Windows Shared Folders, or a Discovery Pattern for the same?

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-20-2022 06:10 AM
Has anyone built out a CMDB Class for DFS/Windows Shared Folders, or a Discovery Pattern for the same? Looking to manage our Shared Folder Requests (New Build, Request Access) using CMDB CIs. Thanks.
- 1,488 Views
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-06-2023 08:16 AM
Thank link does not seem to be working anymore. I am very interested in this.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-03-2022 05:48 AM
Done -- upvoted & commented.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-16-2022 01:07 PM
I want to keep this post active as I and others work through this...so updating with some progress on a design strategy I'm trying:
I've been successful in querying our Active Directory using LDAP Query to get the list of DFS Namespaces and Links with paths. I'm thinking this might be a simpler approach then trying to discover them. We know where they are stored, just need to maintain the list. So with the LDAP source defined, I'm hoping I can use IntegrationHub ETL to import these into the CMDB (thinking cmdb_ci_appl table, or extended table for MS-DFS), and go from there.
Keep the thoughts coming!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-11-2022 12:15 PM
I am currently looking into how to solution this as well. The idea of using the cmdb_ci_storage_fileshare table to store the information has me intrigued. It is nice to see that there might be an oob table for this, although creating a new class wouldn't be an issue. One concern is with using this table would be what the actual intent or designed usage of this table actually is. Storing the incorrect data and then having to move it later is something to avoid of course.
Anyone have any additional information on the table usage? I see that it extends from cmdb_ci and that the cmdb_ci_storage_fileshare_pure extends it.
Thank you