Checksum for existing packages (prior to DSM 2016.1)

Section:

Repository

Description:

To use Staging via Neighborcast, DSM must have a checksum for each package. Starting with DSM 2016.1, the system automatically calculates a checksum (HSA-256) for all packages and stores it in the additional package file package.fpi.checksum (in the original copy of the Repository only).

If you want to use Staging via Neighborcast for older packages as well, this setting must also be enabled.

Note that...

all files of all revisions must be read to calculate the checksum. The duration of this calculation depends on the number and size of the respective packages and on the speed of the hard drive and network.
the checksum is not added for packages in the repository cache of a client. Therefore, a subsequent calculation of the checksum is only recommended if existing packages are assigned to a greater extent on new computers.

Possible values:

Checksum is not generated

Checksum is generated (per revision)

Default value:

Checksum is not generated

Set during/as:

Installation
Creating the repository

Set on level:

Repository

Passed on to:

Change (via):

Repository

Reference (via):

DatabaseProperties.MigrationComputeChecksums

Reasons for change:

Notes/Warnings: