2022-12-13
6 minute read
New features in Docusnap 12
- Documentation of cloud infrastructures
- Documentation of Microsoft 365
- Scheduled CSV import
- Automatic site assignment
- Namespaces for customizing
- Provisioning of inventory modules
Documentation of cloud infrastructures
Previously, all inventoried data in Docusnap was mapped below the domain, which typically corresponds to a Microsoft Active Directory domain in an on-premises environment. Cloud services from Amazon (AWS) and Microsoft (Azure) have therefore also been placed below the domain. Docusnap 12 introduces “Cloud Infrastructure” at the same level of “Infrastructure”. Below the “Cloud Infrastructure” are the tenant domains.
Documentation of Microsoft 365
For all Microsoft 365 inventory with Docusnap 12, all information is inventoried via the Microsoft Graph API. This is accessed via an app registered in Azure. The following Microsoft 365 services are inventoried using the Microsoft 365 wizard:
- Licensing and Usage
- Azure Active Directory
- Teams
- Exchange Online
- SharePoint Online
- OneDrive
All services in the Microsoft 365 area are based on or required the Azure Active Directory resource. In addition to the mandatory Azure Active Directory inventory, Teams, OneDrive, Exchange Online or SharePoint Online can also be selected and recorded.
Licensing and use
Here you can basically find the structure of the Microsoft 365 AdminCenter:
- Users
- active users lists all users and contacts that can be managed for Microsoft 365
- Billing
- available Microsoft 365 products (licenses) and licensees (usually users) are listed
- admin center
- the previously recorded identity providers and services as a direct link in the application
use case
With the Licensee data table, Docusnap 12 provides an additional perspective on users in Microsoft 365. This view shows at a glance which user has which Microsoft 365 licenses and products.Azure Active Directory
Azure Active Directory is basically divided into two areas. Information about users, groups, contacts, devices, and enterprise apps is located in the Resources section. Directory roles and conditional policies are grouped under “Permission Assignment”.
Application example
Docusnap 12 makes it possible to transport security-relevant data to the IT documentation via the member listing of critical roles such as Global Administrator (keyword Connect or IT Concept).Teams
Teams has been one of the most requested features since the launch of our Ideas Portal. With Docusnap 12 it is now possible to document teams comprehensively:
- Teams (All existing teams with their respective members, channels, teams activities and teams settings)
- Teams activities (All teams activities of all teams as a total view and for each team)
- All Users (All users with at least one Teams membership as a total view and for each user)
- Deleted teams (list of all still visible deleted teams)
- All apps (list of all apps in the app catalog of this organization)
use case
First use cases would be the identification of teams of an organization that are no longer active. Also an analysis of the teams memberships of users in an “evolved teams structure” could be interesting.Exchange Online
The Microsoft 365 service is already inventoried and documented extensively with Docusnap 11 via PowerShell queries. This module remains in Docusnap 12, its inventory results are unchanged in the “Infrastructure” area. With Docusnap 12, we capture information about Exchange Online based on Microsoft Graph API queries and present it in the “Cloud Infrastructure” area.
- User mailboxes incl. mailbox folders and calendar groups
- Exchange Online activity overviews
SharePoint Online
We capture the web page based information structure of SharePoint Online. The following information is documented in Docusnap 12:
- All web pages (list of all web pages with URL, creation and last edit)
- User activity (activity and usage data of user web pages)
- Settings ( global web pages settings)
use case
An analysis of an organization’s SharePoint site usage.OneDrive
All users who use the OneDrive service are listed in an overview. In addition to the last access, information about capacities and usage is also documented.
use case
Detect OneDrive drives that are at capacity, identify orphaned and unused OneDrive drives.Scheduled CSV import
With Docusnap 12, CSV files can be imported into Docusnap on a scheduled basis. Especially for customers who value a high degree of automation, this is a long-awaited feature. CSV files are automatically imported via our well-known dialog for repeated scheduled execution. Imported CSV files are stored in a subordinate archive directory after import.
Automatic site assignment
With Docusnap 11, it is already possible to assign a site to a Docusnap Discovery Service. If an inventory is now carried out with this Docusnap Discovery Service, the recorded systems are automatically assigned to the stored sites. The problem so far was that the site assignment was only done once. With Docusnap 12, we are now updating the site assignment to match the actual site.
The automatic site assignment takes place according to the following set of rules:
- If a Docusnap Discovery Service has a site assignment, systems inventoried with it are automatically assigned to this site.
- If mapping criteria (e.g., system name) exist for the system being inventoried, they win. The site assignment from the Docusnap Discovery Service configuration is ignored.
- If automatic site mapping is disabled for a system, the site mapping is not changed.
Namespaces for Customizing
Background
If meta schema adjustments were made up to now, it was always necessary to note that an “ObjectTypeID” was created for each object in the “tMetaObject” meta table. For this the number range from 100,000 was available. If now a metaschema extension is imported into another Docusnap database, very often conflicts occur, because the ObjectTypeIDs in the target database were already used for other customizations.
Namespaces
With the introduction of namespaces, the “namespace” is added to the identifier for each new metaobjet or metatable. When a meta-schema export is performed, the export can be limited to objects that have been mapped to a specific namespace. Thus, customizations can be transferred to the target database cleanly and without the need to resolve conflicts.
Note
Nothing has been changed for custom reports and interface extensions. Here you still have to pay attention to a clean and unique naming. This ensures that no problems occur during import.Provisioning of inventory modules
Updating inventory modules with a Docusnap patch previously only replaced the plug-ins in the application directory. An additional option, “Provisioning of inventory modules”, has been added to the Docusnap Discovery Service configuration. This allows standalone executable inventory modules to be deployed for individual use, to a freely definable folder.
Changes in Docusnap 12
DNS inventory - NEW
The DNS inventory has been completely revised to ensure that the information for documentation meets the most up-to-date requirements. Service configuration, security settings, recursion and forwarding settings, statistical data, and zone data are now inventoried. Zones are divided into primary and secondary zones. Four new reports are available for documentation.
DHCP inventory - NEW
The DHCP inventory has been completely revised to ensure that the information for documentation meets the latest requirements. It now inventories DHCP cluster settings, all policies and classes, option definitions, the server configuration in detail, all IPv4 ranges including multicast strings, and statistics. Four new reports are available for documentation.
Physics - Copying cable connections
With Docusnap 12 it is possible to clone cable connections when documenting physical infrastructure. The following information is transferred in the process:
- Cable type
- Cable color
- Elements
- Different connector types
Initial inventory of systems
With Docusnap 12, the date of the first acquisition is additionally stored for systems. This makes it possible to draw conclusions about the entire life cycle of a system.