Registry Changes

The PrizmDoc installer will modify the registry to increase the size of the non-interactive heap, allowing the Prizm service to create more than the default number of child processes to run its micro-services.

If the registry already contains a value greater than necessary, no changes to the registry will be made. If the registry is modified, and PrizmDoc is un-installed, the original registry values will be replaced.

Interactive Installation

A manual heap size value adjustment process is not required when the PrizmDoc Windows Server installer is running in its interactive UI mode, where it will make all of the necessary registry changes and require a system reboot.

Due to a known issue with the installer, it might not ask for a reboot after the installation, so please make sure to reboot the system manually. This issue will be addressed in the future release.

Non-Interactive Installation

In order to avoid a system reboot when installing PrizmDoc Server for Windows in non-interactive mode, such as for cloud-based systems using auto-deployment, the cloud image must have its registry modified as described below.

Registry Changes

Registry Key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\SubSystems

Value: Windows

The value is a complex, space separated set of system wide settings, one of which is named "SharedSection". This is a comma-separated string value containing 3 numeric values that may look like: SharedSection=1024,20480,768.

The third numeric value is a non-interactive desktop heap size in kilobytes, which must be set to the Heap Size Value (see table below) corresponding to the number of CPU cores in the server:

The heap size value is calculated from the default size by applying a heap size multiplier corresponding to the number of CPU cores available on the server.

The instance count indicates the number of Office document converter processes the Office Conversion service will handle when using the MSO option.