Repository navigation
Releases
v2.0.1
Stable Windows release from exact commit 8392bcf.
Reviewed changelog: https://github.com/ffworker/signaturee-win/blob/v2.0.1/CHANGELOG.md
Manual evidence: #51 (comment)
Signaturee v2.0.0 (Windows)
Signaturee v2.0.0 — Windows
First validated Windows Server 2025 release with a self-hosted web UI, Node.js backend and Windows PowerShell Active Directory signature generator.
Highlights
- Single- and multi-user Outlook signatures in HTML, TXT and RTF.
- LibreOffice as the default headless RTF converter. No Word license required. Word-COM remains an opt-in legacy engine, never an automatic fallback.
- Local and network (SMB/UNC) signature output. Under the SYSTEM task, remote share access normally uses the domain machine account (DOMAIN\VMNAME$).
- Generation and Classic Outlook HTML rendering validated on a freshly prepared Windows Server 2025 VM.
Installation
Download signaturee-win-v2.0.0.zip and verify SHA256SUMS.txt. Follow Prepare your VM (Windows Server 2025) and Windows release and rollback guidance.
ZIP contains application sources/scripts, not Node.js, LibreOffice, customer templates, credentials or runtime databases. Windows PowerShell 5.1, Node.js 22.13+, RSAT ActiveDirectory and system-wide LibreOffice are prerequisites. This is not an EXE/MSI; Git-based update scripts do not apply to ZIP installations.
Supported scope and limitations
- Classic Outlook HTML signatures were visually checked. Validate RTF logos separately if Rich Text email formatting is required.
- Standard web workflows require Active Directory for user/group lookup. CSV worklists select AD users; they are not an independent employee-data source.
- Linux/Docker is not part of v2.0.0. This release establishes the stable Windows baseline for future Linux support in the same repo.
- No automatic rollback for upgrades. Back up all configuration, templates, databases and output state.