Description
Current behavior
Prior to Domino 14.5, the installer allowed the Domino Windows service to be configured to run as the LocalSystem account during installation.
Starting with Domino 14.5.x, this is no longer possible:
Specifying LocalSystem, NT AUTHORITY\SYSTEM, or NT AUTHORITY\LocalSystem causes the installer to reject the account or abort the installation.
Using SYSTEM allows the installation to complete, but the installer configures the service incorrectly by populating the This account field with the literal user name SYSTEM instead of configuring the service to run under the Local System account.
As a result, administrators must manually reconfigure the Windows service after installation.
Requested enhancement
Please enhance the Domino installer so that it recognizes the Windows LocalSystem account as a special built-in service account.
When one of the supported identifiers is specified (for example NT AUTHORITY\SYSTEM, LocalSystem, or another equivalent Windows identifier), the installer should:
configure the Domino service to use the Windows Local System account option,
not expect or require a password,
correctly configure the Windows service using the appropriate Service Control Manager API,
support both interactive installations and response file (silent) installations.
Business value
Many organizations have standardized deployment processes based on unattended Domino installations using response files.
The current behavior requires a manual post-installation step to reconfigure the Windows service, which:
prevents fully unattended deployments,
complicates automated provisioning,
introduces unnecessary administrative effort,
increases the risk of inconsistent service configurations.
Supporting LocalSystem as a special service account would restore full automation for deployments where LocalSystem is intentionally used.
