Hi and welcome to our forums,
The solution you approached (to just replace the service executable file) is not recommended. You would need to make major changes in the package that would lead
to creating a setup package which does not follow the industry standards.
Basically what happens is that most applications have the services installed under the LocalSystem account. If your application requires another user account and this
option is often changed by the users after they install the application then you should
allow the installer to configure the user account for the service.
You could add a new dialog in the package that would capture the username and password from the users and also another option (default one) where you would say the service installs
under LocalSystem account. In that dialog you would store in two public properties the input captured by the user, so if he never inputs anything and the properties
are empty the service will automatically install under the LocalSystem account.
To have the user and password remembered for future upgrades all you need to do is to
set the properties as persistent when you create them in Install Parameters page.
This will make the installer automatically use the username and password provided in the previous installs during an upgrade so the users will not have to provide those details anymore,
they will be filled in by default.
Regards,
Bogdan
FOLLOW US
Get the latest news in Application Packaging