Scense Client- and Update Service installers support SVCSTART property

[Richard]

As of Scense 10 the installers (msi) for the Scense Client and the Scense Update Service support a new public property called 'SVCSTART'.
This property controls the automatic starting of the installed services.
Using this property has some advantages:

• Sometimes during a Scense Client upgrade the Scense Update Manager would indicate that the new Scense Client was successfully installed on a workstation where in reality it was not. This behavior was typically caused by the inability to start the Scense OnDemand service because of a logon failure, where after the installation was rolled back. With Scense 10, and thanks to the new SVCSTART property, the starting of the Scense OnDemand service is now separated from the actual installation making it much easier to troubleshoot, because the Scense Client software remains installed.
  
• In unattended workstation scenarios it can be undesired that the Scense Update Service or the Scense OnDemand Service is started after it is being installed, because these installations are part of a larger unattended installation procedure which should not be disturbed by any actions the Scense services would invoke.
  

The services are still configured to start at computer startup, so there's no necessity for additional configuration. Everything will be as expected after a reboot.

SVCSTART=0 will leave the installed service in the stopped state.
SVCSTART=1 will start the service as part of the installation (Default).

Here's an example of how the SVCSTART property is used:
:Install Scense Client
start /B /HIGH /WAIT %windir%\system32\msiexec.exe /i "Scense Client.msi" ODSUSER="SCENSE\Scense_ODS" ODSPASS="password" SCENSESERVER="SERVER" ALLUSERS=1 REBOOT="ReallySuppress" SVCSTART=0 /q
net start Scense_ODS