Summary: This article explains why Cayosoft Administrator has multiple Cayo.PolicyManager.exe processes running.
Applies to: Cayosoft Administrator 8.x or later
By default Cayosoft Administrator has six Cayo.PolicyManager.exe processes that are running simultaneously and one Cayo.PolicyManagerUI.exe process for Administrator Console. The process that takes up the most physical memory is the main Cayosoft Administrator Service process.
Three processes are named as full and contain a set of all opened PowerShell sessions to different systems that you use in your environment: Active Directory, Microsoft 365, Microsoft Exchange Server, Exchange Online, Teams and etc.
Two processes are named as not full and contain opened PowerShell sessions only to Active Directory and Microsoft 365.
Typically these processes consume 250MB or higher, depending on the number of enabled extensions and size of the environment. So, the minimum requirement for RAM is 16 GB, with up to 32Gb recommended on bigger environments, see Cayosoft Administrator System Requirements – Cayosoft Help Center.
RAM consumption would go up and down, depending on the rules executed by the Administrator Service and the number of objects to process. For example, many hybrid rules like AD Users | Enforce License has to pre-load all cloud users with their assigned licenses to map to on-prem user accounts and compare current licenses with the licenses configured in the rule. Analytics Collection runbook also loads a lot of data.
Also, Cayosoft Administrator has built-in protection against memory leaks. Because the product uses multiple external systems, not 100% of the executed code is controlled. Thus, a certain control has to be embedded over RAM usage to keep Administrator Service responsive in situations when some function or rule would start to consume too much RAM. Service checks its own RAM consumption against total available physical RAM and if consumption rises above a certain threshold, it restarts PowerShell sessions or its own main Service process.