DocuNote is a document management system, which uses Microsoft SQL Server for storage of meta data, rights and other information, connected to documents and the use of a document manage system.
A standard Windows File Share is used for storage of documents. Windows File Share is only available via an application server, since it is locked due to user rights and not directly admissible. In DocuNote, this File Share is called ”document silo” or ”document store”.
When a user wishes to view or edit a document, DocuNote searches for the application server in order to deliver the document to the user. This means that the document is collected in the document silo and placed in the user’s home directory on the network. Subsequent, the document is opened by the attached application, for example Microsoft Word.
All this happens automatically, so the user only has the document delivered via the DocuNote user interface. It is the same process, when the user wishes to end the editing of a document, just the other way around.

Buzzwords
| Document Management System | Microsoft SQL Server | Active Directory Integration |
|---|---|---|
| Single Sign-On | SSL Wildcard Certificate | Document Silo |
| Text Extraction Service | IFilter Technology | Outlook Add-in |
| Desktop Client | Automatic Updates | OCR Recognition |
| Workflow Module | Virtual Environments | Video Conversion |
| Mixed Authentication Mode | Roaming Profiles | Product Life Cycle |
Servers and clients must be within the same domain, in order for document management to take place. If using several domains, analysis of AD forest, trusts etc. is required.
Users and groups used in DocuNote, must be maintained in Active Directory, since DocuNote does not have separate user and group maintenance. Selected OU from AD is synchronized for DocuNote. Home directory in AD must be filled out by the users, since it is used during document management.
The customer must provide a wildcard SSL certificate for the websites needed for the DocuNote web server sites. The certificate is required for DocuNote Web, DocuNote Mobile and DocuNote API, both internally and in DMZ. The certificate is also mandatory for the site serving the DocuNote Desktop Client.
Examples of host headers for needed certificate: web.customer.dk, mobile.customer.dk, api.customer.dk
DocuNote Text Extraction Service uses Microsoft IFilter technology.
Third party software, installed with Text Extraction Service:
Windows 11 with at least 8 GB RAM, recommended 16GB RAM and a minimum screen resolution of 1280 in width, and 768 in height. Requires 400MB free memory for DocuNote and Outlook-add-in. The client must be logged on AD, since a Single Sign On for DocuNote is made from the Windows Account. The client must further have filled out the field ”home directory” in AD, used by document management.
Visual C++ redistributable must be installed on the Windows-client, to support the build in PDF viewer in DocuNote. https://www.microsoft.com/en-us/download/details.aspx?id=26999
The DocuNote Desktop client can pushed to clients using msi and group policies, or using the setup.exe program.
A feature for automatic DocuNote client update can be configured. Automatic updates of the client is only possible, if the user has writing access to the folder, in which the DocuNote client is located.
Parts of the DocuNote Desktop Client, e.g. AI Chat, Quick case search, Send documentation and reports, are shown with Microsoft Edge WebView2. They require the Microsoft Edge WebView2 Runtime (Evergreen) on the machine running the DocuNote client. Windows 11 includes the runtime. Windows Server does not, so on Citrix and Terminal Server / RDP servers it must be installed before these features work.
Install it once per server, as administrator
The installer decides by how it is started:
The winget command is not available on Windows Server by default. Instead, run the following in an elevated PowerShell on each server. It downloads Microsoft's Evergreen Bootstrapper and installs silently:
[Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12
$f = "$env:TEMP\MicrosoftEdgeWebview2Setup.exe"
Invoke-WebRequest "https://go.microsoft.com/fwlink/p/?LinkId=2124703" -OutFile $f -UseBasicParsing
$p = Start-Process $f -ArgumentList "/silent /install" -Wait -PassThru
"WebView2 exit code: $($p.ExitCode)"
Exit code 0 means it was installed (or was already present). The bootstrapper needs internet access. For a server without internet access, download the Evergreen Standalone Installer (x64) from Microsoft's WebView2 page and run it with the same /silent /install arguments, also elevated.
Check the installation
A per-machine installation shows a version number here:
(Get-ItemProperty 'HKLM:\SOFTWARE\WOW6432Node\Microsoft\EdgeUpdate\Clients\{F3017226-FE2A-4295-8BDF-00C3A9A7E4C5}' -ErrorAction SilentlyContinue).pv
No output, or 0.0.0.0, means the runtime is not installed for all users.
Updates
The runtime updates itself automatically through Microsoft Edge Update, the same way as Microsoft Edge. No DocuNote update is needed for that.