Distinguishing Features in Top-Tier Services

Table of Contents

Disclaimer: This post includes affiliate links

If you click on a link and make a purchase, I may receive a commission at no extra cost to you.

Service Properties

Properties

Service Name - The name that will identify your service on the target machine to all the Windows API functions.
Display Name - The service will be displayed under this name. You can localize this value.
Description - A detailed description of the selected service. You can localize this value.
Service File - The service’s source file. Use the[Browse… ] button to select it from your project files.

The Service Name, Display Name, and Description fields support Formatted references and can be edited using Smart Edit control.

Parameters

Service Type - The installed service’s type. You can choose between a Win32 service that runs in its own process and a Win32 service that shares a process.
Allow the service to interact with desktop - The service is allowed to interact with the user by showing an UI. This option shouldn’t be used for services that are installed on Windows Vista or later (Windows 7, 8.1, 10), because these services’ version lack the ability to interact with the user.
Start Type - You have the following options to start a service:
- Automatic - The service will start when starting the operating system.
- On Demand - The service will start only when the user starts it manually.
- Disabled - The service can no longer be started. It is possible to be enabled.
Error Control - Sets the system’s behaviour when the service can not start.
The service is vital for installation - The package installation is aborted if the service cannot be installed.

Context

Load Order Group - The group’s name to whom the installed service belongs. Leave this field empty if the service does not belong to a group.
Dependencies - The list of the required active applications or services needed before this service starts. Separate names in the list by [~] (with the brackets). If the service has no dependencies, then leave this field empty.
Arguments - The command line arguments that will be passed to the service when started.

Account

Start Name - The user account under which your service will run. If left empty, the service will run under the LocalSystem account. Any user account must be specified in this form:<Domain_Name>\<User_name>. For local user accounts, use a dot (.) as the domain name:.\<User_name>. For example, the built-in Administrator account can be specified like this:.\Administrator

Services which interact with the desktop can use only theLocalSystem account.

Password - The password for the service user account. LocalSystem account doesn’t have a password.
Set “Log on as a service” policy - When this option is checked, the Log on as a service policy is set for the specificed user account.

If you want to install a service for a specific user, you need to follow some explicit steps. These steps are explained in the Install a service for a custom user How-To.

For the fields of Formatted Type , use Smart Edit Control to insert reference to a file, folder or property.

In case of Merge Module projects the following attributes can be made configurable at merge time:

Name
DisplayName
ServiceType
ErrorControl
LoadOrderGroup
Dependencies
StartName
Password
Description

For more information about the resources and attributes that can be configured, please see: Configurable Merge Modules Page .

Did you find this page useful?

Please give it a rating:

Thanks!

Report a problem on this page

Information is incorrect or missing

Information is unclear or confusing

Something else

Can you tell us what’s wrong?

Send message

Fox Useful

Distinguishing Features in Top-Tier Services