30 September 2021
On a Citect deployment client machine that is configured to run Citect client as an application, when a deployed project version is rolled out using 'Forced' method, it restarts the Citect client process on Runtime Manager and restarts the client application as expected.
However, if the deployment client machine is configured to run Citect as a service and a deployed project version is rolled out using 'Forced' method, it restarts the Citect client process on Runtime Manager but it would not start Citect as an application.
Citect Scada All versions
This is the expected behaviour when running Citect as a service and using forced deployment, it is meant to restart the Citect runtime manager service, not the UI/application. Since, a service has no dependency on UI therefore we need to create a dependency between these two, thereby forcing UI restart after the service is restarted following forced deployment.
The workaround to achieve this is to change value of 'DeploymentNode.PackagesToKeep' to 1 in file 'C:\ProgramData\AVEVA\Citect SCADA 2018 R2\Config\SE.Asb.Deployment.Node.WindowsService.exe.config