System Maintenance Service

A combination of the following flags:

Specifies which days the maintenance service is allowed to execute maintenance operations.

Usage

• Select one or more days to control the maintenance schedule.
• By default, all days are selected, allowing daily maintenance.

Example

• To run only on weekends: select 'Saturday' and 'Sunday'.

Impact

• Maintenance will only be performed on the selected days.
• Unselected days will be skipped, even if a run time matches.

Defines the specific time(s) of day when maintenance operations should be performed.

Usage

• Enter one or more times in 12-hour or 24-hour format, separated by commas for multiple times.
• Example: 12:00 AM or 2:00 AM, 2:00 PM

Best Practices

• Schedule maintenance during periods of low activity to minimize disruption.
• Use multiple times for environments that require more frequent maintenance.

Impact

• Maintenance will be triggered at each specified time on the selected days.
• Incorrect values may prevent maintenance from running as intended.

Selects which maintenance operations will be executed during each scheduled run.

Usage

• Use the options editor to enable or disable specific maintenance actions, such as index rebuilding, log purging, or batch cleanup.
• Each option is described in the UI and can be tailored to your repository's needs.

Best Practices

• Enable only the actions required for your environment to avoid unnecessary operations.
• Review options periodically as repository requirements evolve.

Impact

• Only the selected actions will be performed during maintenance.
• Disabling critical options may lead to database growth or performance degradation.

When enabled, anonymized usage statistics are sent to GrooperXchange as part of the maintenance cycle.

Usage

• Set to true to participate in usage analytics.
• Set to false to keep all statistics local.

Impact

• Enabling this option helps Grooper support and licensing teams monitor system health and usage trends.
• No personally identifiable information is transmitted.

Binds the Service Instance to a specific Grooper repository. This association is permanent for the lifetime of the service instance. To change the repository, uninstall and reinstall the service with the desired repository assignment.

Usage

• Select the target repository when installing or configuring the service.
• The repository must be accessible and properly configured for the service to function.

Impact

• All operations performed by this Service Instance will be executed against the selected repository.
• Changing the repository after installation is not supported; uninstall and reinstall to rebind.

Specifies the internal Windows service name used to identify the Service Instance on the target machine. This value is typically auto-generated but can be customized during installation.

Usage

• Use a descriptive name to clarify the service's function or assignment.
• The name must be unique among all Windows services on the machine.

Example

Grooper.ActivityProcessing.01

Impact

• Used by system tools and scripts to control or monitor the service.
• Changing this value after installation requires uninstalling and reinstalling the service.

Sets the friendly name shown in the Windows Services control panel and Grooper UI for this Service Instance. This name helps administrators and users identify the service's purpose.

Usage

• Use a clear, descriptive display name to distinguish this service from others.
• The display name can include the service type and instance number for clarity.

Example

Grooper Activity Processing, Instance 01

Impact

• Changing the display name updates how the service appears in management tools but does not affect its internal operation.

Can be one of the following values:

Controls the thread scheduling priority for all processing performed by this Service Instance.

Usage

• Select a priority appropriate for the server's workload.
• On workstations, use a lower priority to avoid impacting user interface responsiveness.

Options

• Values are from the ThreadPriority enumeration, such as Normal, BelowNormal, or AboveNormal.

Impact

• Higher priorities may improve processing speed but can affect other applications.
• Lower priorities reduce the risk of interfering with interactive users.

Specifies the Windows user account used to run the Service Instance. This account must have the necessary permissions for service operation.

Requirements

• Logon as Service permission on the target machine.
• Access to the Grooper database (if using Windows authentication).
• Access to any required file store locations.

Usage

• Enter the account name in the format DOMAIN\\Username or .\LocalUser.
• Avoid using built-in accounts unless required by your environment.

Impact

• The service will run with the permissions of the specified account.
• Insufficient permissions may prevent the service from starting or accessing required resources.

Sets the password for the specified user account. This value is stored securely and is required for non-built-in accounts.

Usage

• Enter the password for the account specified in 'User Name'.
• The password is encrypted and not displayed in the UI.

Security

• Ensure the password is kept up to date if the account's credentials change.
• Only users with administrative privileges should be allowed to view or modify this property.

Impact

• Incorrect passwords will prevent the service from starting.