Service Accounts and Credentials

In domain-based visability deployments, service accounts are used to run system processes, support ongoing operations, and enable maintenance activities. Defining these accounts ahead of time ensures that the system operates reliably and can be supported without interruption.

visability relies on background services and system-level processes that must run consistently — regardless of user login.

Without properly defined service accounts, you may encounter:

• Services failing to start after reboot
• Loss of functionality when users log off
• Delays during support or maintenance activities

Establishing the right accounts upfront helps prevent these issues and ensures a stable operating environment.

Most deployments benefit from defining two types of domain accounts:

Administrative Account

This account is used for:

• Initial setup and system configuration
• Software installation and upgrades
• Troubleshooting and support

It should have elevated privileges and be accessible to authorized personnel during deployment and support scenarios.

Standard Service Account

This account is used for day-to-day system operation.

• Runs visability services where required
• Maintains system functionality in the background
• Does not require full administrative privileges

In many environments, this account may be configured as a managed service account.

Where supported, Group Managed Service Accounts (gMSA) are recommended.

They provide:

• Automatic password management
• Improved security and compliance
• Reduced administrative overhead

If gMSA is not available, a standard domain service account can be used, but credentials must be managed carefully.

Service accounts must have the appropriate permissions to function correctly.

Depending on the deployment, this may include:

• Access to required system services
• Permissions to run applications or background processes
• Access to installation directories (e.g., application folders)

These permissions should be reviewed and validated prior to commissioning.

Service account access is often required during support and maintenance activities.

Before deployment, ensure that:

• Credentials are securely stored and accessible to authorized personnel
• Support teams know which accounts are in use
• Onsite personnel understand how to access systems if needed (especially after reboot)

In environments where auto-login is restricted, this becomes especially important, as manual interaction may be required to restore system operation.