HCL Domino License Analysis Utility
2 |
3 | # HCL Domino License Analysis Utility
4 |
5 | This utility will assist HCL Domino Administrators in doing a health check based on deployment best practices and determining the Authorized User Count within an HCL Domino environment according to the CCB & CCX license model.
6 |
7 | ## Purpose
8 | The purpose of this utility is to provide fast and accurate Authorized User counts for HCL Domino environments by aggregating information that a Domino Administrator would otherwise have to collect manually.
9 |
10 | The DLAU automates the process by aggregating all the information that is needed to accurately determine the Authorized User counts in a fraction of the time.
11 |
12 | ___
13 | ## Documentation
14 |
15 | Please refer to [this page](https://opensource.hcltechsw.com/domino-license-analysis-utility-DLAU/)
16 | 17 | ___ 18 | ## Change log 19 | 20 | We will keep track of each release in the [CHANGE LOG](/docs/changelog.md) 21 | 22 | ___ 23 | ## Code of Conduct 24 | 25 | To understand our Code of Conduct and how we handle misuse, please read the following: 26 | [CODE OF CONDUCT](https://github.com/HCL-TECH-SOFTWARE/domino-license-analysis-utility-DLAU/blob/main/CODE_OF_CONDUCT.md). 27 | 28 | ___ 29 | ## Contributing 30 | 31 | Please read through our [Contributing Guidelines](https://github.com/HCL-TECH-SOFTWARE/domino-license-analysis-utility-DLAU/blob/main/Documentation/CONTRIBUTING.md). Included are directions for opening issues. 32 | 33 | ___ 34 | ## Versioning 35 | 36 | The HCL Domino License Analysis Utility will adhere to the following versioning guidelines as much as possible. Releases will be numbered with the following format: 37 | 38 | `Known Limitations
10 | 11 | Below is a list of current limitations that will be encountered in certain HCL Domino environments when using the Domino License Analysis Utility 12 | 13 |
14 |
21 |
22 | ___
23 | ## LDAP/Active Directory
24 |
25 | Direct scanning of LDAP/Active Directories is not supported. However, as of DLAU 1.2.2, you can now leverage Entitlement Tracking to make sure those users are counted.
26 |
27 | ___
28 | ## Multiple/disconnected HCL Domino Domains
29 |
30 | For HCL Domino environments that have different, unique Domino Domains that are not connected using any type of Directory Assistance, the DLAU will only scan the Domino Domain that was discovered based on your current HCL Notes Location document.
31 |
32 | A common scenario are test or development Domains, or Domains that were put up for specific business functions isolated from the rest of your production environments. Please keep in mind that all of them need to be scanned to get a complete picture of the license needs.
33 |
34 | In order to scan all domino Domains in this scenario, you will need to create / use different Location documents, one per Domino domain, that list the Domino Administration server as the "Home/Mail Server".
35 |
36 | It is required that you use different copies of the DLAU, one copy per Domino Domain. By using multiple copies of DLAU, you will retain the informaiton for each Domino Domain that has been scanned.
37 |
38 | Then, a manual deduplication of discovered Notes Users will need to occur. This is to ensure that a single user that is listed in each Domino Domain is only counted once.
39 |
40 | {: .note }
41 | We are working on a solution that will allow for multiple Domino Domains to be scanned at the same time by allowing multiple Domino Administration servers to be selected.
42 |
43 | ___
44 | ## Directory Assistance on Servers other than Administration Server
45 |
46 | As of DLAU 1.2.1 this limitation has been removed.
47 |
48 | {: .highlight }
49 | Note: this limitation was removed as part of the work done in DNEXT-23861 to enhance Directory Assistance scanning.
50 |
51 | ## List of Domino Servers in the report
52 |
53 | On the results page, DLAU will display a list of Domino server versions found.
54 | This information is retrieved from the Domino Directory. It does however not check if all of the servers listed are existing and/or running at present.
55 |
56 | This limitation applies to the standalone DLAU Tool provided here, but does not apply to the integrated Domino License Dashboard which is integrated in Domino version 14.5 (and above)
--------------------------------------------------------------------------------
/docs/de-de/index.md:
--------------------------------------------------------------------------------
1 | ---
2 | layout: default
3 | title: "Home (German-Deutsch)"
4 | nav_order: 2
5 | description: "HCL Domino License Analysis Utility"
6 | has_children: true
7 | ---
8 |
9 | Sie lesen die deutsche Übersetzung [dieser Seite](../index.md)
10 |
11 | [Neueste Version Herunterladen](https://github.com/HCL-TECH-SOFTWARE/domino-license-analysis-utility-DLAU/releases/latest){: .btn .btn-green }
12 | [Auf GitHub ansehen](https://github.com/HCL-TECH-SOFTWARE/domino-license-analysis-utility-DLAU/){: .btn }
13 |
14 | 15 | Table of contents 16 |
17 | {: .text-delta } 18 | 1. TOC 19 | {:toc} 20 |HCL Domino License Analysis Utility
15 | Dieses Tool unterstützt Domino Administratoren bei der Durchführung eines Health Checks und der Ermittelung der Anzahl der Authorisierten Benutzer einer vorhandenen HCL Domino Umgebung gemäß des CCB & CCX Lizenzmodelles 16 | 17 |
18 |
25 |
26 | ## Ziel
27 |
28 | Ziel dieses Tools ist es schnell und zuverlässig die genaue Anzahl der autorisierten Benutzer einer HCL Domino Umgebung zu ermitteln welche ein Domino Administrator sonst manuell ermitteln müsste.
29 |
30 | DLAU automatisiert den Prozess der Berechung indem es die benötigten Informationen die zur Ermittelung der Benutzeranzahl erforderlich sind in kürzester Zeit einsammelt und lokal auswertet.
31 |
32 | Weitere Informationen zum Lizenzmodell sind in diesem Blogpost verfügbar:
33 | [All You Ever Wanted to Know About Domino CCB Licensing and DLAU Tool](https://blog.hcltechsw.com/domino/all-you-ever-wanted-to-know-about-domino-ccb-licensing-and-dlau-tool/)
34 |
35 | ## Einleitung
36 |
37 | {% include youtube.html id="zBPAdHMGzzo" %}
38 |
39 |
40 | ## Dokumentation
41 | Erfahren Sie mehr über das HCL Domino License Analysis Utility in folgenden Artikeln:
42 |
43 | * [Schritt für Schritt Anleitung](instructions.md)
44 | * [Ergebnisse verstehen](results.md)
45 | * [Lizenzberechnung](licensecalc.md)
46 | * [Was ist das Domino License Utility (PDF)](../../assets/pdf/what-Is-the-domino-license-analysis-utility.pdf)
47 | * [Was wird gescannt](scanning.md)
48 | * [Erklärung der Anmerkungen](observations.md)
49 | * [Fragen und Antworten](faqs.md)
50 | * [Einschränkungen](limitations.md)
51 |
52 | ## Kompatibilität
53 |
54 | Siehe [Systemanforderungen](requirements.md)
55 |
56 | ## Geschwindigkeit und Laufzeit
57 |
58 | Abhängig von der Anzahl der Personendokumente in der HCL Domino Umgebung kann der Prozess von wenigen Minuten bis zu mehreren Stunden dauern, die folgende Tabelle spiegelt unsere Erfahrungen wieder:
59 |
60 | Personendokumente | Laufzeit
61 | --- | ---
62 | 1.000 | 45 minuten
63 | 5,000 | 90 minuten
64 | 10 k | 2 Stunden
65 | 1 Millionen | 15 Stunden
66 |
67 | ## Änderungen
68 |
69 | Das Tool wird regelmäßig aktualisiert - welche Änderungen in dieser Version vorgenommen worden sind lesen sie im [CHANGE LOG](../changelog.md)
70 |
--------------------------------------------------------------------------------
/docs/roadmap.md:
--------------------------------------------------------------------------------
1 | ---
2 | layout: default
3 | title: "Roadmap"
4 | nav_order: 7
5 | description: "Roadmap"
6 | has_children: false
7 | ---
8 |
9 | 19 | Inhalt 20 |
21 | {: .text-delta } 22 | 1. TOC 23 | {:toc} 24 |Roadmap
10 | A brief description of what is planned for upcomming releases of DLAU 11 | 12 |
13 |
20 | ___
21 |
22 | ## Version 1.2.8
23 | ETA: To be defined
24 |
25 | {: .update }
26 | Remove Limitation - DNEXT-23867 Multi-Domain support. Currently only a single Domain is supported
27 |
28 | {: .new }
29 | DNEXT-23871 Include the standalone user report tool for preV12 servers
30 |
31 | {: .new }
32 | DNEXT-23858 Honor "Access Allow" groups used in the server document
33 |
34 | {: .new }
35 | [GitHub Issue #19](https://github.com/HCL-TECH-SOFTWARE/domino-license-analysis-utility-DLAU/issues/19) - DNEXT-26870 - Export functionality enhancements to rename file and add user license category to exported file
36 |
37 | {: .new }
38 | DNEXT-25788 Identify external users by using a field/property from the person document
39 |
40 | {: .new }
41 | [Idea DOMINO-I-2672](https://domino-ideas.hcltechsw.com/ideas/DOMINO-I-2672) - DNEXT-25874 Scan Deny Access groups even if they are stored in a secondary Domino directory
42 |
43 | {: .fix }
44 | DNEXT-30961 - Highest Access Level in Entitlement Tracking database not calculated
45 |
46 | ## Version 1.2.7
47 | October 2025
48 |
49 | For the full list of changes please see the [V1.2.7 changelog](https://opensource.hcltechsw.com/domino-license-analysis-utility-DLAU/changelog/#updates-included-in-v127).
50 |
51 |
52 | ## Version 1.2.6
53 | November 2024
54 |
55 | For the full list of changes please see the [V1.2.6 changelog](https://opensource.hcltechsw.com/domino-license-analysis-utility-DLAU/changelog/#updates-included-in-v126).
56 |
57 |
58 | ## Version 1.2.5
59 | October 2024
60 |
61 | For the full list of changes please see the [V1.2.5 changelog](https://opensource.hcltechsw.com/domino-license-analysis-utility-DLAU/changelog/#updates-included-in-v125).
62 |
63 | ## Version 1.2.4
64 | April 2024
65 |
66 | For the full list of changes please see the [V1.2.4 changelog](https://opensource.hcltechsw.com/domino-license-analysis-utility-DLAU/changelog/#updates-included-in-v124).
67 |
68 | ## Version 1.2.3
69 | March 2024
70 |
71 | For the full list of changes please see the [V1.2.3 changelog](https://opensource.hcltechsw.com/domino-license-analysis-utility-DLAU/changelog/#updates-included-in-v123).
72 |
73 | ## Version 1.2.2
74 | February 2024
75 |
76 | For the full list of changes please see the [V1.2.2 changelog](https://opensource.hcltechsw.com/domino-license-analysis-utility-DLAU/changelog/#updates-included-in-v122).
77 |
78 | ## Version 1.2.1
79 | November 2023
80 |
81 | For the full list of changes please see the [V1.2.1 changelog](https://opensource.hcltechsw.com/domino-license-analysis-utility-DLAU/changelog/#updates-included-in-v121).
82 |
83 |
--------------------------------------------------------------------------------
/docs/de-de/limitations.md:
--------------------------------------------------------------------------------
1 | ---
2 | layout: default
3 | title: "Einschränkungen"
4 | parent: "Home (German-Deutsch)"
5 | nav_order: 3
6 | description: "Bekannte Einschränkungen"
7 | has_children: false
8 | ---
9 |
10 | Sie lesen die deutsche Übersetzung [dieser Seite](../limitations.md)
11 |
12 | 14 | Table of contents 15 |
16 | {: .text-delta } 17 | 1. TOC 18 | {:toc} 19 |Bekannte Einschränkungen
13 | 14 | Anbei eine Liste bekannter Einschränkungen im Bezug auf DLAU. 15 | 16 |
17 |
24 |
25 | ___
26 | ## LDAP/ActiveDirectory
27 |
28 | Coming soon
29 | {: .label .label-yellow }
30 |
31 | Wenn der HCL Domino Server ein externes LDAP/Active Directory zur Authentifizerung von Web-Benutzern verwendet, kann DLAU nicht verifizieren welche Benutzer in diesem externen LDAP enthalten sind.
32 |
33 | Deshalb ist in diesem Fall u.U. eine manuelle Prüfung notwendig.
34 |
35 | {: .highlight }
36 | Aktuell arbeiten wir daran ebenfalls die LDAP / AD Verzeichnisse zu verarbeiten und mit den im License Tracking gefundenen Benutzerlisten abzugleichen.
37 |
38 | ___
39 | ## Mehrere/nicht verbundene Verzeichnisse
40 |
41 | In HCL Domino Umgebungen welche in mehrere eigenständige Domänen aufgeteilt sind bzw. in denen die Directories(Adressbücher) nicht direkt über Directory Assistance eingebunden sind wird DLAU nur die Domino Domäne analysieren die im Arbeitsumgebungsdokument ihres HCL Notes Clients definiert wurde.
42 |
43 | Um alle Domänen zu analysieren erstellen Sie bitte entsprechende Arbeitsumgebungsdokumente, d.h. eins pro Domäne und verwenden den jeweiligen Administrationsserver dieser Domäne jeweils als "Home/Mail Server".
44 |
45 | Pro Domino Domäne erstellen Sie bitte einen eigenen DLAU report, d.h. verwenden eine DLAU Instanz pro Domäne. Nur so ist es möglich die in den einzelnen Domänen gesammelten Informationen später (manuell) zusammenzuführen.
46 |
47 | Bislang ist dieser Deduplizierungsprozess (leider noch) manuell durchzuführen, um sicherzustellen, daß jeder aufgeführte Benutzer in Ihren Domino Domänen nur einmal gezählt wird.
48 |
49 | {: .note }
50 | Wir arbeiten an einer Lösung die autom. Scanns auch über Domänengrenzen hinweg ermöglicht und auch mehrere Administrationsserver unterstützt.
51 |
52 | ___
53 | ## Directory Assistance auf anderen Servern als dem Administrationserver
54 |
55 | DLAU wird nur dann nach zusätzlichen Adressbüchern/Domino Directories suchen wenn wenigstens der Domino Administrationsserver mit einer Directory Assistance DB (DA) konfiguriert wurde.
56 |
57 | Falls in Ihrer Umgebung der Adminserver tatsächlich keine Directory Assistance (DA) DB nutzen, aber ein oder mehrere Server der gleichen Domino Domäne hingegen weitere Adressbücher über DA nutzen, so wird DLAU in der aktuellen Version diese zusätzlichen Adressbücher nicht verarbeiten.
58 |
59 | {: .highlight }
60 | Note: Es handelt sich um eine bekannte Einschränkung an deren Behebung wir bereits arbeiten. Wir planen jeden Server auf die Verwendung von Directory Assistance zu prüfen.
--------------------------------------------------------------------------------
/docs/index.md:
--------------------------------------------------------------------------------
1 | ---
2 | layout: default
3 | title: "Home"
4 | nav_order: 1
5 | description: "HCL Domino License Analysis Utility"
6 | has_children: true
7 | ---
8 |
9 | [Download Latest Release](https://github.com/HCL-TECH-SOFTWARE/domino-license-analysis-utility-DLAU/releases/latest){: .btn .btn-green }
10 | [View on GitHub](https://github.com/HCL-TECH-SOFTWARE/domino-license-analysis-utility-DLAU/){: .btn }
11 |
12 | 18 | Inhalt 19 |
20 | {: .text-delta } 21 | 1. TOC 22 | {:toc} 23 |HCL Domino License Analysis Utility
13 | This utility will assist HCL Domino Administrators in doing a health check based on deployment best practices and determining the Authorized User Count within an HCL Domino environment according to the CCB & CCX license model. 14 | 15 |
16 |
23 | ___
24 | ## Purpose
25 |
26 | The purpose of this utility is to provide fast and accurate Authorized User counts for HCL Domino environments by aggregating information that a Domino Administrator would otherwise have to collect manually. It automates the process by aggregating all the information that is needed to accurately determine the Authorized User counts in a fraction of the time.
27 |
28 | For more information, please refer this HCL Blog Post:
29 | [All You Ever Wanted to Know About Domino CCB Licensing and DLAU Tool](https://www.hcl-software.com/blog/domino/all-you-ever-wanted-to-know-about-domino-ccb-licensing-and-dlau-tool/)
30 |
31 | ## When to use
32 |
33 | The HCL Domino License Analysis Utility (DLAU) should be used in environments where at least one of the HCL Domino Servers is running on a version lower than 14.5. If all of your Domino Servers are running version 14.5 (or above), you should use the integrated Domino License Dashboard which also produces a DLAU report in exactly the same format.
34 |
35 | ## Intro
36 |
37 | {% include youtube.html id="zBPAdHMGzzo" %}
38 |
39 |
40 | ## Documentation
41 | Learn how to use the HCL Domino License Analysis Utility with these topics:
42 |
43 | * [Step-by-Step Instructions](instructions.md)
44 | * [Understanding the Results](results.md)
45 | * [How Licenses Are Calculated](licensecalc.md)
46 | * [What is the Domino License Utility (PDF)](assets/pdf/what-Is-the-domino-license-analysis-utility.pdf)
47 | * [What Is Scanned](scanning.md)
48 | * [Explanation of Observations](observations.md)
49 | * [Frequently Asked Questions](faqs.md)
50 | * [Limitations](limitations.md)
51 |
52 | ## Compatibilty
53 |
54 | see [system requirements](requirements.md)
55 | ## Performance & Runtime
56 |
57 | Depending on the number of Person documents within a HCL Domino environment, the entire process can take anywhere from 45 minutes to 4 hours on average.
58 |
59 | Person Docs | Expected runtime
60 | --- | ---
61 | 1.000 | 45 minutes
62 | 5,000 | 90 minutes
63 | 10 k | 2 hours
64 | 1 Million | 15 hours
65 |
66 | ## Changes
67 |
68 | Be sure to review the changes that are included in this release by opening the [CHANGE LOG](changelog.md)
69 |
--------------------------------------------------------------------------------
/docs/de-de/requirements.md:
--------------------------------------------------------------------------------
1 | ---
2 | layout: default
3 | title: "Voraussetzungen"
4 | parent: "Home (German-Deutsch)"
5 | nav_order: 1
6 | description: "Systemanforderungen"
7 | has_children: false
8 | ---
9 |
10 | 17 | Table of contents 18 |
19 | {: .text-delta } 20 | 1. TOC 21 | {:toc} 22 |Systemanforderungen
11 | Die folgenden Voraussetzungen müssen erfüllt sein, um das Programm ausführen zu können. 12 | 13 |
14 |
21 |
22 | ---
23 |
24 | ## Software
25 |
26 | - Windows 7 oder höher
27 | - Notes Client Version 7.0.2 oder höher
28 | - Domino Server Version 7.0 oder höher
29 |
30 | ## Zugriffsrechte
31 |
32 | - READ-Zugriff auf das Domino-Verzeichnis und andere Systemdatenbanken
33 | - ACL-Rolle "[DenyAccessRead]" im Domino-Verzeichnis
34 | - Gruppenmitgliedschaft in der Gruppe "LocalDomainAdmins".
35 |
36 | ## JavaScript-Unterstützung in den Notes-Client-Voreinstellungen
37 |
38 | DLAU verwendet JavaScript für einige der internen Abläufe, deshalb ist es notwendig die Ausführung von JavaScript im Notes Client zu gestatten. Wenn die Verwendung von JavaScript im Notes Client nicht aktiviert ist wird DLAU nicht funktionieren.
39 |
40 | JavaScript kann im Notes Client wie folgt aktiviert werden:
41 | Im Notes Client, wählen Sie im Menü "Datei" den Punkt "Einstellungen" und aktivieren die folgenden drei (3) Optionen:
42 |
43 | 
44 |
45 |
46 | ## Weitere Anforderungen für CCX/Known Guest Berechnung
47 |
48 | Um CCX und Bekannte Gäste in einer Domino-Umgebung richtig berechnen zu können, müssen zusätzliche Informationen an DLAU zur Analyse übermittelt werden.Für CCX-Benutzer gelten bestimmte Regeln, die beachtet werden müssen. Insbesondere darf ein CCX-Benutzer nur eine maximale Zugriffskontrolllistenstufe von "Autor" für alle Domino-Anwendungen haben. DLAU verwendet auch Informationen über die letzte erfolgreiche Anmeldung des CCX-Benutzers bei einem Domino-Server, um zu berechnen, ob der CCX-Benutzer aktiv oder inaktiv ist.
49 |
50 | In ähnlicher Weise darf ein Bekannter Gast nur eine maximale Zugriffskontrolllistenstufe von "Leser" für alle Domino-Anwendungen haben.
51 |
52 | Um die Informationen bereitzustellen, die DLAU für diese Berechnungen benötigt, müssen zwei zusätzliche Systeme in Ihrer Domino-Serverumgebung laufen:
53 |
54 | * Lizenzverfolgungssystem: Dieses System ist seit Version 7.0 in Domino integriert und erfasst das Datum, die Uhrzeit und das Protokoll, das verwendet wurde, wenn sich ein Benutzer bei Domino authentifiziert.
55 |
56 | [License Tracking System Konfigurationsanleitung](https://help.hcltechsw.com/domino/9.0.1/admin/admin/conf_licensetracking_t.html)
57 |
58 | * Entitlement Tracking (wenn Domino V12) oder die Ergebnisse des User Report Tools: Diese Systeme versorgen DLAU mit der höchsten Zugriffskontrolllistenstufe jedes Domino-Benutzers. Dies ist nur wichtig, wenn der Client über externe Benutzer (CCX-Lizenzen) verfügt.
59 |
60 | [Weitere Informationen](https://opensource.hcltechsw.com/domino-license-analysis-utility-DLAU/instructions/#schritt-6---entitlement-tracking--user-report-tool-scan)
61 |
--------------------------------------------------------------------------------
/docs/requirements.md:
--------------------------------------------------------------------------------
1 | ---
2 | layout: default
3 | title: "Requirements"
4 | parent: "Home"
5 | nav_order: 3
6 | description: "System Requirements"
7 | has_children: false
8 | ---
9 |
10 | 15 | Inhalt 16 |
17 | {: .text-delta } 18 | 1. TOC 19 | {:toc} 20 |System Requirements
11 | The following requirements must be met in order to run the utility. 12 | 13 |
14 |
21 |
22 | ---
23 |
24 | ## Software
25 |
26 | - Windows 7 or higher
27 | - Notes Client version 7.0.2 or higher
28 | - Domino Server version 7.0 or higher
29 |
30 | ## Access rights
31 |
32 | - READ access to the Domino Directory and other system databases1
33 | - ACL role "[GroupModifier]" in the Domino Directory
34 | - Group membership in the "LocalDomainAdmins" Group or at least reader access to the other system databases1
35 |
36 | 1 - The list of applications the user needs access to are:
37 | - entitlements.nsf
38 | - userlicenses.nsf
39 | - names.nsf
40 | - log.nsf
41 | - Any directory assistance application in use as well as the associated directories
42 |
43 | ## JavaScript Support in Notes Client Preferences
44 |
45 | We use JavaScript within DLAU to move through the different scan processes, therefore JavaScript support must be enabled.
46 |
47 | If JavaScript is not enabled for the Notes Client, DLAU will not work.
48 |
49 | In the Notes Client, this can be enabled by opening the Notes Client Preferences (from the Notes Client Menu, select "File -> Preferences...") and then enabling three (3) JavaScript options, as shown below:
50 |
51 | 
52 |
53 |
54 | ## Additional Requirements for CCX/Known Guest Calculations
55 |
56 | In order to properly calculate CCX and Known guests in a Domino environment, additional information must be provided to DLAU for analysis.
57 |
58 | CCX users have certain rules that must be adhered to. Specifically, a CCX User is only allowed to have a maximum Access Control List level of "Author" to all the Domino applications. DLAU also uses information about the CCX Users' last successful login to a Domino server to calculate if the CCX user is Active or Inactive.
59 |
60 | Similarly, a Known Guest is only allowed to have a maximum Access Control List level of "Reader" to all the Domino applications.
61 |
62 | To provide the information that DLAU requires to make these calculations, two additional systems must be running in your Domino server environment:
63 |
64 | * License Tracking System: this is a system that is built into Domino (since V7 I believe) that captures the date, time, and protocol that was used when a user authenticates to Domino
65 |
66 | [License Tracking System Setup Instructions](https://help.hcltechsw.com/domino/9.0.1/admin/admin/conf_licensetracking_t.html)
67 |
68 | * Entitlement Tracking (if Domino V12) or the results from the user Report Tool: These systems will provide DLAU with each Domino user's highest Access Control List level. This is important only if the client has External Users (CCX licenses)
69 |
70 | [Click here for more information](https://opensource.hcltechsw.com/domino-license-analysis-utility-DLAU/instructions/#step-6---entitlement-tracking--user-report-tool-scan)
71 |
--------------------------------------------------------------------------------
/docs/reporting.md:
--------------------------------------------------------------------------------
1 | ---
2 | layout: default
3 | title: "Reporting Results"
4 | parent: "Home"
5 | nav_order: 4
6 | description: "How to report the results to HCL"
7 | has_children: false
8 | has_toc: true
9 | ---
10 |
11 | 15 | Table of contents 16 |
17 | {: .text-delta } 18 | 1. TOC 19 | {:toc} 20 |Reporting the Results of the HCL Domino License Analysis Utility
12 | 13 |
14 |
21 |
22 | ___
23 | Once you are satisfied with the results of the DLAU Scans, you will need to report the results to HCL for future licensing discussions.
24 |
25 | Within the DLAU there are two methods for submitting the information. Below are the instructions for submitting the results.
26 |
27 | ___
28 | ## Step 1 - Provide Additional Company Information
29 | In order for our HCL Sales Team to be able to contact your organization, you will need to provide information that will assist them in contacting you.
30 |
31 | On the "Scan Results" screen, there will be a button labeled "View Report", as shown in the image below:
32 |
33 | 
34 |
35 | When that button is clicked for the first time after the scanning process is completed, the user will be presented with a dialog box where they can provide information about their organization, as shown in the image below:
36 |
37 | 
38 |
39 | At a minimum, you will need to provide your Company Name and HCL Account #. For a faster response from HCL, you can also provide your Name, Email Address and Direct Phone #. These three (3) values are optional.
40 |
41 | Once the information is provided, click on the "OK" button to be taken to the "Scan Results" page.
42 |
43 | ___
44 | ## Step 2 - Understanding the Scan Report
45 | Once you supply your organization's information, you will be presented with the "Your License Information" Report page.
46 |
47 | On this page will be a summary of the License Counts and Company Information provided on the left side of the screen. This is a representation of the "Scan Results" page.
48 |
49 | On the right side of the page are instructions on how to provide these results to HCL.
50 |
51 | Below is an image of what you should see:
52 | 
53 |
54 | ___
55 | ## Step 3 - Submitting the Scan Report
56 | There are two (2) methods for providing these results to HCL:
57 |
58 | ___
59 | ### Option A: Send Via Email
60 | The most efficient and fastest method to provide your License Information to HCL is to submit it as an email.
61 |
62 | When you click on the "Submit Report" button, the information that is shown on the current page is placed into the Body of a new Email message. The "Send To" and "Subject" values are also set.
63 |
64 | When you are ready, simply send the Email message to HCL.
65 |
66 | Below is an example of what the Email message will look like:
67 | 
68 |
69 | {: .notice }
70 | This method CANNOT be used by U.S. Federal Government customers. If you are a U.S. Federal Government customer, please refer to the next submission option.
71 |
72 | ___
73 | ### Option B: Send as PDF
74 | A second option for submitting your License Information is to provide the results as a PDF file. To use this option, click on the "Print Report" button. This will invoke the Print Document functionality in the Notes Client.
75 |
76 | When the "Print Document" dialog is displayed, be sure to select a PDF Rendering printer from the list provided, as shown below:
77 |
78 | 
79 |
80 | Once the PDF of the report has been created, it can be provided to your HCL Sales Representative directly.
81 |
82 | {: mx-auto }
--------------------------------------------------------------------------------
/docs/faqs.md:
--------------------------------------------------------------------------------
1 | ---
2 | layout: default
3 | title: "FAQ"
4 | nav_order: 9
5 | description: "Frequently Asked Questions"
6 | parent: "Home"
7 | has_children: false
8 | ---
9 | 15 | Table of contents 16 |
17 | {: .text-delta } 18 | 1. TOC 19 | {:toc} 20 |Frequently Asked Questions
10 | 11 |
12 |
19 |
20 |
21 | ### Do I need to change the configuration of my HCL Domino servers?
22 |
23 | No. This utility does not require any additional functionality to be added to ANY HCL Domino servers. It runs completely on the local drive of the HCL Domino Administrator who is running the utility. For the tool to function properly your environment needs to be in line with the [System Requirements](requirements.md)
24 |
25 | ### Is this a Licensing Audit? Will I need to involve our legal / compliance team(s)?
26 |
27 | It is important to note that DLAU is not conducting a license audit, which is always an in-depth hindsight analysis. Instead, DLAU is creating a baseline to help you and HCLSoftware have a meaningful forward-looking conversation for your renewal or restart or move to CCB or Volt MX Go. The baseline must be augmented by the customer in terms of future deployment plans as the customer is continually responsible for license compliance going forward.
28 |
29 | ### Will the process block my Notes Client?
30 |
31 | The scans within the utility run in a background task. The user’s Notes Client can be used as normal during the scanning processes. The user only needs to “check in” periodically to see if the current scan is complete and to progress to the next scan.
32 |
33 | ### How long will the process take?
34 |
35 | It depends, typically it should take 1 to 3+ hours, depending on the number of Person documents and HCL Domino servers in the environment. For example, a small deployment (~200 users) will take 45 minutes, medium deployments (~5000 users) will take under 2 hours.
36 | Further reference information on how long the process may take on the [home page](index.md#performance--runtime) of this project
37 |
38 | ### How do I see scanning updates in the status bar?
39 |
40 | Set *DLAU_VERBOSE_MODE=1* in your Notes.INI, restart the Notes client, then begin the scan. While the scan is taking place you will now see additional output in the Notes Client's status bar including a time stamp to help ensure you that progress is continuing. As of DLAU 1.2.2 the additional output will also appear in the scan log.
41 |
42 | ### How can I substantiate needed entitlements?
43 |
44 | Within the “Scan Results” page, there is a button labeled “View Printable Result”. When that is clicked, you will be presented with a printable report that you can share with HCL as a PDF (Print to PDF) if needed for renewal discussions. The data contained in this PDF is in line with our [privacy statement](privacy.md)
45 |
46 | ### How accurate are the results of the scans?
47 |
48 | While this is not an audit tool, it usually provides accurate information of your current environment. If you have any doubts of the report being incorrect, please reach out to your HCL representative or [report an issue](issues.md).
49 | Statistically, our early adopters of the utility are reporting a 96% accuracy. The 4% generally are seen to be special Administration or Design Signing users.
50 |
51 | add new FAQ about CCB / CCX calculations and then link to the June 29 Blog Post
52 |
53 | ### What is the difference between CCB and CCX Licenses?
54 |
55 | For more information on the differences between CCB and CCX licenses, please refer this HCL Blog Post:
56 | [All You Ever Wanted to Know About Domino CCB Licensing and DLAU Tool](https://blog.hcltechsw.com/domino/all-you-ever-wanted-to-know-about-domino-ccb-licensing-and-dlau-tool/?referrer=opensource.hcltechsw.com/domino-license-analysis-utility-DLAU/)
--------------------------------------------------------------------------------
/docs/de-de/faq.md:
--------------------------------------------------------------------------------
1 | ---
2 | layout: default
3 | title: "Fragen & Antworten"
4 | nav_order: 9
5 | description: "Fragen und Antworten"
6 | parent: "Home (German-Deutsch)"
7 | has_children: false
8 | ---
9 |
10 | Sie lesen die deutsche Übersetzung [dieser Seite](../faq.md)
11 |
12 | 13 | Table of contents 14 |
15 | {: .text-delta } 16 | 1. TOC 17 | {:toc} 18 |Fragen und Antworten
13 | 14 |
15 |
22 |
23 | ---
24 |
25 | ### Muss ich die Konfiguration meiner HCL Domino-Server ändern?
26 | Nein. Dieses Dienstprogramm erfordert keine zusätzlichen Funktionen auf irgendwelchen HCL Domino-Servern. Es läuft vollständig auf dem lokalen Laufwerk des HCL Domino-Administrators, der das Dienstprogramm ausführt. Damit das Tool ordnungsgemäß funktioniert, muss Ihre Umgebung mit den [Systemanforderungen](requirements.md) übereinstimmen.
27 |
28 | ---
29 |
30 | ### Handelt es sich um eine Lizenzierungsprüfung? Muss ich unser(e) Rechts-/Compliance-Team(s) einbeziehen?
31 | Es ist wichtig zu wissen, dass DLAU kein Lizenz-Audit durchführt, bei dem es sich immer um eine eingehende Analyse im Nachhinein handelt. Stattdessen erstellt das DLAU eine Baseline, die Ihnen und HCLSoftware hilft, ein sinnvolles, zukunftsorientiertes Gespräch für Ihre Erneuerung oder Ihren Neustart oder den Wechsel zu CCB oder Volt MX Go zu führen. Die Baseline muss vom Kunden im Hinblick auf zukünftige Einsatzpläne ergänzt werden, da der Kunde kontinuierlich für die Einhaltung der Lizenzbestimmungen verantwortlich ist.
32 |
33 | ---
34 |
35 | ### Wird der Prozess meinen Notes Client blockieren?
36 | Die Scans innerhalb des Dienstprogramms laufen in einer Hintergrundaufgabe. Der Notes-Client des Benutzers kann während des Scanvorgangs wie gewohnt verwendet werden. Der Benutzer muss nur regelmäßig "einchecken", um zu sehen, ob der aktuelle Scan abgeschlossen ist und um zum nächsten Scan überzugehen.
37 |
38 | ---
39 |
40 | ### Wie lange wird der Prozess dauern?
41 | Je nach Anzahl der Personendokumente und HCL-Domino-Server in der Umgebung sollte es 1 bis 3+ Stunden dauern. In einer kleinen Umgebung (~200 Benutzer) dauert der Scan ca. 45 Minuten, bei mittelgroßen Umgebungen (~5000 Benutzer) sollte ein Scann weniger als 2 Stunden dauern.
42 |
43 | Weitere Informationen darüber, wie lange der Prozess dauern kann, finden Sie auf der [Homepage](index.md#geschwindigkeit-und-laufzeit) dieses Projekts
44 |
45 | ---
46 |
47 | ### Wie kann ich die benötigten Lizenzen nachweisen?
48 | Auf der Seite "Scan-Ergebnisse" gibt es eine Schaltfläche mit der Bezeichnung "Druckfähiges Ergebnis anzeigen". Wenn Sie auf diese Schaltfläche klicken, erhalten Sie einen druckbaren Bericht, den Sie HCL als PDF (Print to PDF) zur Verfügung stellen können, falls Sie ihn für Gespräche über Ihre Lizensierung benötigen. Die in diesem PDF enthaltenen Daten stehen im Einklang mit unserer [Datenschutzerklärung](privacy.md)
49 |
50 | ---
51 |
52 | ### Wie genau sind die Ergebnisse der Scans?
53 | Obwohl es sich nicht um ein Audit-Tool handelt, liefert es in der Regel genaue Informationen über Ihre aktuelle Umgebung. Wenn Sie Zweifel haben, dass der Bericht nicht korrekt ist, wenden Sie sich bitte an Ihren HCL-Vertreter oder [melden ein Problem](issues.md).
54 |
55 | Statistisch gesehen berichten Kunden von einer Genauigkeit von 96 %. Bei den 4 % handelt es sich im Allgemeinen um Sonderfälle wie spezielle Verwaltungs- oder Design Signing-Benutzer.
56 |
57 | Fügen Sie eine neue FAQ über CCB-/CCX-Berechnungen hinzu und verlinken Sie dann auf den Blogbeitrag vom 29. Juni
58 |
59 | ---
60 |
61 | ### Was ist der Unterschied zwischen CCB- und CCX-Lizenzen?
62 | Weitere Informationen zu den Unterschieden zwischen CCB- und CCX-Lizenzen finden Sie in dem HCL Blog Post:
63 |
64 | [Alles, was Sie schon immer über die CCB-Lizenzierung von Domino und das DLAU-Tool wissen wollten](https://blog.hcltechsw.com/domino/all-you-ever-wanted-to-know-about-domino-ccb-licensing-and-dlau-tool/?referrer=opensource.hcltechsw.com/domino-license-analysis-utility-DLAU/)
--------------------------------------------------------------------------------
/CODE_OF_CONDUCT.md:
--------------------------------------------------------------------------------
1 | # Contributor Covenant Code of Conduct
2 |
3 | Projects should foster a positive environment, to ensure active and pleasant participation for all. This is wording for a contributor covenant, amended from [Contributor Covenant 2.0](https://www.contributor-covenant.org/version/2/0/code_of_conduct/).
4 |
5 | ## Our Pledge
6 |
7 | We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation.
8 |
9 | We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.
10 |
11 | ## Our Standards
12 |
13 | Examples of behavior that contributes to a positive environment for our community include:
14 |
15 | -> Demonstrating empathy and kindness toward other people
16 | - Being respectful of differing opinions, viewpoints, and experiences
17 | - Giving and gracefully accepting constructive feedback
18 | - Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience
19 | - Focusing on what is best not just for us as individuals, but for the overall community
20 |
21 | Examples of unacceptable behavior include:
22 |
23 | - The use of sexualized language or imagery, and sexual attention or advances of any kind
24 | - Trolling, insulting or derogatory comments, and personal or political attacks
25 | - Public or private harassment
26 | - Publishing others’ private information, such as a physical or email address, without their explicit permission
27 | - Other conduct which could reasonably be considered inappropriate in a professional setting
28 |
29 | ## Enforcement Responsibilities
30 |
31 | Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful.
32 |
33 | Community leaders have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, and will communicate reasons for moderation decisions when appropriate.
34 |
35 | ## Scope
36 |
37 | This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public spaces. Examples of representing our community include using an official e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event.
38 |
39 | ## Enforcement
40 |
41 | Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the HCL Open Source Project Officer, who is responsible for enforcement, at [ospo.hclsoftware@hcl.com](mailto:ospo.hclsoftware@hcl.com). All complaints will be reviewed and investigated promptly and fairly. The HCL Open Source Project Office is obligated to respect the privacy and security of the reporter of any incident. Details of enforcement policies may be posted separately.
42 |
43 | Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by the HCL Open Source Project Office.
44 |
45 | ## Attribution
46 |
47 | This Code of Conduct is adapted from the Contributor Covenant, version 2.0, available at https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
48 |
49 | Community Impact Guidelines were inspired by Mozilla’s code of conduct enforcement ladder.
50 |
51 | For answers to common questions about this code of conduct, see the FAQ at https://www.contributor-covenant.org/faq.
52 |
--------------------------------------------------------------------------------
/docs/scanning.md:
--------------------------------------------------------------------------------
1 | ---
2 | layout: default
3 | title: "What is scanned"
4 | parent: "Home"
5 | nav_order: 5
6 | description: "What is being scanned?"
7 | has_children: false
8 | ---
9 |
10 | 16 | Inhalt 17 |
18 | {: .text-delta } 19 | 1. TOC 20 | {:toc} 21 |What is being scanned?
11 | Below is a description of what is scanned by the HCL Domino License Analysis Utility 12 | 13 |
14 |
21 |
22 | ___
23 | ## Scan #1: HCL Domino Server Environment
24 |
25 | The first scan that occurs goes through the HCL Domino server environment. This scan collects all the information about the HCL Domino servers, including the following:
26 |
27 | - Discovery of Domino Administration server
28 | - Domino server names
29 | - Domino Server availability (Online or Offline)
30 | - Directory Assistance (DA) Usage
31 | - If DA is in use, discover all additional Domino Directories
32 | - Check for secured HTTP and LDAP protocols
33 | - Capture the name(s) of the Deny Access Groups that are in use on the Domino servers
34 | - Determine if Domino V12 is in use and, if it is, list which Domino servers are using the Entitlement Tracking system
35 | - Determine if Domino License Tracking system is running and on which Domino servers
36 |
37 | ___
38 | ## Scan #2: HCL Domino Users
39 |
40 | The second scan that occurs goes through all Domino Directories and aggregates information from the Person documents it finds.
41 |
42 | the information that is aggregates is as follows:
43 |
44 | - User's name
45 | - User's Email address
46 | - Notes Certificate Expiry Date (if available)
47 | - Indication if the Internet Password is set (not the actual Internet Password)
48 | - Domino directory where the Person document resides
49 | - Date when user last accessed a Domino Server (only if License Tracking is enabled)
50 | - Protocols that the user's used to access the Domino servers (only if License Tracking is enabled)
51 |
52 | Additional information is aggregated about each user during the subsequent scans.
53 | Please note that all this information is kept locally on your computer only. For more information see [our privacy statement](privacy.md)
54 |
55 | ___
56 | ## Scan #3: Deny Access Groups and User Membership
57 |
58 | The third scan that occurs looks at the values stored on the Server document aggregated data to determine what Deny Access Groups are in use to secure the Domino servers.
59 |
60 | Using the list of Deny Access Groups that are in use, the scan will retrieve the Deny Access Groups, all members of those Groups and also determine if there are Group names within the Deny Access Groups. If additional Group names are discovered, the scan will also retrieve the information for those additional Groups. This recursive scanning of Groups will continue until all Group names have been processed.
61 |
62 | Once all this information is retrieved, each of the users that were discovered during the second scan are crossed referenced against the Members of the Deny Access Groups that were discovered. This cross reference determines if the user is listed in a Deny Access Group. If a user's name is discovered, the User information will be updated to indicate this.
63 |
64 | ___
65 | ## Scan #4: Entitlement Tracking / User Report Tool Results
66 |
67 | The third scan that occurs looks at one of two different systems:
68 |
69 | 1. Entitlement Tracking: this is a new system that was introduced in HCL Domino V12. If the client is using HCL Domino V12, this scan will always occur
70 | 2. User Report Tool Results: this is an optional system that is based on the Entitlement Tracking system that is in HCL domino V12, but has been made to be backwards compatible to Domino V9.x. Customers will need to download and run the [User Report Tool](https://support.hcltechsw.com/csm?id=kb_article&sysparm_article=KB0095328) prior to using the DLAU.
71 |
72 |
73 | The information that this scan retrieves will display the user's highest Access Control List level that each user has to the HCL Domino environment. This is useful in determining if the user is a CCB or a CCX license user.
--------------------------------------------------------------------------------
/docs/de-de/scanning.md:
--------------------------------------------------------------------------------
1 | ---
2 | layout: default
3 | title: "Was wird geprüft"
4 | parent: "Home (German-Deutsch)"
5 | nav_order: 5
6 | description: "Was wird geprüft?"
7 | has_children: false
8 | ---
9 |
10 | Sie lesen die deutsche Übersetzung [dieser Seite](../scanning.md)
11 |
12 | 15 | Table of contents 16 |
17 | {: .text-delta } 18 | 1. TOC 19 | {:toc} 20 |Was wird geprüft?
13 | Im Folgenden wird beschrieben, was mit dem HCL Domino License Analysis Utility geprüft wird 14 | 15 |
16 |
23 |
24 | ___
25 | ## Scan #1: HCL Domino Server Environment
26 |
27 | Der erste Scan, der durchgeführt wird, betrifft die HCL Domino-Serverumgebung. Bei diesem Scan werden die folgenden Informationen über die HCL-Domino-Server gesammelt:
28 |
29 | - Erkennung des Domino-Adminservers
30 | - Namen aller Domino-Server
31 | - Verfügbarkeit der Domino-Servers (Online oder Offline)
32 | - Directory Assistance (DA)-Nutzung
33 | - Wenn DA in Gebrauch ist, werden alle zusätzlichen Domino-Verzeichnisse ermittelt.
34 | - Prüfung auf gesicherte HTTP- und LDAP-Protokolle
35 | - Erfassen der Namen der Deny Access Groups, die auf den Domino Servern verwendet werden
36 | - Feststellen, ob Domino V12 verwendet wird, und wenn ja, auflisten, welche Domino-Server das Entitlement Tracking System verwenden
37 | - Stellen Sie fest, ob das Domino-Lizenzverfolgungssystem läuft und auf welchen Domino-Servern
38 |
39 | ___
40 | ## Scan #2: HCL Domino Users
41 |
42 | Der zweite Scan durchläuft alle Domino-Verzeichnisse und sammelt Informationen aus den gefundenen Personendokumenten.
43 |
44 | Die aggregierten Informationen sind wie folgt:
45 |
46 | - Name des Benutzers
47 | - E-Mail Adresse des Benutzers
48 | - Anmerkungen Ablaufdatum des Zertifikats (falls verfügbar)
49 | - Angabe, ob das Internet-Passwort gesetzt ist (nicht das tatsächliche Internet-Passwort)
50 | - Domino-Verzeichnis, in dem sich das Personendokument befindet
51 | - Datum, an dem der Benutzer zuletzt auf einen Domino Server zugegriffen hat (nur wenn die Lizenzverfolgung aktiviert ist)
52 | - Netzwerkprotokolle, die der Benutzer für den Zugriff auf die Domino-Server verwendet hat (nur wenn die Lizenzverfolgung aktiviert ist)
53 |
54 | Bei den nachfolgenden Scans werden zusätzliche Informationen über jeden Benutzer gesammelt.
55 |
56 | Bitte beachten Sie, dass alle diese Informationen nur lokal auf Ihrem Computer gespeichert werden. Für weitere Informationen siehe [Datenschutz](privacy.md)
57 |
58 | ___
59 | ## Scan #3: Deny Access Groups und Gruppenstruktur
60 |
61 | Bei der dritten Überprüfung werden die auf dem Serverdokument gespeicherten Werte untersucht, um festzustellen, welche Zugriffsverweigerungsgruppen zur Sicherung der Domino-Server verwendet werden.
62 |
63 | Anhand der Liste der verwendeten Zugriffsverweigerungsgruppen ruft der Scan die Zugriffsverweigerungsgruppen und alle Mitglieder dieser Gruppen ab und stellt fest, ob es Gruppennamen innerhalb der Zugriffsverweigerungsgruppen gibt. Wenn zusätzliche Gruppennamen entdeckt werden, ruft der Scan auch die Informationen für diese zusätzlichen Gruppen ab. Dieses rekursive Scannen von Gruppen wird fortgesetzt, bis alle Gruppennamen verarbeitet worden sind.
64 |
65 | Sobald all diese Informationen abgerufen wurden, werden alle Benutzer, die während des zweiten Scans entdeckt wurden, mit den Mitgliedern der gefundenen Zugriffsverweigerungsgruppen abgeglichen. Durch diesen Querverweis wird festgestellt, ob der Benutzer in einer Deny Access Group aufgeführt ist. Wenn der Name eines Benutzers gefunden wird, werden die Benutzerinformationen entsprechend aktualisiert.
66 |
67 | ___
68 | ## Scan #4: Entitlement Tracking / User Report Tool Ergebnisse
69 |
70 | Bei der dritten Überprüfung wird eines von zwei verschiedenen Systemen untersucht:
71 |
72 | 1. Entitlement Tracking: Dies ist ein neues System, das in HCL Domino V12 eingeführt wurde. Wenn der Client HCL Domino V12 verwendet, wird dieser Scan immer durchgeführt.
73 | 2. User Report Tool Results: Hierbei handelt es sich um ein optionales System, das auf dem in HCL Domino V12 enthaltenen Entitlement Tracking-System basiert, aber rückwärtskompatibel zu Domino V9.x ist. Verwenden Sie [User Report Tool](https://support.hcltechsw.com/csm?id=kb_article&sysparm_article=KB0095328) _bevor_ Sie DLAU nutzen.
74 |
75 |
76 | Die Informationen, die dieser Scan abruft, zeigen die höchste Zugriffskontrolllistenstufe des Benutzers an, die jeder Benutzer in der HCL-Domino-Umgebung hat. Dies ist nützlich, um festzustellen, ob es sich bei dem Benutzer um einen CCB- oder CCX-Lizenzbenutzer handelt.
--------------------------------------------------------------------------------
/docs/_config.yml:
--------------------------------------------------------------------------------
1 | # Site settings
2 | theme: jekyll-theme-minimal
3 | remote_theme: pmarsceill/just-the-docs
4 | title: HCL Domino License Analysis Utility
5 | description: The HCL Domino License Analysis Utility
6 | version: 1.0
7 |
8 | git_url: "https://github.com/HCL-TECH-SOFTWARE/domino-license-analysis-utility-DLAU"
9 | baseurl: "/domino-license-analysis-utility-DLAU"
10 | permalink: pretty
11 | exclude:
12 | [
13 | "*.gemspec",
14 | "*.gem",
15 | "Gemfile",
16 | "Gemfile.lock",
17 | "lib/",
18 | "bin/",
19 | "README.md",
20 | "Rakefile",
21 | ]
22 |
23 | # Set a path/url to a logo that will be displayed instead of the title
24 | logo: "/assets/images/svg/Domino.svg"
25 | favicon_ico: "/assets/images/favicon.ico"
26 |
27 |
28 | # Enable or disable the site search
29 | # Supports true (default) or false
30 | search_enabled: true
31 | search:
32 | # Split pages into sections that can be searched individually
33 | # Supports 1 - 6, default: 2
34 | heading_level: 2
35 | # Maximum amount of previews per search result
36 | # Default: 3
37 | previews: 5
38 | # Maximum amount of words to display before a matched word in the preview
39 | # Default: 5
40 | preview_words_before: 10
41 | # Maximum amount of words to display after a matched word in the preview
42 | # Default: 10
43 | preview_words_after: 10
44 | # Set the search token separator
45 | # Default: /[\s\-/]+/
46 | # Example: enable support for hyphenated search words
47 | tokenizer_separator: /[\s/]+/
48 | # Display the relative url in search results
49 | # Supports true (default) or false
50 | rel_url: true
51 | # Enable or disable the search button that appears in the bottom right corner of every page
52 | # Supports true or false (default)
53 | button: false
54 |
55 | # Enable or disable heading anchors
56 | heading_anchors: true
57 |
58 | # Aux links for the upper right navigation
59 | #aux_links:
60 | # "This sample on Github":
61 | # - "https://github.com/"
62 |
63 | aux_links:
64 | "Download":
65 | - "https://github.com/HCL-TECH-SOFTWARE/domino-license-analysis-utility-DLAU/releases/latest"
66 |
67 | # Makes Aux links open in a new tab. Default is false
68 | aux_links_new_tab: true
69 |
70 | # Sort order for navigation links
71 | # nav_sort: case_insensitive # default, equivalent to nil
72 | nav_sort: case_insensitive # Capital letters sorted before lowercase
73 |
74 |
75 | callouts:
76 | fix:
77 | title: Bugfix
78 | color: yellow
79 | update:
80 | title: Update
81 | color: blue
82 | new:
83 | title: New
84 | color: green
85 | notice:
86 | title: Special Notice
87 | color: red
88 |
89 | # Footer content
90 | # appears at the bottom of every page's main content
91 |
92 | # Back to top link
93 | back_to_top: true
94 | back_to_top_text: "Back to top"
95 |
96 | next_page: true
97 |
98 | footer_content: "Copyright © 2023 HCLSoftware. Distributed as Apache 2.0 license."
99 |
100 | # Footer last edited timestamp
101 | # last_edit_timestamp: true # show or hide edit time - page must have `last_modified_date` defined in the frontmatter
102 | # last_edit_time_format: "%b %e %Y at %I:%M %p" # uses ruby's time format: https://ruby-doc.org/stdlib-2.7.0/libdoc/time/rdoc/Time.html
103 |
104 | # Footer "Edit this page on GitHub" link text
105 | gh_edit_link: true # show or hide edit this page link
106 | gh_edit_link_text: "Edit this page on GitHub"
107 | # the github URL for your repo
108 | gh_edit_repository: "https://github.com/HCL-TECH-SOFTWARE/domino-license-analysis-utility-DLAU"
109 | gh_edit_branch: "main" # the branch that your docs is served from
110 | gh_edit_source: docs # the source that your files originate from
111 | gh_edit_view_mode: "tree" # "tree" or "edit" if you want the user to jump into the editor immediately
112 |
113 | # Color scheme currently only supports "dark", "light"/nil (default), or a custom scheme that you define
114 | color_scheme: nil
115 |
116 | # Google Analytics Tracking (optional)
117 | # e.g, UA-1234567-89
118 | # ga_tracking: - removed on purpose
119 |
120 | plugins:
121 | - jekyll-seo-tag
122 |
123 | highlighter: rouge
124 |
125 | kramdown:
126 | input: GFM
127 | syntax_highlighter: rouge
128 | # syntax_highlighter_opts:
129 | # block:
130 | # line_numbers: true
131 | # compress_html:
132 | # clippings: all
133 | # comments: all
134 | # endings: all
135 | # startings: []
136 | # blanklines: false
137 | # profile: false
138 | # # ignore:
139 | # # envs: all
140 |
--------------------------------------------------------------------------------
/docs/assets/images/svg/Domino.svg:
--------------------------------------------------------------------------------
1 |
--------------------------------------------------------------------------------
/docs/observations.md:
--------------------------------------------------------------------------------
1 | ---
2 | layout: default
3 | title: "Observations"
4 | parent: "Home"
5 | nav_order: 6
6 | description: "Observations Explained"
7 | has_children: false
8 | ---
9 |
10 | 17 | Inhalt 18 |
19 | {: .text-delta } 20 | 1. TOC 21 | {:toc} 22 |Observations Explained
11 | 12 |
13 |
20 |
21 | During the scanning processes, a number of observations are captured. These can range form simple informational observations to more serious potential security vulnerabilities of the HCL Domino environment.
22 |
23 | These observations are captured while the scans are occurring and are provided to the user once all scans are completed.
24 |
25 | Instructions on how to remediate any HCL Domino environment settings to correct the observations are provided within the DLAU interface.
26 |
27 | Below is a list of the Observations that are captured with a description of what the observation means.
28 |
29 | **Special Note:** information in **_Bold Italicized_** letters are for example purposes only. these values will vary between clients.
30 |
31 | ___
32 | ## Security Observations
33 |
34 | The HCL Domino Server **_"Production/ACME"_** is not properly secured for HTTP traffic
35 |
36 | - This observation indicates that the server access settings are not enforced for HTTP traffic. When this is the case, even if a user's name is listed in a Deny Access Group, the user has the ability to access the HCL Domino servers using a web browser. The HTTP port needs to be properly secured in order to report on user's who are listed in a Deny Access Group properly, else they will be counted as an Authorized User
37 |
38 |
39 | The HCL Domino Server **_"Production/ACME"_** is not properly secured for LDAP traffic
40 |
41 | - This observation indicates that the server access settings are not enforced for LDAP traffic. When this is the case, even if a user's name is listed in a Deny Access Group, the user has the ability to access the HCL Domino servers using an LDAP client. The LDAP port needs to be properly secured in order to report on user's who are listed in a Deny Access Group properly, else they will be counted as an Authorized User
42 |
43 | The HCL Domino Server **_"Production/ACME"_** is not using any Deny Access Groups to secure server access
44 |
45 | - This observation is reporting that a Deny Access Group is not listed on the specified HCL Domino server document. therefore, anyone with credentials, either using a Notes ID or internet credentials, has the ability to access the HCL Domino server. Even if an employee leaves the client's organization, they would still have the ability to access the HCL Domino environment.
46 |
47 | The Deny Access Group named **_"ACME Deny Access"_** appears to be missing from your Domino Directory
48 |
49 | - This observation is reporting that, even though there is a Deny Access group listed on the Domino server document, the actual Deny Access group does not exist. In this scenario, the usage of the Deny Access group will be ignored, and in turn anyone with credentials to the HCL Domino environment will have access to the HCL Domino server.
50 |
51 | ___
52 | ## Warning Observations
53 |
54 | The HCL Domino Server **_"International/ACME"_** appears to be Offline
55 |
56 | - This observation is indicating that the server listed is not accessible during the HCL Domino Environment scan. This can indicate either a connectivity issue or that the HCL Domino server is, in fact, offline. If the HCL Domino server is offline purposefully, there is nothing more for the user to do. But if the listed HCL Domino server is supposed to be accessible, this observation is highlighting a potential connectivity issue for all users.
57 |
58 | The HCL Domino Directory configured in Directory Assistance cannot be located - Server: **_Production/ACME_** (file name: **_external_names.nsf_**)
59 |
60 | - This observation is indicating that the listed additional Domino Directory that is configured in the Directory Assistance Catalog is not accessible and/or available. This observation can be causing connectivity or other issues for the users that are listed in the additional Domino Directory
61 |
62 | The Directory Assistance configuration **_"DomainName" (DomainTitle)_** Is a LDAP Directory
63 |
64 | - This observation indicates that the HCL Domino environment has a Directory Assistance configuration that connects to a LDAP Directory. Scanning of LDAP Directories is not yet supported by this utility. Therefore, the total Authorized Users that are being reported may not be representative of the total number of possible Authorized Users in your environment.
65 |
66 | The HCL Domino Server is configured to allow wildcard group access
67 |
68 | - This observation indicates that the HCL Domino environment allows for users to access server(s) that may be uncounted as part of the scan.
69 |
70 | ___
71 | ## Informational Observations
72 |
73 | The License Tracking task is not running on the HCL Domino server **_Production/ACME_**
74 |
75 | - This observation is reporting that the HCL Domino server listed does not have the Domino License Tracking system running. As this is an optional system , there is no immediate need for the Domino Administrator to make any changes. However, having the Domino License Tracking system running will provide better results for the Domino Administrator when they review the aggregated User Information
76 |
77 | The Deny Access Group named **_"ACME More Deny Access"_** has no Members listed
78 |
79 | - This observation is indicating that the Deny Access group that is in use within the HCL Domino environment has no user names within its Members list. This is indicated as an Informational Observation as there may be other Group names listed in the Members list.
80 |
--------------------------------------------------------------------------------
/docs/de-de/observations.md:
--------------------------------------------------------------------------------
1 | ---
2 | layout: default
3 | title: "Anmerkungen"
4 | parent: "Home (German-Deutsch)"
5 | nav_order: 6
6 | description: "Anmerkungen"
7 | has_children: false
8 | ---
9 |
10 | Sie lesen die deutsche Übersetzung [dieser Seite](../issues.md)
11 |
12 | 14 | Table of contents 15 |
16 | {: .text-delta } 17 | 1. TOC 18 | {:toc} 19 |Erklärung der Anmerkungen
13 | 14 |
15 |
22 | Während des Scanvorgangs wird eine Reihe von Anmerkungen erfasst. Diese können von einfachen Informationsbeobachtungen bis hin zu schwerwiegenderen potenziellen Sicherheitsschwachstellen in der HCL-Domino-Umgebung reichen.
23 |
24 | Diese Beobachtungen werden während der Scans erfasst und dem Benutzer zur Verfügung gestellt, sobald alle Scans abgeschlossen sind.
25 |
26 | Anweisungen zur Korrektur der HCL Domino-Umgebungseinstellungen, um die Beobachtungen zu korrigieren, werden innerhalb der DLAU-Schnittstelle bereitgestellt.
27 |
28 | Nachfolgend finden Sie eine Liste der erfassten Beobachtungen mit einer Beschreibung, was die Beobachtung bedeutet.
29 |
30 | **Hinweis:** Informationen in **_fett / kursiv_** sind nur als Beispiel zu verstehen.
31 |
32 | ___
33 | ## Security Observations
34 |
35 | The HCL Domino Server **_“Production/ACME”_** is not properly secured for HTTP traffic
36 |
37 | - Diese Anmerkung deutet darauf hin, dass die Serverzugriffseinstellungen für den HTTP-Verkehr nicht erzwungen werden. Wenn dies der Fall ist, kann der Benutzer mit einem Webbrowser auf die HCL Domino-Server zugreifen, selbst wenn der Name des Benutzers in einer Zugriffsverweigerungsgruppe aufgeführt ist. Der HTTP-Port muss ordnungsgemäß gesichert sein, damit Benutzer, die in einer Zugriffsverweigerungsgruppe aufgeführt sind, ordnungsgemäß gemeldet werden können, andernfalls werden sie als autorisierte Benutzer gezählt.
38 |
39 | Der HCL Domino Server **_"Production/ACME"_** ist nicht ordnungsgemäß für den LDAP-Datenverkehr gesichert
40 |
41 | - Diese Beobachtung deutet darauf hin, dass die Serverzugriffseinstellungen für den LDAP-Verkehr nicht erzwungen werden. Wenn dies der Fall ist, kann der Benutzer mit einem LDAP-Client auf die HCL Domino-Server zugreifen, selbst wenn der Name des Benutzers in einer Zugriffsverweigerungsgruppe aufgeführt ist. Der LDAP-Port muss ordnungsgemäß gesichert sein, damit Benutzer, die in einer Zugriffsverweigerungsgruppe aufgeführt sind, ordnungsgemäß gemeldet werden können, da sie sonst als autorisierte Benutzer gezählt werden.
42 |
43 | Der HCL Domino Server **_"Production/ACME"_** verwendet keine Deny Access Groups zur Sicherung des Serverzugriffs
44 |
45 | - Diese Beobachtung meldet, dass auf dem angegebenen HCL-Domino-Serverdokument keine Deny Access Group aufgeführt ist. Daher kann jeder, der über eine Notes-ID oder Internet-Zugangsdaten verfügt, auf den HCL-Domino-Server zugreifen. Selbst wenn ein Mitarbeiter das Unternehmen des Kunden verlässt, hat er immer noch die Möglichkeit, auf die HCL Domino-Umgebung zuzugreifen.
46 |
47 | Die Deny Access-Gruppe mit dem Namen **_"ACME Deny Access"_** scheint in Ihrem Domino-Verzeichnis zu fehlen
48 |
49 | - Diese Beobachtung zeigt an, dass die Gruppe "Deny Access" nicht existiert, obwohl sie im Domino-Server-Dokument aufgeführt ist. In diesem Szenario wird die Verwendung der Zugriffsverweigerungsgruppe ignoriert, und im Gegenzug hat jeder mit Anmeldeinformationen für die HCL-Domino-Umgebung Zugriff auf den HCL-Domino-Server.
50 |
51 | ___
52 | ## Warnungen
53 |
54 | Der HCL Domino Server **_"International/ACME"_** scheint offline zu sein
55 |
56 | - Diese Beobachtung zeigt an, dass der aufgelistete Server während der Überprüfung der HCL-Domino-Umgebung nicht erreichbar ist. Dies kann entweder auf ein Konnektivitätsproblem hinweisen oder darauf, dass der HCL Domino-Server tatsächlich offline ist. Wenn der HCL Domino-Server absichtlich offline ist, kann der Benutzer nichts weiter tun. Wenn der aufgelistete HCL Domino-Server jedoch zugänglich sein sollte, weist diese Beobachtung auf ein potenzielles Konnektivitätsproblem für alle Benutzer hin.
57 |
58 | Das in der Verzeichnisunterstützung konfigurierte HCL Domino-Verzeichnis kann nicht gefunden werden - Server: **_Production/ACME_** (Dateiname: **_external_names.nsf_**)
59 |
60 | - Diese Anmerkung zeigt an, dass das aufgelistete zusätzliche Domino-Verzeichnis, das im Verzeichnisdienstkatalog konfiguriert ist, nicht zugänglich und/oder verfügbar ist. Diese Beobachtung kann zu Konnektivitäts- oder anderen Problemen für die Benutzer führen, die in dem zusätzlichen Domino-Verzeichnis aufgeführt sind.
61 |
62 | Die Directory Assistance-Konfiguration **_"DomainName" (DomainTitle)_** ist ein LDAP-Verzeichnis
63 |
64 | - Diese Beobachtung zeigt an, dass die HCL-Domino-Umgebung über eine Directory Assistance-Konfiguration verfügt, die eine Verbindung zu einem LDAP-Verzeichnis herstellt. Das Scannen von LDAP-Verzeichnissen wird von diesem Dienstprogramm noch nicht unterstützt. Daher ist die Gesamtzahl der angezeigten autorisierten Benutzer möglicherweise nicht repräsentativ für die Gesamtzahl der möglichen autorisierten Benutzer in Ihrer Umgebung.
65 |
66 | ___
67 | ## Informationelle Beobachtungen
68 |
69 | Die Lizenzverfolgungsaufgabe läuft nicht auf dem HCL Domino-Server **_Production/ACME_**
70 |
71 | - Diese Beobachtung zeigt an, dass auf dem aufgeführten HCL-Domino-Server das Domino-Lizenzverfolgungssystem nicht ausgeführt wird. Da es sich um ein optionales System handelt, besteht für den Domino-Administrator keine unmittelbare Notwendigkeit, irgendwelche Änderungen vorzunehmen. Wenn das Domino-Lizenzverfolgungssystem jedoch läuft, erhält der Domino-Administrator bessere Ergebnisse, wenn er die aggregierten Benutzerinformationen überprüft.
72 |
73 | Die Zugriffsverweigerungsgruppe mit dem Namen **_"ACME More Deny Access"_** hat keine Mitglieder aufgelistet.
74 |
75 | - Diese Beobachtung zeigt an, dass die in der HCL-Domino-Umgebung verwendete Deny Access-Gruppe keine Benutzernamen in ihrer Mitgliederliste hat. Es handelt sich um eine Informationsbeobachtung, da in der Mitgliederliste auch andere Gruppennamen aufgeführt sein können.
76 |
--------------------------------------------------------------------------------
/docs/de-de/results.md:
--------------------------------------------------------------------------------
1 | ---
2 | layout: default
3 | title: "Ergebnisse verstehen"
4 | parent: "Home (German-Deutsch)"
5 | nav_order: 7
6 | description: "Ergebnisse verstehen"
7 | has_children: false
8 | ---
9 |
10 | Sie lesen die deutsche Übersetzung [dieser Seite](../results.md)
11 |
12 | 16 | Inhalt 17 |
18 | {: .text-delta } 19 | 1. TOC 20 | {:toc} 21 |Ergebnisse verstehen
13 | 14 |
15 |
22 |
23 | ___
24 | Sobald der Scan abgeschlossen ist wird Ihnen eine Übersicht der Ergebnisse angezeigt wie hier dargestellt:
25 |
26 | 
27 |
28 | Dies ist das Ergebnis der durchgeführten Scans. Was es bedeutet und wie die Informationen zu verstehen sind wird im nachfolgend beschrieben.
29 |
30 | ____
31 | ### Authorized Users
32 | Der Wert "Autorisierte Benutzer" ist die Gesamtzahl der Benutzer, die autorisiert sind oder die Fähigkeit haben, auf Ihre HCL Domino-Server zuzugreifen. Die angezeigte Zahl wird von vielen Faktoren bestimmt:
33 |
34 | 1. Die Anzahl der Personendokumente, die in allen Domino-Verzeichnissen in Ihrer Umgebung enthalten sind
35 | 2. Diese Personendokumente haben ein gültiges Notenzertifikat
36 | - Wenn in dem Personendokument kein Notes-Zertifikat vorhanden ist, aber dennoch ein Internet-Passwort verfügbar
37 | 3. Der Name des Benutzers ist in keiner der Zugriffsverweigerungsgruppen aufgeführt, die auf den HCL-Domino-Servern verwendet werden.
38 | 4. Wenn der Benutzer in einer Zugriffsverweigerungsgruppe aufgeführt ist, kann der Benutzer immer noch als autorisierter Benutzer gezählt werden, wenn die HTTP- und/oder LDAP-Ports aktiviert sind, aber NICHT dieselben Sicherheitseinstellungen verwendet werden, die für den Rest der HCL Domino-Server verwendet wird. Weitere Informationen zu diesem Thema finden Sie in der [Observations Explained](../observations.md) page.
39 |
40 | Die Anzahl der autorisierten Benutzer wird für Lizenzzwecke verwendet.
41 |
42 | ___
43 | ### CCB Benutzer
44 | Der Wert "CCB-Benutzer" ist die Gesamtzahl der internen Mitarbeiter der Organisation, die die Möglichkeit haben, die Domino-Umgebung zu nutzen und darauf zuzugreifen.
45 |
46 | Auszug aus der Lizenzvereinbarung:
47 |
48 | *"Licensee must obtain separate, dedicated CCB entitlements for each Internal User. “Internal User” shall mean permanent or temporary or transient employee, or person paid for, or acting on behalf of Licensee’s Enterprise ("Licensee’s Enterprise" is Licensee and all Affiliates per
49 | MLA §1.1) who is assigned A/U access to the Program in any manner directly or indirectly (for example: via a multiplexing program, device, or application server) through any means.
50 | In addition, Licensee must obtain separate, dedicated CCB entitlements to assign A/U credentials to a specific task or role or other such entities."*
51 |
52 | ___
53 | ### CCX Benutzer
54 | Der Wert "CCX-Benutzer" ist die Gesamtzahl der externen Benutzer der Organisation, die die Möglichkeit haben, Dokumente in der Domino-Umgebung zu erstellen und zu lesen.
55 |
56 | Auszug aus der Lizenzvereinbarung:
57 |
58 | *"Licensee must obtain separate, dedicated CCX entitlements for
59 | each External User. An "External User" is a unique person not included in above Internal Users, who is assigned Authorized User access to the Program with restricted maximum level of Domino application access (ACL) as "AUTHOR". A CCX A/U entitlement is unique, but may be reassigned to another user after thirty (30) days of inactivity."*
60 |
61 | ___
62 | ### Personendokumente
63 | Der Wert "Personendokumente" ist die Gesamtzahl der Personendokumente, die in allen Domino-Verzeichnissen innerhalb der HCL-Domino-Umgebung enthalten sind.
64 |
65 | ___
66 | ### Mail Benutzer
67 | Der Wert "Mail Users" ist die Gesamtzahl der Benutzer, die für den Zugriff auf HCL Domino Mail konfiguriert sind. Dies ist auch ein wichtiger Wert bei der Bestimmung des erforderlichen Lizenztyps, wenn Sie nicht bereits für Complete Collaboration for Business (CCB)-Lizenzen lizenziert sind.
68 |
69 | ___
70 | ### Deny Access Gruppen
71 | Der Wert "Deny Access Groups" ist die Anzahl der Deny Access Groups, die auf Ihren HCL Domino-Servern verwendet werden. Diese Zahl umfasst auch alle rekursiven Gruppen, die beim Auffinden der verwendeten Deny Access Groups entdeckt wurden.
72 |
73 | ___
74 | ### Administration Server
75 | Dies ist der HCL-Domino-Administrationsserver, der als Grundlage für alle durchgeführten Scans verwendet wurde.
76 |
77 | __
78 | ### Alle Domino Servers in der Umgebung
79 | Dies ist eine Liste aller HCL-Domino-Server, die in der Umgebung konfiguriert sind. Sie basiert auf den Server-Dokumenten, die in allen gescannten Domino-Verzeichnissen gefunden wurden.
80 |
81 | In dieser Liste wird auch angezeigt, ob der Server online (verfügbar) oder offline ist.
82 |
83 | ___
84 | ### Entitlement Tracking Enabled Servers
85 | Für HCL Domino V12.x-Umgebungen wurde ein neues System mit der Bezeichnung "Entitlement Tracking" eingeführt. Diese Liste enthält alle HCL Domino-Server in der Umgebung, auf denen das System "Entitlement Tracking" läuft.
86 |
87 | Weitere Informationen zum "Entitlement Tracking System" finden Sie unter [Entitlement Tracking System](https://help.hcltechsw.com/domino/12.0.0/admin/admn_entitlementtracking.html)
88 |
89 | ___
90 | ### User Report Tool
91 | Für HCL Domino Server V9 - V11.x gibt es ein System namens "User Report Tool". Dieses System entspricht dem "Entitlement Tracking System", ist aber für HCL Domino Versionen kleiner als V12.x ausgelegt.
92 |
93 | Der angezeigte Wert ist der Ort, an dem sich die Ergebnisse des User Report Tools befinden.
94 |
95 | Weitere Informationen über das "User Report Tool" finden Sie unter: [User Report Tool Knowledgebase document](https://support.hcltechsw.com/csm?id=kb_article&sysparm_article=KB0095328)
96 |
97 | ___
98 | ### Directory Assistance Information
99 | Dieser Wert zeigt an, wo sich der Verzeichnisdienstkatalog in Ihrer HCL-Domino-Umgebung befindet.
100 |
101 | Wenn das Auskunftssystem nicht in Gebrauch ist, wird diese Information nicht angezeigt.
102 |
103 | ___
104 | ### Weitere Domino Verzeichnisse
105 | Dieser Wert listet alle zusätzlichen Domino-Verzeichnisse auf, die in Ihrer Organisation vorhanden sind.
106 |
107 | Wenn der erste aufgelistete Wert in der Farbe Blau angezeigt wird, bedeutet dies, dass das aufgelistete Domino-Verzeichnis verwendet wird, um "Externe Benutzer" aufzulisten - Benutzer, die keine Mitarbeiter der Organisation sind, denen aber dennoch ein begrenzter Zugriff auf die HCL-Domino-Server gewährt wird.
108 |
109 | Wenn das Auskunftssystem nicht in Gebrauch ist, wird diese Information nicht angezeigt.
110 |
111 | ___
112 | ### Anmerkungen
113 | Die im Abschnitt "Observations" angezeigten Werte listen alle Ergebnisse auf, die während des Scanvorgangs entdeckt wurden.
114 |
115 | Die Beobachtungen können von "Informational" (kleinere Punkte, die den Wert der gesammelten Daten verbessern können) über "Warnings" (Punkte, die in Ihrer HCL Domino-Umgebung ein Problem darstellen können) bis hin zu "Security" (Punkte, die die Sicherheit Ihrer HCL Domino-Umgebung beeinträchtigen und sich auf die Anzahl der "Authorized User" auswirken) reichen.
116 |
117 | {: .notice }
118 | Bei Sicherheitsrelevante Ergebnisse ist es empfehlenswert, sich mit jedem dieser Punkte zu befassen und den Scan dann erneut durchzuführen. Auf diese Weise erhalten Sie eine bessere Darstellung der tatsächlichen autorisierten Benutzer.
119 |
120 | Weitere Informationen zu den einzelnen möglichen Beobachtungen finden Sie unter [Anmerkungen](observations.md)
--------------------------------------------------------------------------------
/docs/results.md:
--------------------------------------------------------------------------------
1 | ---
2 | layout: default
3 | title: "Understanding Results"
4 | parent: "Home"
5 | nav_order: 7
6 | description: "Understanding the Results"
7 | has_children: false
8 | ---
9 |
10 | 16 | Inhalt 17 |
18 | {: .text-delta } 19 | 1. TOC 20 | {:toc} 21 |Understanding The Results
11 | 12 |
13 |
20 |
21 | ___
22 | Once you have completed the scans, you will be presented with a Results page that will look similar to the image below:
23 |
24 | 
25 |
26 | This is the findings from the scans that were performed. But what do these mean? Below is a description of what each area means and how the DLAU came to those values.
27 |
28 | ____
29 | ### Authorized Users
30 | The "Authorized Users" value is the total number of users who are authorized, or have the ability, to access your HCL Domino servers. The number that is displayed is determined by many factors:
31 |
32 | 1. The number of Person documents contained in all Domino Directories in your environment
33 | 2. These Person documents have a Valid Notes Certificate
34 | - If there is no Notes Certificate on the Person document, there will still be an Internet Password available
35 | 3. The user's name is not listed in any of the Deny Access Groups that are in use on the HCL Domino servers
36 | 4. If the user IS listed in a Deny Access Group, the user may still be counted as an Authorized User IF the HTTP and/or LDAP ports are enabled but NOT using the same security that is in use for the remainder of the HCL Domino servers. For more information on this topic, please see the [Observations](de-de/observations.md) page.
37 |
38 | The Authorized Users number is what is used for license purposes.***
39 |
40 | ___
41 | ### CCB Users
42 | The "CCB Users" value is the total number of Internal Employees of the organization that have the ability to use and access the Domino environment.***
43 |
44 | As noted in the CCB License Agreement:
45 |
46 | *Licensee must obtain separate, dedicated CCB entitlements for each Internal User. “Internal User” shall mean permanent or temporary or transient employee, or person paid for, or acting on behalf of Licensee’s Enterprise ("Licensee’s Enterprise" is Licensee and all Affiliates per
47 | MLA §1.1) who is assigned A/U access to the Program in any manner directly or indirectly (for example: via a multiplexing program, device, or application server) through any means.
48 | In addition, Licensee must obtain separate, dedicated CCB entitlements to assign A/U credentials to a specific task or role or other such entities.*
49 |
50 | ___
51 | ### CCX Users
52 | The "CCX Users" value is the total number of External Users of the organization that have gthe ability to Create and Read documents in the Domino environment.***
53 |
54 | As noted in the CCB License Agreement:
55 |
56 | *Licensee must obtain separate, dedicated CCX entitlements for
57 | each External User. An "External User" is a unique person not included in above Internal Users, who is assigned Authorized User access to the Program with restricted maximum level of Domino application access (ACL) as "AUTHOR". A CCX A/U entitlement is unique, but may be reassigned to another user after thirty (30) days of inactivity.*
58 |
59 | ___
60 | ### Inactive CCX Users
61 |
62 | This number is for informational purposes only. An inactive CCX user will not count towards CCX entitlements.
63 | Those are CCX users who technically can log in, but have not been logging in within the past 30 days of time.
64 | Inactive CCX Users shown in the column "All 365 days" is the number of CCX users who have never logged in within the past 365 days.
65 |
66 | ___
67 |
68 | ### Person Documents
69 | The "Person Documents" value is the total number of Person documents contained within all Domino Directories within the HCL Domino environment.***
70 |
71 | ___
72 | ### Mail Users
73 | The "Mail Users" value is the total number of users that are configured for HCL Domino Mail access. This is also an important value when determining the type of license that is required if you are not already licensed for Complete Collaboration for Business (CCB) licenses.
74 |
75 | ___
76 | ### Deny Access Groups
77 | The "Deny Access Groups" value is the number of Deny Access Groups that are in use on your HCL Domino servers. This number also includes any Recursive Groups that were discovered while locating the Deny Access Groups that are in use.
78 |
79 | ___
80 | ### Administration Server
81 | This is the HCL Domino Administration server that was used for the basis of all scans that are performed.
82 |
83 | __
84 | ### All Domino Servers in Environment
85 | This is a list of all HCL Domino servers that are configured in the environment. This is based on the Server documents discovered in all Domino Directories that were scanned.
86 |
87 | This list will also show if the server is online (Available) or offline.
88 |
89 | ___
90 | ### Entitlement Tracking Enabled Servers
91 | For HCL Domino V12.x environments, a new system titled "Entitlement Tracking" was introduced. This list is all the HCL Domino servers in the environment that is running the Entitlement Tracking system.
92 |
93 | For more information on "Entitlement Tracking System", please refer to [Entitlement Tracking System](https://help.hcltechsw.com/domino/12.0.0/admin/admn_entitlementtracking.html)
94 |
95 | ___
96 | ### User Report Tool Output Location
97 | For HCL Domino servers V9 - V11.x, there is a system called the "User Report Tool". This is a system which is equivalent to the "Entitlement Tracking System", but it has been made to work on versions of HCL Domino that are less than V12.x
98 |
99 | The value that is shown is where the results of the User Report Tool is located.
100 |
101 | For more information on the "User Report Tool", please refer to: [User Report Tool Knowledgebase document](https://support.hcltechsw.com/csm?id=kb_article&sysparm_article=KB0095328)
102 |
103 | ___
104 | ### Directory Assistance Information
105 | This value will show where the Directory Assistance Catalog is located in your HCL Domino environment.
106 |
107 | If the Directory Assistance system is not in use, this information will not be shown.
108 |
109 | ___
110 | ### Additional Domino Directories
111 | This value will list all additional Domino Directories that are in your organization.
112 |
113 | If the first value listed is shown in the color Blue, this indicates that the Domino directory listed is being used to list "External Users" - users that are not employees of the organization but are still being granted limited access to the HCL domino servers.
114 |
115 | If the Directory Assistance system is not in use, this information will not be shown.
116 |
117 | ___
118 | ### Observations
119 | The values shown in the 'Observations" section list all Environment Observations that were discovered during the scanning process.
120 |
121 | The Observations can range from "Informational" (minor items that can improve the value of the data collected), "Warnings" (items that may be an issue in your HCL Domino environment), and "Security" (items that will affect the secure nature of your HCL Domino environment and will have an effect on the "Authorized User" count).
122 |
123 | {: .notice }
124 | For "Security" Observations, it is recommended to address each of them and then run the scan again. This will provide a better representation of the true Authorized Users.
125 |
126 | For more information on each possible Observation, please open this link [Anmerkungen](de-/deobservations.md)
127 |
128 | *** If there were any non-Domino users found in the Entitlement Tracking part of the scan, they will be included in these counts.
--------------------------------------------------------------------------------
/docs/licensecalc.md:
--------------------------------------------------------------------------------
1 | ---
2 | layout: default
3 | title: "License Calculation"
4 | nav_order: 4
5 | description: "License Calculation"
6 | has_children: false
7 | ---
8 |
9 | 14 | Table of contents 15 |
16 | {: .text-delta } 17 | 1. TOC 18 | {:toc} 19 |How CCB and CCX Licenses Are Calculated
10 | 11 |
12 |
19 |
20 | The two (2) strategic licenses for HCL Domino, are:
21 |
22 | **Complete Collaboration Business Edition (CCB) -and-
23 | Complete Collaboration eXternal user (CCX)**
24 |
25 | ### Complete Collaboration Business Edition (CCB)
26 |
27 | CCB entitlements are needed for all of the employees and contractors in your enterprise needing access to your Domino CCB servers – covering all B2E (Business-to-Employees) scenarios. All CCB users have access to the full spectrum of Domino capabilities.
28 |
29 | A server licensed under CCB also include unlimited external web user access as needed for most B2C (Business-to-Consumer/Citizen) scenarios:
30 |
31 | * Guests: unlimited anonymous browser users can freely access your Domino based websites.
32 | * Known Guests: unlimited registered users with credentials to login for read-only access to applications.
33 |
34 | (see further here [“Licensing Update: Domino V12 and Key CCX Enhancement”](https://blog.hcltechsw.com/domino/licensing-update-domino-v12-and-key-ccx-enhancement/)).
35 |
36 | The volume of entitlements needed for a CCB configuration is the count of all credentials in Domino directories or any other authentication source used by the enterprise.
37 |
38 | ### Complete Collaboration eXternal user (CCX)
39 |
40 | For B2B (Business-to-Business) or advanced B2C scenarios, where the external users need to fully engage in applications beyond the read/only access permitted for Known Guests, HCL introduced the CCX entitlement as an add-on for CCB environments. The typical CCX user is a business partner, external agents, etc.
41 |
42 | CCX users have full functionality to use Domino and Domino Leap (if installed) applications and workflows but cannot create applications themselves. CCX users do not have a personal mailbox but can use task/functional mail for workflow routing or applications generating mail.
43 |
44 | Like the CCB Authorized User entitlement, the CCX Authorized User entitlement is also unique, however, can logically be reassigned after 30 days of inactivity. Consequently, you need entitlements to cover actual/expected CCX users in any 30-day period.
45 |
46 | This level of licensing has some restrictions that must be in place to identify them correctly. The most important restriction is that the CCX users cannot have an Access Control List level higher than “Editor” access. This means that a CCX user can create data (on documents) within a HCL Domino application but cannot modify those or other documents or data.
47 |
48 | Calculating CCB licenses is very straight forward: Count the number of valid Person Documents (valid meaning that there is a Notes ID associated with the Person document, the user listed on the Person Document is not a member of an active Deny Access Group, and the “CCB User” has access to at least one of the Domino servers).
49 |
50 | Calculating CCX users is more complex and requires two (2) additional functions of the Domino server to be running / available at the time of the DLAU scans.
51 |
52 | ___
53 |
54 | ## Domino User License Tracking
55 |
56 | The Domino User License Tracking is a system that is built into every Domino server since Domino V7. It is a system for monitoring and capturing when users log into a Domino server. It monitors logins from multiple different protocols as well (NRPC, HTTP, LDAP, SMTP, POP3, IMAP, IIOP).
57 |
58 | The information that is captured is used in the DLAU scans to determine the last login date for each user. This, in turn, allows the DLAU to determine when a potential CCX user was last active.
59 |
60 | CCX Licenses are calculated on the number of users who have accessed a Domino server over a twelve (12) month period, having this system active is required.
61 |
62 | For example, if the following number of CCX users accessed the Domino environment over a twelve (12) month period, the CCX licenses would be the high-water mark of the twelve (12) months’ worth of findings:
63 |
64 | - Jan: 12,000
65 | - Feb: 11,000
66 | - Mar: 10,000
67 | - Apr: 10,500
68 | - May: 12,500
69 | - Jun: 14,000
70 | - Jul: 13,500
71 | - Aug: 12,000
72 | - Sep: 13,000
73 | - Oct: 14,000
74 | - Nov: 12,500
75 | - Dec: 11,000
76 |
77 | i.e. 14,000 CCX entitlements needed for this configuration.
78 |
79 | To obtain this information for use in the DLAU, you must enable the License Tracking system on ALL Domino servers. Follow this link for instructions on enabling License Tracking: [License Tracking Eablement Instructions](https://help.hcltechsw.com/domino/12.0.2/admin/conf_licensetracking_t.html)
80 |
81 | ___
82 |
83 | ## Entitlement Tracking / Domino User Report Tool
84 | Another important aspect of calculating CCX licenses is ensuring that CCX users have a maximum Access Control List (ACL) level of “Editor” to all Domino applications.
85 |
86 | HCL has created two (2) systems for reporting on the ACL Levels of Domino Users.
87 |
88 | As of Domino 12.0, a new internal mechanism titled the “Entitlement Tracking System” is provided for collecting the highest entitlement that individual users have across a Domino domain. When a user appears in the ACL of a database with Reader access or above and that person has the right to access the server, the user is said to be an entitled user.
89 |
90 | A similar tool has been created for clients that are using earlier versions of Domino called the “Domino User Report Tool”. This system performs almost identical processes as the Entitlement Tracking system and reports the information into a Domino application which DLAU will access. DLAU will for now use the Domino User Report Tool for consistency across Domino versions now deployed.
91 |
92 | The Entitlement Tracking system is automatically available on HCL Domino V12.0 and above servers.
93 |
94 | The Domino User Report Tool is provided as an executable program which can run on any Notes client from V9.0.1 – V11.0.1. The Domino User Report Tool needs to be downloaded and deployed on a Domino Administrators computer.
95 |
96 | To obtain the Domino User Report Tool, follow this URL link: [User Report Tool for gathering data on users' maximum access levels across a set of servers](https://support.hcltechsw.com/csm?id=kb_article&sysparm_article=KB0095328)
97 |
98 | ## Categorizing Users or Directories as 'External'
99 |
100 | In order to identify if a user or account is an internal or external account, Directories and Person documents can be tagged. This tagging helps
101 |
102 | ### Directory
103 |
104 | An entire Directory can be tagged to only(!) contain external user accounts. This is done in the Directory Assistance database.
105 |
106 | Prerequsites:
107 | - The Directory must be configured in the Directory Assistance database.
108 | - Directory Assistance database must be updated with v14.5 of the template (da.ntf).
109 |
110 | 
111 |
112 | On the Basics tab of the Directory Assistance document, change the "Directory contains external users" item to "Yes" to tell the License Administration feature that any users in this directory are external users.
113 |
114 | This field was introduced in the Directory Assistance template (da.ntf) of version 14.5. The Template is compatible with HCL Domino version 12.0.x and later.
115 |
116 | For more information see:
117 | [HCL License Dashboard: Background and first steps](https://help.hcl-software.com/domino/14.5.0/admin/admn_dla_first_steps.html)
118 |
119 | ### Person Document
120 |
121 | An Person document in the Domino Directory can be tagged as external user account.
122 |
123 | On the Advanced tab of the Person document, change the "Account Type" item to "External" to indicate the License Administration that this user is an external user.
124 |
125 | 
126 |
127 | Please note:
128 | If the actual permissions of the user are above the license restrictions for external users, the user will still be counted as 'Internal' even though the person document is set to be 'external'
129 |
130 |
131 | Technical details:
132 |
133 | Field | Details
134 | --- | ---
135 | Field Name | $$PersonClassification
136 | Data Type | Text
137 | Field Flags | SUMMARY
138 | Field Value | "0" (default) for Internal, "1" for External
139 |
140 | To set this field programmatically, use e.g. a LotusScript agent to process selected documents:
141 |
142 | ```
143 | Dim session As New NotesSession
144 | Dim collection As NotesDocumentCollection
145 |
146 | Set collection = session.CurrentDatabase.UnprocessedDocuments
147 | Set PersonDoc = collection.GetFirstDocument()
148 | While Not(PersonDoc Is Nothing)
149 |
150 | If not (PersonDoc.GetItemValue ("$$PersonClassification")(0) = "1") then
151 | Call PersonDoc.ReplaceItemValue ("$$PersonClassification","1")
152 | Call PersonDoc.Save (True,False)
153 | end if
154 |
155 | Set doc = collection.GetNextDocument(PersonDoc)
156 | Wend
157 | ```
158 |
159 | For more information see: [Understanding the Person document](https://help.hcl-software.com/domino/14.5.0/admin/othr_persondocuments_r.html)
160 |
--------------------------------------------------------------------------------
/docs/de-de/licensecalc.md:
--------------------------------------------------------------------------------
1 | ---
2 | layout: default
3 | title: "Lizenzberechnung"
4 | parent: "Home (German-Deutsch)"
5 | nav_order: 2
6 | description: "Lizenzberechnung"
7 | has_children: false
8 | ---
9 |
10 | 13 | Table of contents 14 |
15 | {: .text-delta } 16 | 1. TOC 17 | {:toc} 18 |Wie CCB und CCX Lizenzen berechnet werden
11 | 12 |
13 |
20 |
21 | Es gibt zwei Lizenzmodelle für HCL Domino, die mit Hilfe von DLAU analysiert werden können, diese sind:
22 |
23 | * Complete Collaboration Business Edition (CCB)
24 | -und-
25 | * Complete Collaboration eXternal user (CCX)
26 |
27 | ## Complete Collaboration Business Edition (CCB)
28 |
29 | CCB Lizenzen sind für alle Mitarbeiter und Vertragsarbeiter des eigenen Unternehmens
30 | , wenn diese auf Domino Server Zugriff haben - damit sind alle B2E (Business-to-Employee) Scenarien gemeint. Alle CCB Benutzer können den kompletten Funktionsumfang von HCL Domino nutzen.
31 |
32 | Zusätzlich enthält ein Server, welcher unter CCB Lizensiert ist, eine unbegrenzte Zahl von Nutzern für folgende B2C (Business-to-Consumer/Citizen) Szenarien:
33 |
34 | * Gäste: unbegrenzter Anonymer Zugriff via Browser um Domino-basierte Webseiten zu besuchen
35 | * Bekannte Gäste: unbegrenter namentlicher Zugriff, d.h. Anmeldung am System mit höchstens Lesezugriff.
36 |
37 | (Weitere Informationen zu diesem Lizenzmodell finden Sie unter [“Licensing Update: Domino V12 and Key CCX Enhancement”](https://blog.hcltechsw.com/domino/licensing-update-domino-v12-and-key-ccx-enhancement/)).
38 |
39 | Die Menge der benötigten Lizenzen für eine CCB-Konfiguration entspricht der Menge aller im Domino Directory und aller angeschlossenen Authentifizierungsquellen in Ihrer gesamten Enterprise-Umgebung.
40 |
41 | ## Complete Collaboration eXternal user (CCX)
42 |
43 | Für B2B (Business-to-Business) oder speziellen B2C Szenarien be denen alle externen Benutzer mehr als nur Leserechte in Ihrer Umgebung benötigen, existiert diese zusätzliche Option. Complete Collaboration eXternal user (CCX) wird als Add-on zur CCB Lizensierung angeboten um z.B. ihren Business Partnern, externe Agenturen, etc eine Lizenz für den Zugriff auf Ihre Umgebung zu ermöglichen.
44 |
45 | CCX Benutzer können den vollständigen Funktionsumfang der Domino und, sofern installiert, der Domino Leap Produktpalette nutzen um mit Anwendungen und Workflows zu arbeiten, aber sie können keine Anwendungen erstellen oder bearbeiten. CCX Benutzer dürfen auch kein eigenes Postfach haben, können allerdings Fach-/Funktionspostfächer für Workflows nutzen und aus Anwendungen heraus Mails erstellen.
46 |
47 | Ähnlich wie das CCB Modell sind auch CCX als Authorisierte Benutzer zu betrachten, sind also namentlich bekannte Benutzer, werden jedoch nach 30 Tagen nichtbenutzung neu zugewisen. d.h. gezählt werden im CCX Modell nur Benutzer die sich innerhalb von 30 Tagen tatsächlich angemeldet haben.
48 |
49 | Beachten Sie in diesem Zusammenhang, Sie müssen genügend CCX Lizenzen vorhalten um die aktuelle und ggf zukünftige/schwankende Benutzermenge abzudecken.
50 |
51 | Das CCX Lizenzmodell unterliegt einigen Einschränkungen, werden diese nicht erfüllt gilt ein Benutzer nicht als CCX sondern als CCB Benutzer. Die wichtigste Einschränkung für CCX Benutzer ist das dieser höchstens die Berechtigungsstufe "Editor" haben darf, d.h. ein CCX Benutzer kann Dokumente in einer Datenbank erstellen, und auch Dokumente anderer Benutzern editieren (dafür sind Editoren-Rechte erforderlich). Bisher waren nur Author-Rechte gestattet, seit Sept. 2024 dürfen CCX Benutzer auch Editor-Rechte erhalten.
52 |
53 | Die Berechnung von CCB Lizenzen ist relativ einfach: Gezählt werden die Anzahl gültiger Personendokumente - gültig in diesem Fall heisst, daß es eine NotesID oder ein Kennwort zur Authentifizierung gibt, der Benutzername nicht in einer Deny-Access Gruppe aufgeführt ist, und der Benutzer mindestens zu einem Server der Umgebung Zugriff hat.
54 |
55 | Die Berechnung von CCX Benutzern ist weitaus komplexer und erfordert zwei zustzliche Funktionen, die auf dem Domino Server bzw den Domino servern aktiviert sein müssen bevor der DLAU scan ausgeführt werden kann:
56 |
57 | ___
58 |
59 | ## Domino User License Tracking
60 |
61 | Domino User License Tracking ist eine Funktion in Domino, die es seit Version 7 gibt. Es wurde entwickelt um dem Administrator einen Überblick darüber zu geben, welche Benutzer sich am System anmelden und über welche Protokolle (NRPC, HTTP, LDAP, SMTP, POP3, IMAP, IIOP) die Benutzer zugreifen.
62 |
63 | Diese Informationen werden von DLAU benötigt um festzustellen wann ein Benutzer sich zuletzt angemeldet hat. Wie oben beschrieben ist diese Information wichtig um die Anzahl der benötigten CCX Lizenzen zu ermitteln.
64 |
65 | CCX Lizenzen werden von DLAU als Höchstwert der Benutzer gezählt, die sich in den letzten 12 Monaten angemeldet haben. Für eine korrekte Berechnung ist es erforderlich das [Domino User License Tracking zu aktivieren](https://help.hcltechsw.com/domino/12.0.2/admin/conf_licensetracking_t.html) und die Informationen über den gesamten Zeitraum zu sammeln.
66 |
67 | Zum Beispiel:
68 | Die Anzahl der CCX Benutzer schwankt im laufe eines Jahres wie in nachfolgender Tabelle dargestellt. DLAU wird den höchsten Wert innerhalb der letzten 12 Monate verwenden:
69 |
70 | - Jan: 12.000
71 | - Feb: 11.000
72 | - Mar: 10.000
73 | - Apr: 10.500
74 | - May: 12.500
75 | - Jun: 14.000
76 | - Jul: 13.500
77 | - Aug: 12.000
78 | - Sep: 13.000
79 | - Oct: 14.000
80 | - Nov: 12.500
81 | - Dec: 11.000
82 |
83 | d.h. in dieser Konfiguration würden 14.000 CCX Lizenzen benötigt werden.
84 |
85 | Das User License Tracking System muß auf ALLEN(!) Domino Servern aktiviert werden, damit DLAU diese Informationen nutzen kann. Für weitere Informationen zur Akivierung lesen Sie bitte [License Tracking Enablement Instructions](https://help.hcltechsw.com/domino/12.0.2/admin/conf_licensetracking_t.html)
86 |
87 | ___
88 |
89 | ## Entitlement Tracking / Domino User Report Tool
90 |
91 | Ein weiter wichtiger Aspekt zur richtigen Berechnung von CCX Benutzern ist das CCX Bentzer in der Zugriffskontrollliste von Datenbanken maximal nur Editor-Rechte haben dürfen - bezogen auf alle Domino Server und alle Datenbanken.
92 |
93 | HCL hat für die Berechnung der Zugriffsrechte zwei Methoden bereitgestellt:
94 |
95 | ### für Server mit Domino 12.0 und höher
96 | Seit Domino 12.0 gibt es eine integrierte Funktion namens “Entitlement Tracking" welches die jeweils höchste Zugriffsberechtigung eines Benutzers über die gesamte Domino Domäne hinweg ausliest und tagesaktuell zur Verfügung stellt.
97 |
98 | Wenn ein Benutzer mindestens Leserechte in der Umgebung besitzt wird er von dem System erfasst und im weiteren mit den jeweils höchsten Berechtigungen die in der Gesamten Umgebung existieren der Auswertung hinzufgefügt.
99 |
100 | Das Entitlement Tracking ist in HCL Domino V12.0 enthalten und automatisch aktiviert.
101 |
102 | ### für Server mit Domino 11.0.x und kleiner
103 |
104 | Ein ähnliches Tool namens "Domino User Report Tool" wurde speziell für Server entwickelt die nicht mit Version 12.0.x oder höher laufen. Es funktioniert ähnlich dem Entitlement Tracking nur erfolgt die Erfassung der Informationen über ein Tool welches auf einem Client PC und nicht auf dem Server gestartet wird. Das Ergebnis wird von DLAU für die weitere Berechnung der benötigten Lizenzen verwendet.
105 |
106 | Das Domino User Report Tool wird als ausführbares Programm bereitgestellt und funktioniert mit Notes Client Versionen von V9.0.1 – V11.0.1.
107 | Verfügbar ist das Tool als Download und wird vom Administrator der Umgebung ausgeführt.
108 |
109 | Sie können das Tool über diesen Link herunterladen: [User Report Tool for gathering data on users' maximum access levels across a set of servers](https://support.hcltechsw.com/csm?id=kb_article&sysparm_article=KB0095328)
110 |
111 | ## Categorizing Users or Directories as 'External'
112 |
113 | In order to identify if a user or account is an internal or external account, Directories and Person documents can be tagged. This tagging helps
114 |
115 | ### Adressbuch
116 |
117 | Ein Adressbuch (Directory) welches nur(!) externe Benutzer enthält kann in der Directory Assistance datenbank als solches markiert werden.
118 |
119 | Vorausssetzungen:
120 | - Das Adressbuch muss in der Directory Assistance datenbank konfiguriert sein.
121 | - Directory Assistance Datenbank muss das Template (da.ntf) der Version v14.5 oder höher benutzen.
122 |
123 | 
124 |
125 | Im Reiter 'Basics' des Directory Assistance Dokumentes, kann die Einstellung "Verzeichnis enthält externe Benutzer" auf "Ja" geändert werden um der License Administration-Funktion die Information zu übergeben das alle Benutzer in diesem Directory als externe Benutzer zu betrachten sind.
126 |
127 | Das Feld wurde im Directory Assistance template (da.ntf) der version 14.5 einfgeführt. Das Template ist kompatibel mit HCL Domino Version 12.0.x und höher.
128 |
129 | Für weitere Informationen siehe:
130 | [HCL License Dashboard: Background and first steps](https://help.hcl-software.com/domino/14.5.0/admin/admn_dla_first_steps.html)
131 |
132 | ### Personendokument
133 |
134 | Ein Personendokument in einem Domino Directory can als externer User Account markiert werden.
135 |
136 | Die entsprechende Einstellung findet sich im Reiter "Erweitert" innerhalb des Personendokuments.
137 | Das Feld "Account Type" kann auf "External" gesetzt werden um der License Administration-Funktion die Information zu übergeben das es sich bei diesem Benutzer um einen externen Benutzer handelt.
138 |
139 | 
140 |
141 | Beachte:
142 | Wenn die tatsächlichen Berechtigungen des Accounts über den Lizenzbeschränkungen für externe Benutzer liegen, dann wird ein Benutzer als 'Intern' gezählt auch wenn der Account-Typ im Personendokument auf 'Extern' steht.
143 |
144 | Technische Details:
145 |
146 | Feld | Details
147 | --- | ---
148 | Field Name | $$PersonClassification
149 | Data Type | Text
150 | Field Flags | SUMMARY
151 | Field Value | "0" (default) for Internal, "1" for External
152 |
153 | Um das Feld programmatisch zu setzen, kann z.B. ein LotusScript Agent verwendet werden der das Feld für alle markierten Dokumente in einer Ansicht setzt:
154 |
155 | ```
156 | Dim session As New NotesSession
157 | Dim collection As NotesDocumentCollection
158 |
159 | Set collection = session.CurrentDatabase.UnprocessedDocuments
160 | Set PersonDoc = collection.GetFirstDocument()
161 | While Not(PersonDoc Is Nothing)
162 |
163 | If not (PersonDoc.GetItemValue ("$$PersonClassification")(0) = "1") then
164 | Call PersonDoc.ReplaceItemValue ("$$PersonClassification","1")
165 | Call PersonDoc.Save (True,False)
166 | end if
167 |
168 | Set doc = collection.GetNextDocument(PersonDoc)
169 | Wend
170 | ```
171 |
172 | Für weitere Informationen siehe: [Understanding the Person document](https://help.hcl-software.com/domino/14.5.0/admin/othr_persondocuments_r.html)
173 |
--------------------------------------------------------------------------------
/docs/de-de/instructions.md:
--------------------------------------------------------------------------------
1 | ---
2 | layout: default
3 | title: "Anleitung"
4 | parent: "Home (German-Deutsch)"
5 | nav_order: 2
6 | description: "Schritt für Schritt Anleitung"
7 | has_children: false
8 | has_toc: true
9 | ---
10 |
11 | Sie lesen die deutsche Übersetzung [dieser Seite](../instructions.md)
12 |
13 | 14 | Inhalt 15 |
16 | {: .text-delta } 17 | 1. TOC 18 | {:toc} 19 |Benutzung des HCL Domino License Analysis Utilities
14 | 15 |
16 |
23 |
24 | ___
25 | ## Voraussetungen - Herunterladen
26 | Bevor Sie mit dieser Anleitung beginnen können müssen Sie das HCL Domino License Analysis Utility (DLAU) herunterladen und in ihr Notes Data Verzeichnis legen.
27 |
28 | DLAU wurde so programmiert, daß es am besten von einem lokalen PC aus gestartet wird ohne es auf ihre HCL Domino server replizieren/kopieren zu müssen.
29 |
30 | [Neueste Version laden](https://github.com/HCL-TECH-SOFTWARE/domino-license-analysis-utility-DLAU/releases/latest){: .btn .btn-green }
31 |
32 | Prüfen Sie ebenfalls ob Ihre Umgebung die [Mindestanforderungen](../requirements.md) erfüllt.
33 |
34 | ___
35 | ## Schritt 1 - Starten und signieren
36 | Nachdem DLAU heruntergeladen und in das Notes Daten Verzeichnis kopiert wurde muss es nun vor der Benutzung noch signiert werden.
37 |
38 | Die Designelemente im tool müssen elektronisch signiert werden damit das Tool ohne ECL Warnungen benutzt werden kann und damit der Scan im Hintergrund ablaufen kann. Wenn die Analyse läuft können Sie also ihren HCL Notes Client weiter benutzen.
39 |
40 | Die einfachste methode das Tool zu signieren ist es die Datenbank direkt im Windows Explorer zu öffnen.
41 | Nach dem öffnen erscheint ein Bildschirm (Siehe Foto) mit einer Anleitung zum signieren des Tools:
42 |
43 | 
44 |
45 | Je nachdem wie erfahren sie im Umgang mit elektronischen Signaturen sind wählen sie die entsprechende Option.
46 |
47 | ___
48 | ## Schritt 2 - Erneut öffnen
49 | Nachdem die Anwendung signiert worden ist, schliessen sie diese und öffnen Sie die Anwendung erneut.
50 | Das Icon müsste sich bereits auf ihrer HCL Notes Arbeitsoberfläche befinden.
51 |
52 | Sobald Sie DLAU erneut geöffnet haben werden Sie mit folgenden Bildschirm begrüßt
53 |
54 | 
55 |
56 | Im Begrüßungstext wird beschrieben welche Schritte das Tool durchführen wird. Es liefert auch informationen darüber welche Schritte unternommen werden können um bessere bzw. klarere Ergebnisse zu erzielen.
57 |
58 | Wenn Sie den Scan starten möchten oder wenn Sie weitere Systeme hinzufügen möchten nutzen Sie bitte die Links unter "Important Links"
59 |
60 | Um den Scanprozess zu starten klicken Sie bitte auf die Schaltfläche **"Next"** .
61 |
62 | ___
63 | ## Schritt 3 - HCL Domino Umgebung Scannen
64 |
65 | Dieser erste Scan ist der "HCL Domino Environment Scan". Damit wird die Umgebung allgemein untersucht, die Servernamen werden ermittelt, Deny Access Gruppen und andere Zugriffsrelevante Einstellungen der Server werden analysiert.
66 |
67 | Hier eine Übersicht der Aktionen die in diesem Schritt durchgeführt werden:
68 |
69 | * Identifizieren des Domino Administrationsservers
70 | * Namen der Domino server ermitteln
71 | * Verfügbarkeit der Domino Server ermitteln (Online or Offline)
72 | * Directory Assistance Usage auslesen
73 | * Wenn DA benutzt wird, alle zusätzlichen Domino Directories einlesen
74 | * Prüfen ob HTTP und/oder LDAP protocol verwendet wird
75 | * Namen der verwendenten Deny Access Groups ermitteln
76 | * Prüfen ob Domino V12 verwendet wird, falls ja, auflisten der Server welche das Entitlement Tracking system verwenden
77 | * Prüfen ob und auf welchen Servern das (alte) Domino License Tracking system verwendet wird
78 |
79 | Um den Scan der Umgebung zu starten klicken Sie bitte auf die Schaltfläche **Start Environment Scan Now** :
80 |
81 | 
82 |
83 | Dieser allgemeine HCL Domino Environment scan wird ungefähr **5 minutes** dauern, je nachdem wieviele HCL Domino Servers in Ihrer Umgebung vorhanden sind kann es ggf. schneller gehen oder länger dauern.
84 |
85 | Wenn in Ihrer Umgebung zusätzliche Domino Directories (Adressbücher) über Directoy Assistance Katalog eingebunden sind werden wir Sie fragen ob diese Adressbücher für die registrierung **externer Benutzer** verwendet werden.
86 | Ein **Externer Benutzer** ist ein Benutzer welcher kein Mitarbeiter der eigenen Organisation bzw. des eigenen Unternehmens ist sowie in der Zugriffskontrolle nur maximal "Author" Rechte in den HCL Domino Datenbanken besitzt.
87 | Dieser Benutzertyp wird im Lizenzmodell als **Complete Collaboration for External Users** (CCX) bezeichnet.
88 |
89 | Falls dies in Ihrer Umgebung der Fall sein sollte, werden Sie folgende Meldung erhalten.:
90 |
91 | 
92 |
93 | Wenn Sie an dieser Stelle mit "Yes" antworten, werden Sie im nachfolgendn Dialog aufgefordert weitere Informationen zu den Directories/Adressbüchern anzugeben. z.B. welches der Directories für CCX Benutzer verwendet wird und/oder die Möglichkeit einen bestimmte OrgUnit / Certifier zu definieren der in Ihrer Umgebung für CCX Benutzer verwendet wurde.
94 |
95 | 
96 |
97 | Sobald der HCL Domino Environment Scan erfolgreich abgeschlossen wurde, erhalten Sie eine übersicht der bisherigen Erkenntnisse:
98 |
99 | 
100 |
101 | To progress to the next scan, click the **"Next"** button.
102 |
103 | ___
104 | ## Schritt 4 - HCL Domino Benutzer Scan
105 | In diesem Schritt, der als "HCL Domino Users Scan" bezeichnet wird werden alle Directories/Adressbücher durchsucht um Personendokumente zu finden.
106 |
107 | Die Informationen die ausgelesen werden sind:
108 |
109 | * Benutzername
110 | * Email addresse
111 | * Notes Zertifikat und Ablaufdatum (if available)
112 | * Ob ein Internet Password gesetzt ist oder nicht (natürlich wird das Kennwort selbst nicht ausgelesen)
113 | * Name des Domino Directories/Adressbuches in dem das Personendokument gefunden wurde
114 | * Datum wann der Benutzer auf den Domino Server zuletzt zugegriffen hat (nur wenn License Tracking aktiviert ist)
115 | * Protokoll mit dem der Benutzer auf den Domino Server zugegriffen hat (nur wenn License Tracking aktiviert ist)
116 |
117 | Weitere Informationen werden erst im späteren Verlauf der Analyse hinzugefügt, mehr dazu in den folgenden Schritten.
118 |
119 | Um den HCL Domino Users Scan, zu starten betätigen Sie die Schaltfläche **Start Users Scan Now** :
120 |
121 | 
122 |
123 | Sobald der HCL Domino Users Scan erfolgreich beendet wurde, werden die Ergebnisse wie folgt dargestellt:
124 | 
125 |
126 | Um mit dem nächsten Schritt fortzufahren betätigen Sie die Schaltfläche **"Next"** .
127 |
128 | ___
129 | ## Schritt 5 - Deny Access Group Scan
130 | Die Dritte Prüfung betrifft die Deny Access Gruppen. Dieser Scan vergleicht die Konfiguration im Domino Server Dokument mit den gefundenen Deny Access Gruppen um herauszufinden welche der Gruppen tatsächlich verwendet werden um den Zugriff zum Server zu steuern.
131 |
132 | Ausgehend von den gefundenen Deny Access Gruppen wird in diesem Schritt jede Gruppe aufgelöst um alle Gruppenmitglieder und verschachtelte Gruppen zu identifizieren. Dieser rekursieve Scan wird solange laufen bis alle Gruppen aufgelöst wurden.
133 |
134 | Sobald alle Informationen gefunden wurden, werden Benutzernamen aus den DEny Access Gruppen verglichen mit den Namen der Benutzer die im vorherigen Schritt gefunden wurden um festzustellen ob ein Benutzer Zugriff zum Server hat oder nicht.
135 |
136 | Um mit dem Deny Access Group Scan zu starten, betätigen Sie die Schaltfläche **Start Deny Access Scan Now** :
137 |
138 | 
139 |
140 | Sobald der Deny Access Group Scan abgeschlossen ist, werden die Ergebnisse wie folgt dargestellt:
141 |
142 | 
143 |
144 | Um mit dem nächsten Schritt fortzufahren bentätigen Sie die Schaltfläche **"Next"** .
145 |
146 | ___
147 | ## Schritt 6 - Entitlement Tracking / User Report Tool Scan
148 | Im vierten Schritt "Entitlement Tracking / User Report Tool Scan"wird nach einem von zwei möglichen Datenquellen gesucht:
149 |
150 | 1. Entitlement Tracking: ist ein Feature des HCL Domino V12 Servers. Sobald ein V12 server gefunden wurde wird dieser Scann durchgeführt
151 |
152 | 2. User Report Tool Results: ist ein optionales Feature welches auf dem Entitlement Tracking Feature (siehe oben) baseirt und seit HCL Domino V12 zur Verfügung steht. Im Gegensatz zum Entitlement Tracking selbst ist dieses Feature auch rückwärtskompatibel und funktioniert mit Domino servern der Version 9.0.x. Um diese Datenquelle nutzen zu können ist es erforderlich das Tool herunterzuladen und seperat zu starten bevor DLAU verwendet werden kann.
153 |
154 | Sie finden das User Report Tool hier: [User Report Tool - HCL Knowledgebase Article KB0095328](https://support.hcltechsw.com/csm?id=kb_article&sysparm_article=KB0095328)
155 |
156 |
157 | Die Informationen aus dieser Prüfung werden zusammengefasst und stellen die höchste Berechtigung in der **Access Control List (ACL)** dar die ein Benutzer in Ihrer HCL Domino Umgebung erreichen kann. Das ist notwendig um festzustellen ob es sich bei dem Benutzer womöglich um einen CCB oder einen CCX Benutzer handelt.
158 |
159 | Um den Entitlement Tracking / User Report Tool Scan zu starten, klicken Sie bitte auf die Schaltfläche **Start Entitlement Tracking / User Report Tool Scan Now** :
160 |
161 | 
162 |
163 | Sobald der Entitlement Tracking / User Report Tool vollständig abgeschlossen ist werden die Ergebnisse wie folgt dargestellt:
164 |
165 | 
166 |
167 | Um mit dem nächsten Schritt fortzufahren bentätigen Sie die Schaltfläche **"Next"** .
168 |
169 | ___
170 | ## Schritt 7 - Zusammenfassung und Ansehen der Ergebnisse
171 | Jetzt sind alle Scanns abgeschlossen. Sie erhalten eine Erfolgsmeldung wie in nachfolgendem Bildschirmfoto dargestellt:
172 |
173 | 
174 |
175 | Jetzt haben Sie die Möglichkeit sich die Ergebnisse genauer anzusehen. Drücken Sie dazu auf die Schaltfläche **"View Results"** .
176 |
177 | Die Ergebnisse werden wie folgt dargestellt:
178 |
179 | 
180 |
181 |
182 | ## Fertig
183 |
184 | Die vom Tool berechneten Werte repräsentieren ihre aktuelle Umgebung und aktuelle Konfiguration, es ist jedoch möglich das diese Werte nicht ihren zukünftigen Bedarf wiederspiegeln. Lesen Sie deshalb bitte unbedingt den Artikel [Ergebnisse Verstehen](results.md) - und falls sie Fragen zu den ermittelten Ergebnissen haben kontaktieren Sie bitte ihren HCL Ansprechpartner oder öffnen ein Supportticket unter [HCL Customer Support](https://support.hcltechsw.com/csm)
185 |
186 |
187 | {: mx-auto }
--------------------------------------------------------------------------------
/LICENSE:
--------------------------------------------------------------------------------
1 | Apache License
2 | Version 2.0, January 2004
3 | http://www.apache.org/licenses/
4 |
5 | TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
6 |
7 | 1. Definitions.
8 |
9 | "License" shall mean the terms and conditions for use, reproduction,
10 | and distribution as defined by Sections 1 through 9 of this document.
11 |
12 | "Licensor" shall mean the copyright owner or entity authorized by
13 | the copyright owner that is granting the License.
14 |
15 | "Legal Entity" shall mean the union of the acting entity and all
16 | other entities that control, are controlled by, or are under common
17 | control with that entity. For the purposes of this definition,
18 | "control" means (i) the power, direct or indirect, to cause the
19 | direction or management of such entity, whether by contract or
20 | otherwise, or (ii) ownership of fifty percent (50%) or more of the
21 | outstanding shares, or (iii) beneficial ownership of such entity.
22 |
23 | "You" (or "Your") shall mean an individual or Legal Entity
24 | exercising permissions granted by this License.
25 |
26 | "Source" form shall mean the preferred form for making modifications,
27 | including but not limited to software source code, documentation
28 | source, and configuration files.
29 |
30 | "Object" form shall mean any form resulting from mechanical
31 | transformation or translation of a Source form, including but
32 | not limited to compiled object code, generated documentation,
33 | and conversions to other media types.
34 |
35 | "Work" shall mean the work of authorship, whether in Source or
36 | Object form, made available under the License, as indicated by a
37 | copyright notice that is included in or attached to the work
38 | (an example is provided in the Appendix below).
39 |
40 | "Derivative Works" shall mean any work, whether in Source or Object
41 | form, that is based on (or derived from) the Work and for which the
42 | editorial revisions, annotations, elaborations, or other modifications
43 | represent, as a whole, an original work of authorship. For the purposes
44 | of this License, Derivative Works shall not include works that remain
45 | separable from, or merely link (or bind by name) to the interfaces of,
46 | the Work and Derivative Works thereof.
47 |
48 | "Contribution" shall mean any work of authorship, including
49 | the original version of the Work and any modifications or additions
50 | to that Work or Derivative Works thereof, that is intentionally
51 | submitted to Licensor for inclusion in the Work by the copyright owner
52 | or by an individual or Legal Entity authorized to submit on behalf of
53 | the copyright owner. For the purposes of this definition, "submitted"
54 | means any form of electronic, verbal, or written communication sent
55 | to the Licensor or its representatives, including but not limited to
56 | communication on electronic mailing lists, source code control systems,
57 | and issue tracking systems that are managed by, or on behalf of, the
58 | Licensor for the purpose of discussing and improving the Work, but
59 | excluding communication that is conspicuously marked or otherwise
60 | designated in writing by the copyright owner as "Not a Contribution."
61 |
62 | "Contributor" shall mean Licensor and any individual or Legal Entity
63 | on behalf of whom a Contribution has been received by Licensor and
64 | subsequently incorporated within the Work.
65 |
66 | 2. Grant of Copyright License. Subject to the terms and conditions of
67 | this License, each Contributor hereby grants to You a perpetual,
68 | worldwide, non-exclusive, no-charge, royalty-free, irrevocable
69 | copyright license to reproduce, prepare Derivative Works of,
70 | publicly display, publicly perform, sublicense, and distribute the
71 | Work and such Derivative Works in Source or Object form.
72 |
73 | 3. Grant of Patent License. Subject to the terms and conditions of
74 | this License, each Contributor hereby grants to You a perpetual,
75 | worldwide, non-exclusive, no-charge, royalty-free, irrevocable
76 | (except as stated in this section) patent license to make, have made,
77 | use, offer to sell, sell, import, and otherwise transfer the Work,
78 | where such license applies only to those patent claims licensable
79 | by such Contributor that are necessarily infringed by their
80 | Contribution(s) alone or by combination of their Contribution(s)
81 | with the Work to which such Contribution(s) was submitted. If You
82 | institute patent litigation against any entity (including a
83 | cross-claim or counterclaim in a lawsuit) alleging that the Work
84 | or a Contribution incorporated within the Work constitutes direct
85 | or contributory patent infringement, then any patent licenses
86 | granted to You under this License for that Work shall terminate
87 | as of the date such litigation is filed.
88 |
89 | 4. Redistribution. You may reproduce and distribute copies of the
90 | Work or Derivative Works thereof in any medium, with or without
91 | modifications, and in Source or Object form, provided that You
92 | meet the following conditions:
93 |
94 | (a) You must give any other recipients of the Work or
95 | Derivative Works a copy of this License; and
96 |
97 | (b) You must cause any modified files to carry prominent notices
98 | stating that You changed the files; and
99 |
100 | (c) You must retain, in the Source form of any Derivative Works
101 | that You distribute, all copyright, patent, trademark, and
102 | attribution notices from the Source form of the Work,
103 | excluding those notices that do not pertain to any part of
104 | the Derivative Works; and
105 |
106 | (d) If the Work includes a "NOTICE" text file as part of its
107 | distribution, then any Derivative Works that You distribute must
108 | include a readable copy of the attribution notices contained
109 | within such NOTICE file, excluding those notices that do not
110 | pertain to any part of the Derivative Works, in at least one
111 | of the following places: within a NOTICE text file distributed
112 | as part of the Derivative Works; within the Source form or
113 | documentation, if provided along with the Derivative Works; or,
114 | within a display generated by the Derivative Works, if and
115 | wherever such third-party notices normally appear. The contents
116 | of the NOTICE file are for informational purposes only and
117 | do not modify the License. You may add Your own attribution
118 | notices within Derivative Works that You distribute, alongside
119 | or as an addendum to the NOTICE text from the Work, provided
120 | that such additional attribution notices cannot be construed
121 | as modifying the License.
122 |
123 | You may add Your own copyright statement to Your modifications and
124 | may provide additional or different license terms and conditions
125 | for use, reproduction, or distribution of Your modifications, or
126 | for any such Derivative Works as a whole, provided Your use,
127 | reproduction, and distribution of the Work otherwise complies with
128 | the conditions stated in this License.
129 |
130 | 5. Submission of Contributions. Unless You explicitly state otherwise,
131 | any Contribution intentionally submitted for inclusion in the Work
132 | by You to the Licensor shall be under the terms and conditions of
133 | this License, without any additional terms or conditions.
134 | Notwithstanding the above, nothing herein shall supersede or modify
135 | the terms of any separate license agreement you may have executed
136 | with Licensor regarding such Contributions.
137 |
138 | 6. Trademarks. This License does not grant permission to use the trade
139 | names, trademarks, service marks, or product names of the Licensor,
140 | except as required for reasonable and customary use in describing the
141 | origin of the Work and reproducing the content of the NOTICE file.
142 |
143 | 7. Disclaimer of Warranty. Unless required by applicable law or
144 | agreed to in writing, Licensor provides the Work (and each
145 | Contributor provides its Contributions) on an "AS IS" BASIS,
146 | WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
147 | implied, including, without limitation, any warranties or conditions
148 | of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
149 | PARTICULAR PURPOSE. You are solely responsible for determining the
150 | appropriateness of using or redistributing the Work and assume any
151 | risks associated with Your exercise of permissions under this License.
152 |
153 | 8. Limitation of Liability. In no event and under no legal theory,
154 | whether in tort (including negligence), contract, or otherwise,
155 | unless required by applicable law (such as deliberate and grossly
156 | negligent acts) or agreed to in writing, shall any Contributor be
157 | liable to You for damages, including any direct, indirect, special,
158 | incidental, or consequential damages of any character arising as a
159 | result of this License or out of the use or inability to use the
160 | Work (including but not limited to damages for loss of goodwill,
161 | work stoppage, computer failure or malfunction, or any and all
162 | other commercial damages or losses), even if such Contributor
163 | has been advised of the possibility of such damages.
164 |
165 | 9. Accepting Warranty or Additional Liability. While redistributing
166 | the Work or Derivative Works thereof, You may choose to offer,
167 | and charge a fee for, acceptance of support, warranty, indemnity,
168 | or other liability obligations and/or rights consistent with this
169 | License. However, in accepting such obligations, You may act only
170 | on Your own behalf and on Your sole responsibility, not on behalf
171 | of any other Contributor, and only if You agree to indemnify,
172 | defend, and hold each Contributor harmless for any liability
173 | incurred by, or claims asserted against, such Contributor by reason
174 | of your accepting any such warranty or additional liability.
175 |
176 | END OF TERMS AND CONDITIONS
177 |
178 | APPENDIX: How to apply the Apache License to your work.
179 |
180 | To apply the Apache License to your work, attach the following
181 | boilerplate notice, with the fields enclosed by brackets "[]"
182 | replaced with your own identifying information. (Don't include
183 | the brackets!) The text should be enclosed in the appropriate
184 | comment syntax for the file format. We also recommend that a
185 | file or class name and description of purpose be included on the
186 | same "printed page" as the copyright notice for easier
187 | identification within third-party archives.
188 |
189 | Copyright Nash!Com, Daniel Nashed 2019, 2020
190 | Copyright IBM Corporation 2015, 2019
191 |
192 | Licensed under the Apache License, Version 2.0 (the "License");
193 | you may not use this file except in compliance with the License.
194 | You may obtain a copy of the License at
195 |
196 | http://www.apache.org/licenses/LICENSE-2.0
197 |
198 | Unless required by applicable law or agreed to in writing, software
199 | distributed under the License is distributed on an "AS IS" BASIS,
200 | WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
201 | See the License for the specific language governing permissions and
202 | limitations under the License.
203 |
--------------------------------------------------------------------------------
/docs/instructions.md:
--------------------------------------------------------------------------------
1 | ---
2 | layout: default
3 | title: "How to use"
4 | parent: "Home"
5 | nav_order: 2
6 | description: "Step by Step Instructions"
7 | has_children: false
8 | has_toc: true
9 | ---
10 |
11 | 17 | Inhalt 18 |
19 | {: .text-delta } 20 | 1. TOC 21 | {:toc} 22 |How to use the HCL Domino License Analysis Utility
12 | 13 |
14 |
21 |
22 | ___
23 | ## Prerequisites - Download Utility
24 | Prior to continuing through this documentation, you will need to download the HCL Domino License Analysis Utility (DLAU) into your Notes Data directory.
25 |
26 | DLAU is designed to work most efficiently on a local hard drive, so there is no need to copy/replicate the DLAU onto any of your HCL Domino servers.
27 |
28 | [Download Latest Release](https://github.com/HCL-TECH-SOFTWARE/domino-license-analysis-utility-DLAU/releases/latest){: .btn .btn-green }
29 |
30 | ___
31 | ## Recommendations
32 |
33 | Before starting, please acknowledge a few comments which we have received from customers that may help to get better results:
34 | - Leverage "Deny Access" Groups to block a user from accessing the server
35 | - Make sure to enable "Enforce Server Access" settings in the server document AND in the the Internet Ports for HTTP
36 | - Review access levels of your Domino applications prior running DLAU. This can be done e.g. by using the database catalog (catalog.nsf)
37 |
38 | ## Step 1 - Create the Application from the Template
39 | DLAU is provided as a template and you must create an application from the template. Save the [NTF](https://github.com/HCL-TECH-SOFTWARE/domino-license-analysis-utility-DLAU/releases/latest) from the latest release to your Notes Data directory. Once it is there, open the HCL Notes Client and proceed to File - New Application.
40 |
41 |
42 | 
43 | In the resulting dialog, in the top section, choose `Local` for the Server, for the Title use `HCL Domino License Analysis Utility` and the file name of `licenseanalysis.nsf`.
44 |
45 | In the template section, select `Local` for the Server and then locate the `HCL Domino License Analysis Utility` template in the list. Once this is done, select the `OK` button to finish the creation of the Application. Once the creation is complete, it will launch and you can proceed.
46 |
47 | 
48 |
49 | ## Step 2 - Sign the Design
50 | Now that the DLAU Application is created, it is now time for you to re-sign the design.
51 |
52 | It is required to sign the design elements in order for the environment scans to run in the background. Running the scans in the background will allow you to continue using your HCL Notes Client while the processing is taking place.
53 |
54 | The simplest method for opening the utility is to double-click on it in the File Explorer application.
55 |
56 | Once the utility is open, you should see the screen below which contains instructions on how to resign the design of the utility:
57 |
58 | 
59 |
60 | Depending on your experience level and how much you want to monitor the re-signing process, select the appropriate method listed.
61 |
62 | ___
63 | ## Step 2 - Re-Open
64 | Now that the design of the DLAU has been signed, you will need to re-open the utility. When you initially opened the DLAU a Domino application icon will have been added to your Workspace. Locate and open the DLAU.
65 |
66 | Once opened, you will be presented with the following screen:
67 |
68 | 
69 |
70 | Once opened, you will be provided some high level information about what the utility will be performing. It also provides you with information on other systems that can contribute to a cleaner result from the DLAU. If you would like to run and/or install the additional systems, click on the links under the "Important Links" area.
71 |
72 | To begin the scanning processes, click the **"Next"** button.
73 |
74 | ____
75 | ## Step 3 - HCL Domino Environment Scan
76 | The first scan is the "HCL Domino Environment Scan". This scan concentrates on the HCL Domino servers, their availability, usage of Deny Access Groups, and whether they are properly secured.
77 |
78 | A listing of what is scanned during this step is below:
79 |
80 | * Discovery of Domino Administration server
81 | * If the Administration server can not be detected, you will be prompted to select your Domino Directory. Typically the file name is "names.nsf"
82 | * Domino server names
83 | * Domino Server availability (Online or Offline)
84 | * Directory Assistance Usage
85 | * If DA is in use, discover all additional Domino Directories
86 | * Check for secured HTTP and LDAP protocols
87 | * Capture the name(s) of the Deny Access Groups that are in use on the Domino servers
88 | * Determine if Domino V12 is in use and, if it is, list which Domino servers are using the Entitlement Tracking system
89 | * Determine if Domino License Tracking system is running and on which Domino servers
90 |
91 | To begin the HCL Domino Environment Scan, click the **Start Environment Scan Now** button:
92 |
93 | 
94 |
95 | The HCL Domino Environment scan will take approximately **5 minutes** to complete, depending on the number of HCL Domino Servers in your environment.
96 |
97 | If your organization is using additional Domino Directories via the Directory Assistance Catalog, you will be asked if any of those additional Domino directories are being used to register **External Users**. An **External User** is a user that is not a direct employee of your organization and has a maximum Access Control List level of "Editor" to the Domino applications on your HCL Domino servers. This is better known as a **Complete Collaboration for External Users** (CCX) license.
98 |
99 | If this is the scenario in your environment, you will be presented the following message:
100 |
101 | 
102 |
103 | If you select "yes" as your answer, you will be presented with the following dialog which will provide you the opportunity to select either the Additional Domino Directory for CCX users and/or the ability to select the OrgUnit / Org that identifies the CCX users:
104 |
105 | 
106 |
107 | If your environment is running Domino V11 or older, you will also be asked to provide the results from the **User Report Tool**.
108 |
109 | {: .new }
110 | As of DLAU V1.2.5, the results from a recent User Report Tool process **MUST** be provided. **Failure to provide the results will cause DLAU to stop the remainder of the process and close.**
111 |
112 | 
113 |
114 | Once the HCL Domino Environment Scan is complete, you will be presented with the results, as shown below:
115 |
116 | 
117 |
118 | To progress to the next scan, click the **"Next"** button.
119 |
120 | ___
121 | ## Step 4 - HCL Domino Users Scan
122 | The second scan is the "HCL Domino Users Scan". This scan will process all Domino Directories and aggregates information from the Person documents it finds.
123 |
124 | The information that is aggregated is as follows:
125 |
126 | * User's name
127 | * User's Email address
128 | * Notes Certificate Expiry Date (if available)
129 | * Indication if the Internet Password is set (not the actual Internet Password)
130 | * Domino Directory where the Person document resides
131 | * Date when user last accessed a Domino Server (only if License Tracking is enabled)
132 | * Protocols that the user's used to access the Domino servers (only if License Tracking is enabled)
133 |
134 | Additional information is aggregated about each user during the subsequent scans.
135 |
136 | To begin the HCL Domino Users Scan, click the **Start Users Scan Now** button:
137 |
138 | 
139 |
140 | Once the HCL Domino Users Scan is complete, you will be presented with the results, as shown below:
141 | 
142 |
143 | To progress to the next scan, click the **"Next"** button.
144 |
145 | ___
146 | ## Step 5 - Deny Access Group Scan
147 | The third scan is the "Deny Access Group Scan". This scan looks at the values stored on the Server document aggregated data to determine what Deny Access Groups are in use to secure the Domino servers.
148 |
149 | Using the list of Deny Access Groups that are in use, the scan will retrieve the Deny Access Groups, all members of those Groups and also determine if there are Group names within the Deny Access Groups. If additional Group names are discovered, the scan will also retrieve the information for those additional Groups. This recursive scanning of Groups will continue until all Group names have been processed.
150 |
151 | Once all this information is retrieved, each of the users that were discovered during the "HCL Domino Users Scan" are crossed referenced against the Members of the Deny Access Groups that were discovered. This cross reference determines if the user is listed in a Deny Access Group. If a user's name is discovered, the User information will be updated to indicate this.
152 |
153 | To begin the Deny Access Group Scan, click the **Start Deny Access Scan Now** button:
154 |
155 | 
156 |
157 | Once the Deny Access Group Scan is complete, you will be presented with the results, as shown below:
158 |
159 | 
160 |
161 | To progress to the next scan, click the **"Next"** button.
162 |
163 | ___
164 | ## Step 6 - Entitlement Tracking / User Report Tool Scan
165 | The fourth and final scan is the "Entitlement Tracking / User Report Tool Scan". This scan will look at one of the next two systems:
166 |
167 | 1. **Entitlement Tracking System**: this is a new system that was introduced in HCL Domino V12. If the client is using HCL Domino V12, this scan will always occur.
168 |
169 | 2. **User Report Tool Results**: this is a REQUIRED system that is based on the Entitlement Tracking system that is in HCL domino V12, but has been made to be backwards compatible to Domino V9.x. The user will need to download and run the User Report Tool prior to using the DLAU.
170 |
171 | Here is a link to the User Report Tool: [User Report Tool - HCL Knowledgebase Article KB0095328](https://support.hcltechsw.com/csm?id=kb_article&sysparm_article=KB0095328)
172 |
173 |
174 | The information that this scan retrieves will display the highest **Access Control List (ACL)** level that each user has to the HCL Domino environment. This is useful in determining if the user is a CCB or a CCX license user.
175 |
176 | **To begin the Entitlement Tracking Scan**, click the **Start Entitlement Tracking Scan Now** button:
177 |
178 | 
179 |
180 | Once the Entitlement Tracking Scan is complete, you will be presented with the results, as shown below:
181 |
182 | 
183 |
184 | To progress to the next screen, click the **"Next"** button.
185 |
186 | **To begin the User Report Tool Scan**, click the **Start User Report Tool Scan Now** button:
187 |
188 | 
189 |
190 | Once the User Report Tool Scan is complete, you will be presented with the results, as shown below:
191 |
192 | 
193 |
194 | To progress to the next screen, click the **"Next"** button.
195 |
196 |
197 | ___
198 | ## Step 7 - Completion of the Wizard and Review of Results
199 | Now that all scans are complete, you will be presented with a screen stating that "All Scans Are Complete", as shoen below:
200 |
201 | 
202 |
203 | To review the results of the Scans, click on the **"View Results"** button. When that button is clicked, you will be presented with the full results of the DLAU scans, as shown below:
204 |
205 | 
206 |
207 |
208 | ## Finally
209 |
210 | The figures calculated by the tool are representing your current environment configuration. However, they may not meet your future configuration, so please see [understanding the results](results.md) - if in doubt, please contact your HCL representative or open a support ticket at [HCL Customer Support](https://support.hcltechsw.com/csm)
211 |
212 | Now you can continue with reporting the results to HCL, details are described [in here](reporting.md)
213 |
214 |
215 | {: mx-auto }
--------------------------------------------------------------------------------
/docs/changelog.md:
--------------------------------------------------------------------------------
1 | ---
2 | layout: default
3 | title: "CHANGELOG"
4 | nav_order: 8
5 | description: "Change Log"
6 | has_children: false
7 | has_toc: true
8 | ---
9 |
10 | 15 | Table of contents 16 |
17 | {: .text-delta } 18 | 1. TOC 19 | {:toc} 20 |Change Log
11 | All notable changes to this project will be documented in this file. 12 | 13 |
14 |
21 |
22 | ___
23 | ## UPDATES INCLUDED IN V1.2.7
24 |
25 | {: .update }
26 | CCX users will be displayed with empty if CCX user count is zero. This ensures complete visibility of all types of users.
27 |
28 | {: .update }
29 | The summary report will now displays list of Domino servers in which entitlement tracking is not running as well. This provides more comprehensive reporting data.
30 |
31 | {: .update }
32 | User Interface update: Customer name, Customer ID, and Domino DOMAIN fields have been moved to the top of the report for more legibility.
33 |
34 | {: .fix }
35 | DNEXT-29998 - SPR: MOBNDB8K7J – DLAU was not reporting flat users correctly.
36 |
37 | {: .fix }
38 | SPR: HNAKDFABUJ – Fail with an overflow error when processing large number of servers.
39 |
40 | ___
41 | ## UPDATES INCLUDED IN V1.2.6
42 |
43 | {: .fix }
44 | [GitHub Issue #79](https://github.com/HCL-TECH-SOFTWARE/domino-license-analysis-utility-DLAU/issues/79) - "External Org" users getting improperly categorized as Known Guests
45 |
46 | {: .fix }
47 | [GitHub Issue #78](https://github.com/HCL-TECH-SOFTWARE/domino-license-analysis-utility-DLAU/issues/78) - External users by organization name is case sensitive
48 |
49 | {: .fix }
50 | [GitHub Issue #72](https://github.com/HCL-TECH-SOFTWARE/domino-license-analysis-utility-DLAU/issues/72) - Directory Assistance processed differently based on sequence of loading server docs
51 |
52 | {: .fix }
53 | UI/UX Issues in Scan Wizard15 | Table of contents 16 |
17 | {: .text-delta } 18 | 1. TOC 19 | {:toc} 20 |- “Environment Scan Results” is not displaying the list of additional Domino Directories found
- “User Report Tool” Scan tab should no longer allow the user to change the location of the User Report Tool. 54 | 55 | {: .update } 56 | User Report Tool Selection Change
57 | The User Report Tool should only be enforced if the user indicates that they are calculating External Users. If they are only calculating CCB users, the User Report Tool should be optional 58 | 59 | ___ 60 | ## UPDATES INCLUDED IN V1.2.5 61 | 62 | {: .new } 63 | With DLAU V1.2.5, the new "Highest Access Level" change for External Users (CCX Licenses) now allows these users to have "Editor" ACL Access. In order to properly calculate this new level, the "User Report Tool" has now become a reuiqrement for calculating External users (CCX Licenses). Please refer to the following webpage for more details: [User Report Tool Instructions](https://opensource.hcltechsw.com/domino-license-analysis-utility-DLAU/instructions/#step-6---entitlement-tracking--user-report-tool-scan) 64 | 65 | {: .update } 66 | Change to CCX "Highest Access Level" logic to match new CCX Licensing requirements (now allowing "Editor" ACL Level for CCX licensed users) 67 | 68 | {: .fix } 69 | [GitHub Issue #74](https://github.com/HCL-TECH-SOFTWARE/domino-license-analysis-utility-DLAU/issues/74) Regression Issue: Directory Assistance "Disabled" Flag only honored when "Domain Type" is set to "LDAP" 70 | 71 | {: .fix } 72 | [GitHub Issue #71](https://github.com/HCL-TECH-SOFTWARE/domino-license-analysis-utility-DLAU/issues/71) External (CCX) Users Who Are Not Listed in Entitlement Tracking Are Being Recognized as CCB Users when selecting External Organization 73 | 74 | {: .fix } 75 | [GitHub Issue #70](https://github.com/HCL-TECH-SOFTWARE/domino-license-analysis-utility-DLAU/issues/70) Wrong categorization in "User Information" view due to spelling mistake 76 | 77 | {: .fix } 78 | [GitHub Issue #66](https://github.com/HCL-TECH-SOFTWARE/domino-license-analysis-utility-DLAU/issues/66) Known guests specified by org calculating as CCB due to missing logic 79 | 80 | {: .fix } 81 | [GitHub Issue #64](https://github.com/HCL-TECH-SOFTWARE/domino-license-analysis-utility-DLAU/issues/64) Selected Org/OrgUnit in the Known Guest Identification dialog are not marked as Known Guests. (a part of #66) 82 | 83 | {: .fix } 84 | [GitHub Issue #53](https://github.com/HCL-TECH-SOFTWARE/domino-license-analysis-utility-DLAU/issues/53) CCX not properly detected by OU/OrgSelected 85 | 86 | ___ 87 | ## UPDATES INCLUDED IN V1.2.4 88 | 89 | {: .new } 90 | DNEXT-23869 Report to include Domino server versions 91 | 92 | {: .new } 93 | DNEXT-24782 Make DLAU work with a readonly user with the appropriate rights 94 | 95 | {: .new } 96 | [Idea DOMINO-I-2537](https://hcl-software.aha.io/ideas/ideas/DOMINO-I-2537) - DNEXT-23865 Support MacOS 97 | 98 | {: .new } 99 | DNEXT-26713 Save the server versions as a reference for each scan 100 | 101 | {: .new } 102 | DNEXT-23868 Note when server access is setup to allow wildcarded usernames 103 | 104 | {: .new } 105 | [Issue #19](https://github.com/HCL-TECH-SOFTWARE/domino-license-analysis-utility-DLAU/issues/19) - DNEXT-23870 Add new export category and create directory if it does not exist 106 | 107 | {: .fix } 108 | DNEXT-26644 New version available string is missing the new version title 109 | 110 | {: .fix } 111 | DNEXT-26672 Error when dividing by zero when creating the digital signature 112 | 113 | {: .fix } 114 | DNEXT-26677 User information from primary directory is lost when they also exist in another scanned directory 115 | 116 | {: .fix } 117 | DNEXT-26710 Attempt to fix situations where user receives ERROR: Object variable not set #: 91, line: 3 118 | 119 | {: .fix } 120 | DNEXT-26795 Correct the spelling of "signing" on "signing" page 121 | 122 | {: .fix } 123 | DNEXT-26878 utility is duplicated on the Nomad page 124 | 125 | ___ 126 | ## UPDATES INCLUDED IN V1.2.3 127 | 128 | {: .new } 129 | DNEXT-26195 - Include DLAU version in the emailed report 130 | 131 | {: .fix } 132 | DNEXT-26190 - Global variable was being updated incorrectly causing incorrect error message 133 | 134 | {: .fix } 135 | DNEXT-25836, DNEXT-25837 - addressed typo and string updates 136 | 137 | {: .fix } 138 | DNEXT-26194 - Recompiled LotusScript with 32-bit compiler 139 | 140 | {: .update } 141 | DNEXT-25997 - added additional logging output behind Notes.ini *DLAU_VERBOSE_MODE=1* 142 | 143 | ___ 144 | ## UPDATES INCLUDED IN V1.2.2 145 | 146 | {: .new } 147 | DNEXT-23866 - Check for new version 148 | 149 | {: .new } 150 | DNEXT-24943 - Include user names from entitlement tracking in user counting 151 | 152 | {: .fix } 153 | DNEXT-24797 - Fix string in dialog that warns the user they don't have appropriate rights to the names.nsf 154 | 155 | {: .fix } 156 | DNEXT-24798 - Fix string in dialog that warns the user they don't have the appropriate role in the Domino Directory 157 | 158 | {: .fix } 159 | [Issue #50](https://github.com/HCL-TECH-SOFTWARE/domino-license-analysis-utility-DLAU/issues/50) - DNEXT-25113 Observation information is not accurate when non-Domino LDAP is used as authentication 160 | 161 | {: .fix } 162 | DNEXT-25221, DNEXT-25419 - Admin server is changing when additional directories are identified 163 | 164 | {: .fix } 165 | DNEXT-25782, DNEXT-25635 - Incorrect error message due to improper casing on file naming comparison 166 | 167 | {: .fix } 168 | DNEXT-25742 Corrected misspelled word 169 | 170 | {: .update } 171 | *DLAU_VERBOSE_MODE=1* with the Notes.INI set before beginning the scan, the logging has been enhanced to capture the output in the scan log as well as logging additional information. 172 | ___ 173 | ## UPDATES INCLUDED IN V1.2.1 174 | 175 | {: .new } 176 | DNEXT-23861 - Added support for scanning Directory Assistance on all servers in the environment. 177 | 178 | {: .new } 179 | [Idea Domino-I-2499](https://domino-ideas.hcltechsw.com/ideas/DOMINO-I-2499) - DNEXT-23784 - The Customer Name, HCL Customer, etc. can now be stored in a configuration document. 180 | 181 | {: .new } 182 | DNEXT-24589 - Added the ability to output logging to the status bar to give the scanner an improved experience to understand progress. Set *DLAU_VERBOSE_MODE=1* in the Notes.INI before beginning the scan. 183 | 184 | {: .new } 185 | DNEXT-23852 - Version of DLAU is now included in the printable report as well as it is stored on the results of each scan to see how scans change over releases. 186 | 187 | {: .new } 188 | DNEXT-23855 - Addressing an issue when Domino is used as LDAP server 189 | 190 | {: .update } 191 | [Issue #54](https://github.com/HCL-TECH-SOFTWARE/domino-license-analysis-utility-DLAU/issues/54) - DNEXT-24094 - Logging improvements have additional spaces around each functional area of scanning for visual improvements. 192 | 193 | {: .fix } 194 | [Issue #34](https://github.com/HCL-TECH-SOFTWARE/domino-license-analysis-utility-DLAU/issues/34) - DNEXT-23853 - Export CCB Users does not provide content 195 | 196 | {: .fix } 197 | [Issue #39](https://github.com/HCL-TECH-SOFTWARE/domino-license-analysis-utility-DLAU/issues/39) - DNEXT-23780 - Clicking on "Deny Access Users" opens the view "dagroups" instead of "UserInfo" 198 | 199 | {: .fix } 200 | [Issue #41](https://github.com/HCL-TECH-SOFTWARE/domino-license-analysis-utility-DLAU/issues/41) - DNEXT-23856 - Issues with Directory Catalog not in root directory 201 | 202 | {: .fix } 203 | [Issue #46](https://github.com/HCL-TECH-SOFTWARE/domino-license-analysis-utility-DLAU/issues/46) - DNEXT-23854 - Bug when DA is not trusted for credentials 204 | 205 | {: .fix } 206 | [Issue #47](https://github.com/HCL-TECH-SOFTWARE/domino-license-analysis-utility-DLAU/issues/47) - DNEXT-23857 - External (CCX) Users Who are not listed in Entitlement Tracking are being recognized as CCB Users 207 | 208 | {: .fix } 209 | DNEXT-23771 - Clicking on the pop-up help does not work and is missing in certain situations. 210 | 211 | {: .fix } 212 | DNEXT-24588 - UI shifts when selecting an entry in the "Observations" field on the results page if there is a value that is too long 213 | 214 | {: .new } 215 | [Issue #29](https://github.com/HCL-TECH-SOFTWARE/domino-license-analysis-utility-DLAU/issues/29) - DNEXT-24491 Server names are reported incorrectly in an Observation 216 | 217 | ___ 218 | ## UPDATES INCLUDED IN V1.2.0 219 | 220 | {: .new } 221 | DLAU is now shipped as a template 222 | 223 | {: .new } 224 | DLAU is now signed by Open Source Template/Domino Development 225 | 226 | {: .update } 227 | Modified non-warranted license included 228 | 229 | ___ 230 | ## UPDATES INCLUDED IN V1.1.6 231 | 232 | {: .fix } 233 | Due to a failing LotusScript Method, the time difference calculation of when the user's Notes Certificate is expiring was not functioning correctly if the Notes Certificate expiry date is more than 69 years into the future. 234 | 235 | ___ 236 | ## UPDATES INCLUDED IN V1.1.5 237 | 238 | {: .update } 239 | The methods for indicating the version of DLAU has changed. In DLAU, there is now a Shared Field that is used for displaying the DLAU version. 240 | 241 | {: .fix } 242 | The User Interface for the list of Observations and their decrpitions/instructions has been adjusted to provide more room for the descriptions/instructions. 243 | 244 | {: .fix} 245 | An adjustment has been made to the User Information scan to accommodate for Person documents that were created in a background process that do not contain all Field values that are expected. 246 | 247 | {: .fix} 248 | The Field Description popup has been adjusted to provide proper messages for CCB and CCX user counts. 249 | 250 | ___ 251 | ## UPDATES INCLUDED IN V1.1.4 252 | 253 | {: .new } 254 | Each of the DLAU Scans will now log any errors that are encountered during the scan process. If a critical error is encountered, the user will be provided the opportunity to view the Scan Log. 255 | 256 | {: .update } 257 | For the message asking the user if they has External Users / Known Guests, the buttons on the message have been changed to "Yes" and "No" to reduce user confusion. 258 | 259 | {: .fix } 260 | During the User Count Calculations, there has been identified a LotusScript Regression Issue in newer versions of the Notes Client (V12.0.2) where a call to obtain a collection of documents can fail to return the proper results if more than one Search Key is used. 261 | 262 | ___ 263 | ## UPDATES INCLUDED IN V1.1.3 264 | 265 | {: .fix } 266 | In the Scan Wizard, if the "Cancel' button is pressed prior to the completion of all scans, the user is presented with an error message "Division by zero". 267 | 268 | {: .fix } 269 | If there are no CCX or Known User counts, the Report page may cause a calculation error. 270 | 271 | ___ 272 | ## UPDATES INCLUDED IN V1.1.2 273 | 274 | {: .fix } 275 | If all different User License types are not captured in a Domino environment, the Report page may cause a calculation error. 276 | 277 | ___ 278 | ## UPDATES INCLUDED IN V1.1.1 279 | 280 | {: .new } 281 | There is now a new set of user calculations included on the "Scan Results" page to display the various User Counts for active users over a 1-year (365 days) time period. 282 | 283 | {: .fix } 284 | When prompted for "External User Calculations" during the HCL Domino Environment Scan, the list of Orgs/OrgUnits was not being populated properly due to an incorrect listing in the completed Domino environment scan. 285 | 286 | {: .fix } 287 | If a user's name in their Person document contains a quote ( " ), the Deny Access Groups scan would fail with a LotusScript error. 288 | 289 | ___ 290 | ## UPDATES INCLUDED IN V1.1.0 291 | 292 | {: .new } 293 | On the "Printable Report" screen, add the ability for the user to send the results to HCL using a specially formatted email. 294 | 295 | {: .new } 296 | Calculate "Known Guests" in a similar fashion to how "CCX Users" are calculated, with the "Highest ACL Level" check to ensure that the user has ACL Level "Reader" or lower 297 | 298 | {: .update } 299 | Adjust "User Information" View to show the User Categories ("CCB Users", CCX Active Users", "CCX Inactive Users", "Known Guest Users") 300 | 301 | {: .update } 302 | Update the "Printable Report" screen to include the "CCX Inactive Count" and "Known Guests Count" 303 | 304 | {: .update } 305 | On the "Printable Report" screen, update the instructions for use and message for US Federal Government customers 306 | 307 | {: .update } 308 | Sort the Members List on the Deny Access Group documents 309 | 310 | {: .fix } 311 | For the "External Users" dialog, ensure that values are selected if the user clicks the "OK" button 312 | 313 | ___ 314 | ## UPDATES INCLUDED IN V1.0.12 315 | 316 | {: .update } 317 | Remove any reliance on JavaScript code. This is to allow organizations that have user Policies that block usage of JavaScript in Notes applications 318 | 319 | {: .update } 320 | The DLAU is now backwards compatible to Lotus Notes V7.0.2 321 | 322 | {: .update } 323 | Modify the "Required Fields" for the "Printable Report" to make user information optional (GDPR Compliance) 324 | 325 | {: .fix } 326 | Adjust the layout of the "Printable Report" so that it shows the correct User Counts dependent on how the DLAU was run (with or without CCB/CCX counts) 327 | 328 | {: .fix } 329 | Modify the method for generating the final User Counts to occur at the end of the scanning process so that the User Counts are based on the final results, not partial results 330 | 331 | 332 | ___ 333 | ## UPDATES INCLUDED IN V1.0.11 334 | 335 | {: .update } 336 | Remove "# Members" column from "Deny Access Groups" View to lessen the confusiojn between the # of user names listed in the Deny Access Group versus how many Deny Access Users were discovered in the Domino environment 337 | 338 | {: .update } 339 | Add a disclaimer to the "Printable Report" screen for US Federal Government clients indicating who to limit sharing the results of the DLAU with 340 | 341 | {: .update } 342 | Add a message to the "Scan Results" screen when 1 or more Security Observations are discovered 343 | 344 | {: .update } 345 | Update the "Printable Report" screen to include the "CCX License Count" 346 | 347 | {: .update } 348 | Modify method for displaying the number of Deny Access Groups that are captured in the DLAU 349 | 350 | {: .fix } 351 | The labels for CCB Users, CCX Active Users, and CCX Inactive Users were being displayed when those calculations are not being performed 352 | 353 | {: .fix } 354 | When calculating "Mail Users" the DLAU was not checking if the Domino Mail server that the user was configured for is an Active Domiuno server 355 | 356 | {: .fix } 357 | The DLAU was reporting that a LDAP Directory was in use when the configured LDAP Directory was disabled 358 | 359 | {: .fix } 360 | For Pre-V12 Domino environments, the "User Report Tool" area on the "Scan Results" screen was displayed with blank values when the "user Report Tool" was not selected 361 | 362 | {: .fix } 363 | Users were receiving a sporadic "Object Variable Not Set" error when attempting to set a value onto the Scan Results controlling document 364 | 365 | {: .fix } 366 | If a Domino server document had a carriage return in the "Server Name" field, the DLAU would display an empty Domino server name in the "Observations" list 367 | 368 | ___ 369 | ## UPDATES INCLUDED IN V1.0.10 370 | 371 | {: .new } 372 | The DLAU can now differentiate between Complete Collaboration for Business (CCB) and Complete Collaboration for External Users (CCX). New values are now displayed on the "Scan Results" page with a breakdown of each license type 373 | 374 | {: .update } 375 | the "Previous Results" page has been updated to reflect the new CCB & CCX calculations 376 | 377 | {: .fix } 378 | A sporadic hang and eventual shut down of the HCL Notes client was occurring during the question dialog about External Users. The display of the dialog has been moved to later in the logic to stop the Notes Client issues 379 | 380 | {: .fix } 381 | An incorrect message was being displayed on the Printable Report page which indicated that an LDAP directory was in use when no LDAP Directories are configured 382 | 383 | {: .fix } 384 | The "User Information Export" was not working when a subset of the User data was selected for export 385 | 386 | {: .fix } 387 | On the "Observations" details page, there were labels showing for a programmatic tabbed table in the UI when they should be non-visible 388 | 389 | {: .fix } 390 | When viewing the Printable Report, when the user is asked for their "Client Information" the functionality would allow the user to progress without entering their information. This has changed to enforce the entry of the information prior to seeing the printable report 391 | 392 | {: .fix } 393 | There was a sporadic failure in completing the Scan Wizard in very specific situations if the User Report Tool Output was not indicated for older Domino environments 394 | 395 | ___ 396 | ## UPDATES INCLUDED IN V1.0.9 397 | 398 | {: .update } 399 | Numerous minor UI/UX changes, including better UI spacing to fit smaller resolution screens and a new application icon which uses the resources available in teh "HCL Domino Design Guide" 400 | 401 | {: .update } 402 | The version numbering system that is now being used adheres to the Versioning infomration found on the main page of this site 403 | 404 | {: .fix } 405 | If the HCL Domino servers each have different Directory Assistance Catalogs and/or there are multiple Directory Assistance Configurations which point to the same Domino Directory, but are on separate Domino servers, the DLAU was scanning those Domino Directories miultiple times. A correction to the scan has beendesinged to ensure that only one instance of a Domino Directory is added to the scanning list 406 | 407 | --- 408 | ## UPDATES INCLUDED IN V1.0.0h 409 | 410 | {: .new } 411 | This version now indicates the number of Domino Mail Users that are configured in the Domino directories if they are also an Authorized User 412 | 413 | {: .new } 414 | If there are LDAP Directories configured in the Directory Assistance Catalog, a new Observation is captured, and an On-Screen message is displayed to the user stating that the utility currently does not support scanning of LDAP Directories 415 | 416 | {: .update } 417 | The original Base64 Script Library has been removed. This is in preparation for the utility to be placed into an Open-Source Repository and to follow our rules for the Apache 2.0 License 418 | 419 | {: .update } 420 | When scanning the HTTP and LDAP Port Settings on the Domino server documents, we now also check to see if the HTTP / LDAP port is enabled. If it is not enabled, then we ignore the additional check to see if those ports have the option "Enforce server access settings" enabled 421 | 422 | {: .fix } 423 | In HCL Notes Client (64Bit version only) the NotesTimer event would crash the HCL Notes Client if it was triggered while a Dialogbox was being displayed on the user's screen 424 | 425 | ___ 426 | ## UPDATES INCLUDED IN V1.0.0g 427 | 428 | {: .fix } 429 | An issue was introduced in the new Re-signing functionality that would present an error after the design was resigned 430 | 431 | ___ 432 | ## UPDATES INCLUDED IN V1.0.0f 433 | 434 | {: .new } 435 | On the initial page that is presented with instructions for re-signing the design, there is now functionality to re-sign the design even if the user does not have access to a Domino Designer or Domino Administrator client 436 | 437 | {: .update } 438 | UI/UX - some of the wording for the Information Popup Messages to better clarify what each set of information is presenting to the user 439 | 440 | {: .fix } 441 | A regression issue was introduced that ignored an open environment if an HCL Domino server did not have secured HTTP and / or LDAP ports 442 | 443 | ___ 444 | ## UPDATES INCLUDED IN V1.0.0e 445 | 446 | {: .update } 447 | UI/UX - the categorization of the "User Information" view has been changed to better display users who have access to all Domino servers and users who can only see a subset of the Domino servers 448 | 449 | {: .fix } 450 | if an organization utilizes the "Alternative Name" field on the Person documents, those Person documents would be captured in DLAU multiple times 451 | 452 | ___ 453 | ## UPDATES INCLUDED IN V1.0.0d 454 | 455 | {: .fix } 456 | If an organization has a large number of Groups in their Domino Directory (more than 65,536 Groups), the Deny Access Scan would fail. the logic for listing all Group Names has been adjusted to now accommodate up to 1,000,000 Groups in a single Domino Directory 457 | 458 | ___ 459 | ## UPDATES INCLUDED IN V1.0.0c 460 | 461 | {: .new } 462 | the User Information documents now capture if the User is a Notes Mail user. This data is not displayed at this time, but will be used in a near future release that will assist in calculating Notes Mail versus Notes Application users for proper Domino Server licensing purposes (e.g., Utility Server versus Mail Server versus Enterprise Server) 463 | 464 | {: .new } 465 | If there is a User that is identified as having access to some, but not all, Domino servers, they are now identified as an "Authorized User - Partial Deny Access". They will now be in a different category in the "User Information" View and still count towards the "Authorized User" count 466 | 467 | {: .new } 468 | On the User Information documents, when the document is opened there is now a new area titled "Server Accessibility" that lists all available Domino servers, the Domino servers that the user can access, and the Domino servers that they CANNOT access based on the Deny Access Group scans that are performed 469 | 470 | {: .fix } 471 | changed how the License Tracking System is identified as "running" - previously it looked for License Tracking results per available server. Now, the scan will look at the settings in the Domino Directory to see if License Tracking is enabled for each available server. this was changed for environments that have License Tracking enabled for a Domino server but there are no results for the Domino server available 472 | 473 | {: .fix } 474 | In some environments that have a large number of Observations, the Log document within DLAU that lists all Observations was encountering a data limit (32kb) of values. This has been corrected to allow much more data to be stored on the Log document 475 | 476 | {: .fix } 477 | If the client's Domino servers had a mix of different Deny Access names listed on the Security tab of the Server documents (e.g., Sever A has 2 Groups listed, Server B has 1 Group listed, Server C has 3 Groups listed) the Deny Access User calculation was not occurring correctly 478 | 479 | {: .fix } 480 | The list of Domino Servers that are using a specific Deny Access Group was not fully listed on the Deny Access Group document within the utility --------------------------------------------------------------------------------