Operations

When deploying Cayosoft Administrator, proper configuration of ancillary components ensures system integrity, performance, and scalability.

Below are best practices and considerations for specific product components.

Post-Deployment best practices

Ensure the VM can connect securely to all required resources, such as Entra ID Connect.
Ensure the Cayosoft Administrator application is updated to the latest version post-deployment. Learn more in: Upgrading from product UI.
Regularly back up the configuration and database to avoid data loss during future updates or migrations. Learn more in: Backing up and handling Cayosoft Administrator databases .
Regularly monitor the Total Peak RAM parameter to ensure the server has sufficient memory resources for optimal performance. High memory usage can indicate the need for additional memory allocation or the optimization of rules and configurations. For details, refer to the Cayosoft Administrator processes running article.

Protect your data stored in the Cayosoft databases with an encryption key. Learn more in: Secure information stored persistently in the Cayosoft Configuration DB; Migrating Cayosoft Administrator to new server.
Always securely back up the encryption key immediately after installation.
Store the key in a secure location, separate from the database server (e.g., a hardware security module or encrypted storage).
Loss of the encryption key will make data recovery impossible.

Ensure sufficient storage capacity on the server hosting the Change History database.
Regularly monitor and back up Change History data to maintain audit trail integrity.
Use database maintenance tools to archive or purge older entries, depending on your retention policies.

Enable debug logging only when actively troubleshooting to avoid excessive log sizes.
Store logs on the designated file share (see File Storage section) to centralize access and ensure scalability.
Periodically archive or purge old logs to maintain storage efficiency.
If required, share debug logs with Cayosoft Support through a secure transfer method for issue resolution.

Stagger rule schedules. If adding another server is not immediately feasible, stagger rule execution to reduce contention for system resources during peak times.
Monitor pending operations. Track the duration of pending operations (e.g., password resets showing “operation pending” for several seconds) to identify actionable bottlenecks.