You shared the subfolder \SMS from the ServerProtect program folder and tried to do silent installation from there by executing the following:
\\ServerName\ShareName\setup.exe -s -SMS -m"SPNT5"
The operating system on both machines, the SNTP Information Server (IS) and the target machine, is Microsoft Windows 2003. Then you observed that the setup runs for a short time (can be seen in the Task Manager), then the installation dies without any message.
After enabling ServerProtect debugging and problem reproduction, only an empty sp5db.log file (0 bytes) was created, and no SPNT.log at all.
On the other hand, the installation in non-silent mode (without "-s" parameter) works properly.
This happens because the permissions for the shared "\SMS" on the ServerProtect IS are "read (R)" for group "Everyone", which is the default in MS Windows 2003.
If you change the permissions to "read write (RW)" for group everyone, the installation will work properly. However, this is not an option for you because of high security impact.
ServerProtect 5.x uses InstallShield 12.0, while version 5.58 uses InstallShield 5.5. In Silent Install mode, InstallShield 12.0 will, by default, create a setup.log in the source folder. Therefore, if the permissions on the shared folder "\SMS" is set to read only, the log file will not be created and the installation will fail.
The creation of the setup.log file cannot be disabled, but there is a way to redirect this log to another drive/folder.
To do so, execute the following command:
\\ServerName\ShareName\setup.exe -f2c:\setup.log -s -SMS -m"SPNT5"
This way, the setup.log file will be created in drive c:\ on the target server.
The permissions for "Everyone" on the shared folder "\SMS" can now be left as default for silent installation.