How Suspend™ functionality works after the upgrade to 10.3
Overview
IMPORTANT: The legacy Cayosoft Suspend™ configuration will be retired on June 1st, 2026. The legacy configuration will be removed in the product release following the retirement and will be no longer supported. The legacy Suspend rules will remain functional in older versions of Cayosoft Administrator with no support provided by Cayosoft. Migrate to the modern Suspend configuration before the retirement—refer to the following article for additional information on migration: Modern Suspend Configuration.
The Suspend™ Tool has been migrated to the Cayosoft Administrator Service with significantly improved functionality. For details, please see the following article: Modern Suspend Configuration.
After upgrading to version 10.3.0, the legacy suspend functionality continues to work due to the implemented coexistence of the old and new suspend features. Existing automation rules and web actions will still use the legacy Suspend™ policies. However, new suspend automation rules will fail with an error if the Use Modern Suspend™ Rules and Configurations setting in the Active Directory extension is set to No.
Review the following for additional information:
Switching to the modern Suspend™ is optional.
However, if you switch, you must redo your rules and configurations to align with the new functionality.
After upgrading the Suspend™ Tool, a banner will appear in Active Directory Users and Computers (ADUC) indicating that the Suspend™ application is a legacy product that will no longer receive updates or support. You can continue using this legacy suspend application, but for fully supported and enhanced suspend functionality, please use the suspend rules within Cayosoft Administrator.
Legacy Suspend™ functionality will continue to work and be fully supported in version 10.3.
However, it will be deprecated in a future release. The exact timeline for deprecation will be announced at a later date.
Video Tutorial
In this video, you will learn what steps should be performed before using the Modern Suspend™ functionality.
Scenario: Upgrade
After the upgrade, the Use Modern Suspend Rules and Configurations extension in Active Directory is set to No by default.
Legacy Suspend rules configured in the previous versions continue to work.
New Automation Rules fail with the error.
Web actions for Suspend™ and Undo Suspend™ use the legacy Suspend™ path.
The new Process scheduled suspend operations rule is not scheduled.
-
Default suspend configurations are created but not used:
AD User Suspend
AD User Undo Suspend
AD User Terminate
AD Group Suspend
AD Computer Suspend (New functionality)
Microsoft 365 User Suspend
Microsoft 365 User Undo Suspend.
Upgraded ADUC Suspend tool with new banners.
As a result, Suspend™ works entirely as it did without interruption. You cannot suspend users, groups, and computers using the new modern flow.
Scenario: Switchover to Modern Suspend after the upgrade
If the Use Modern Suspend Rules and Configurations setting in the Active Directory extension is manually set to Yes:
Legacy Suspend rules, except for object retention and Suspend™ reporting rules, will stop working and fail with errors.
New Suspend rules will work without errors.
Web actions for Suspend™ and Undo now follow the new Suspend™ path.
The Process Scheduled Suspend Operations rule is scheduled for daily execution.
Web actions are now linked to new default Suspend™ configurations and utilize them for suspending.
Scheduled suspends performed using the legacy Suspend™ feature are no longer processed, but they can still be viewed via the legacy reports. To process these, they should be re- suspended manually using the new Suspend functionality.
Undo Suspend™ still works for both old and new objects, depending on the method used for suspension.
The Web Portal displays the status of suspended objects for both legacy and modern Suspend™ methods.
As a result, you will suspend users, groups, and computers using the new Suspend flow. Undo Suspend continues to function for both old and new objects.
Scenario: New Installation
After the upgrade in the Active Directory extension Use Modern Suspend Rules and Configurations is set to Yes by default.
If you create legacy Suspend rules they will fail with errors.
The New Suspend rules work correctly.
Web actions for Suspend and Undo Suspend use the modern configurations.
Process scheduled suspend operations rule is scheduled to run once daily by default.
-
The following default Suspend configurations are created:
AD User Suspend
AD User Undo Suspend
AD User Terminate
AD Group Suspend
AD Computer Suspend (New functionality)
Microsoft 365 User Suspend
Microsoft 365 User Undo Suspend.
-
Web actions are tied to default Suspend™ configurations.
As a result, you suspend users, groups, and computers using the modern Suspend™ flow.
Suspend Rules and Actions After the Upgrade
After upgrading, all legacy rules are renamed with a "(Legacy)" suffix.
| Rule or Action | Upgraded | After Upgrade | After switchover | |
|---|---|---|---|---|
| AD Suspend | ADUC standalone program | Yes | Show legacy no longer supported banner | Same as after the upgrade |
| Suspend Web Action (immediate) | Yes | Upgraded web action continues to work using legacy suspend | Web action uses new configurations | |
| AD Users | Suspend Users | No | The rule continues to work without change | Running rule results in error, use new rule instead | |
| AD Users | Suspend Expired AD Users | No | The rule continues to work without change | Running rule results in error, use new rule instead | |
| Text file (SQL; Oracle) | Suspend AD Users | No | The rule continues to work without change | Running rule results in error, use new rule instead | |
| AD Groups | Suspend Empty Groups | No | The rule continues to work without change | Running rule results in error, use new rule instead | |
| MS365 Suspend | Suspend Web action | Yes | Upgraded web action continues to work using legacy suspend | Web action uses new flow, configurations, and scheduling |
| Office 365 Users and Guests Inactive | Suspend Users | No | The rule continues to work without change | Running rule results in error, use new rule instead | |
| Text file (SQL; Oracle) | Suspend Office 365 Users | No | The rule continues to work without change | Running rule results in error, use new rule instead | |
| Scheduled Suspend | AD Groups | Process Scheduled Suspends | No | The rule continues to work without change | Running rule results in error, use new rule instead |
| AD Users | Process Scheduled Suspends | No | The rule continues to work without change | Running rule results in error, use new rule instead | |
| AD Groups | Report on Scheduled Suspend Operations | No | The rule continues to work without change | Continues to work, showing legacy scheduled suspends | |
| AD Users | Report on Scheduled Suspend Operations | No | The rule continues to work without change | Continues to work, showing legacy scheduled suspends | |
| Objects Scheduled for legacy Suspend | No | Scheduled suspends are processed by the above rules without change | No longer processed | |
| Scheduled delete | AD Groups | Enforce Object Retention (Delete) | No | The rule continues to work without change | The rule continues to work without change |
| AD users | Enforce Object Retention (Delete) | No | The rule continues to work without change | The rule continues to work without change | |
| Objects Scheduled for Deletion | No | Processed and deleted without change | The rule continues to work without change | |
| Undo Web | Undo Suspend AD Web action | Yes | Upgraded web action continues to work using legacy undo | Legacy undo for legacy objects, new undo for new objects |
| Undo Suspend 365 Web action | Yes | Upgraded web action continues to work using legacy undo | Legacy undo for legacy objects, new undo for new objects | |
| Scheduled Undo | AD Groups | Process Scheduled Undo Suspends | No | The rule continues to work without change | The rule continues to work without change |
| AD Users | Process Scheduled Undo Suspends | No | The rule continues to work without change | The rule continues to work without change | |
| Objects scheduled for Undo | No | Processed and run through undo | Processed and run through undo |
Replacement of old suspend rules with new rules
| Old Rule or Action | New replacement rule |
|---|---|
| Suspend Web Action (AD, MS365) | Suspend Web Action (AD, MS365) |
| ADUC standalone program | AD Users | Suspend |
| AD Users | Suspend Users | |
| AD Users | Suspend Expired AD Users | |
| Text file (SQL; Oracle) | Suspend AD Users | Text file (SQL; Oracle) | Suspend AD Users |
| AD Groups | Suspend Empty Groups | AD Groups | Suspend |
| Office 365 Users and Guests Inactive | Suspend Users | Microsoft 365 Users | Suspend |
| Text file (SQL; Oracle) | Suspend Office 365 Users | Text file (SQL; Oracle) | Suspend Office 365 Users |
| AD Groups | Process Scheduled Suspends | Process scheduled suspend operations |
| AD Users | Process Scheduled Suspends | |
| AD Groups | Process Scheduled Undo Suspends | |
| AD Users | Process Scheduled Undo Suspends | |
| AD Groups | Report on Scheduled Suspend Operations | Report on Suspended AD Objects and Scheduled Operations |
| AD Users | Report on Scheduled Suspend Operations | |
| AD Groups | Enforce Object Retention (Delete) | N/A or Process scheduled suspend operations |
| AD users | Enforce Object Retention (Delete) | |
| Undo Suspend AD Web action | N/A, upgraded |
| Undo Suspend 365 Web action |
Change History
| Version | Notes |
|---|---|
| 10.3.0 | The functionality has been added to the product. |
Comments
0 comments
Please sign in to leave a comment.