To solve the issue a PowerShell script has been prepared. The script requires Powershell 3.0 or later and needs to be run on the Core Server.
The script has 3 sets of parameters:
1. the "Encode" set with only one parameter
"-encodepassword" which allows encoding the password used to connect to the share where an archive may be located
2. the "Local" set with the following specific parameters:
"-local" which is a switch indicating that the archive to be checked is located on a local volume
3. the "Network" set with the following specific parameters:
"-network" which is a switch indicating that the archive to be checked is located on a network share
"-user" which takes as value the user name for the credentials needed to access the network share hosting the archive
"-encodedpassword" which takes as value the previously encoded password for the credentials needed to access the network share hosting the archive
Additionally, there are quite a few parameters that belong to both the "Local" and the "Network" parameter sets:
"-path" which is the path to the archive location
"-checks" which takes as value an array of the checks performed against the archive. By default all possible checks are set; they are "Structure","IndexOffsets","Checksum","DataSize"
"-jobcount" which allows changing the caption for the archive check job logged on the core. By default this is 0 (zero). The value can be any integer number.
"-port" which specifies the service port. The default value is 8006.
The script is attached to this KB