System Manager Behavior and Requirements

The System Manager (ASM) serves as the central control point for visability, handling configuration, coordination, and system-level services. Unlike Display Nodes, its operation is not dependent on an active user session, which allows for greater flexibility within domain-managed environments.

Understanding this difference is important when applying domain policies and planning system behavior.

The System Manager runs critical visability services in the background as Windows Services. This means that core functionality continues to operate regardless of whether a user is actively logged in.

Because of this architecture:

• The system does not require a persistent user session
• Users can log in and out without impacting system operation
• Services continue running through reboots and normal system activity

This makes ASM more adaptable to standard IT policies compared to Display Nodes.

Unlike Display Nodes, ASM systems do not require auto-login.

In most environments:

• Screen savers and automatic lock are acceptable
• User sessions can be logged off without affecting system functionality

However, automatic logoff of system-level services must be avoided. The visability services themselves must remain active at all times, regardless of user session state.

Because ASM relies on background services, it is important to ensure those services are configured with the appropriate credentials.

In domain environments:

• Services may be configured to run under a domain account
• That account must have the necessary permissions to operate reliably
• Credentials should be managed in accordance with organizational policies

This becomes especially important in environments where user sessions are not persistent.

In deployments where ASM is part of a clustered or high-availability environment, service-based operation becomes even more critical.

• Services must be able to start and run independently of user login
• Failover scenarios rely on consistent service availability
• Domain credentials used by services must be valid across all nodes

These environments should be validated carefully to ensure continuity of operation.

While ASM is more tolerant of standard domain policies, certain settings should still be reviewed:

• Policies that affect Windows Services
• Security policies that restrict service account behavior
• Any settings that may interrupt or disable background processes

The goal is to ensure that system services remain uninterrupted at all times.