Hi Stephen, perhaps this is a little different in the case of the PTPSync application. It almost doesn’t need a CSU step since it defaults to a local SQLite database for configuration and the host service’s primary purpose is to host the ptpd executable. I just used ProjectAlpha here because it was a quick service host that I was very familiar with.
Assuming a “default config” could be used, then you could basically do away with CSU for this particular application. Then all you would have are the silent switches for MSI.
That said, this might a good case for the NSSM host for something even more simple.
@mwtrigg, the actual app doing the time synchronization is the
ptpd.exe - you could even run this from a scheduled task in Windows to simplify things. The rest of the included components are just for convenience in configuration and monitoring as well as providing a Windows service wrapper.