Content:
Overview
Starting from the 10.3 version, Suspend Tool has been migrated to Administrator Service with significantly improved functionality. For details, please see this article about New Suspend Configuration.
After upgrading to 10.3.0, nothing changes and the legacy suspend functionality keeps working due to the implemented co-existence of old and new suspend: old automation rules and Web actions use legacy Suspend policies, new suspend automation rules fail with the error that they don't work if in Active Directory extension 'Use Modern Suspend Rules and Configurations' is set to No.
It is up to you when you decide to switch to the modern Suspend. But switching to modern suspend means you must redo your suspend rules and configurations.
After upgrading the Suspend Tool, it will show a banner in ADUC: the Suspend application is now a legacy product that will not receive any updates and support. You can continue using this suspend application, but for fully supported and enhanced suspend functionality use the suspend rules inside Cayosoft Administrator.
Video Tutorial
In this video, you will learn what steps should be performed before you start using the New Suspend functionality.
Scenario: Upgrade
- After the upgrade in the Active Directory extension 'Use Modern Suspend Rules and Configurations' is set to 'No' by default.
- Legacy Suspend rules configured in the previous versions continue to work as they have.
- Modern Suspend 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:
- 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
- In the Active Directory extension 'Use Modern Suspend Rules and Configurations' is manually set to 'Yes'.
- Legacy Suspend rules stop working and fail with errors except for the object retention and Suspend reporting rules.
- New Suspend rules work without errors.
- Web actions for suspend and undo use a new suspend path.
- Process scheduled suspend operations rule is scheduled for daily execution.
- Web actions are now tied to new default Suspend configurations and use them for suspend.
- Scheduled suspends performed in legacy Suspend are no longer processed, but can be viewed via the legacy reports.
- To process them they should be re-suspended manually using New Suspend functionality.
- Undo suspend still works on both old and new objects, depending on how it was suspended.
- Web UI shows suspended objects status for objects suspended with both legacy and modern Suspend.
As a result, you suspend users, groups, and computers using the new Suspend flow. Undo suspend still works on 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.
- 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:
- 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 and how they behave after the upgrade
Rule or Action | Upgraded | After Upgrade | After switchover | |
---|---|---|---|---|
AD Suspend | ADUC standalone programe | Yes | Show legacy no longer supported banner | Same as after 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 | Rule continues to work without change | Running rule results in error, use new rule instead | |
AD Users | Suspend Expired AD Users | No | Rule continues to work without change | Running rule results in error, use new rule instead | |
Text file (SQL; Oracle) | Suspend AD Users | No | Rule continues to work without change | Running rule results in error, use new rule instead | |
AD Groups | Suspend Empty Groups | No | 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 | Rule continues to work without change | Running rule results in error, use new rule instead | |
Text file (SQL; Oracle) | Suspend Office 365 Users | No | Rule continues to work without change | Running rule results in error, use new rule instead | |
Scheduled Suspend | AD Groups | Process Scheduled Suspends | No | Rule continues to work without change | Running rule results in error, use new rule instead |
AD Users | Process Scheduled Suspends | No | Rule continues to work without change | Running rule results in error, use new rule instead | |
AD Groups | Report on Scheduled Suspend Operations | No | Rule continues to work without change | Continues to work, showing legacy scheduled suspends | |
AD Users | Report on Scheduled Suspend Operations | No | Rule continues to work without change | Continues to work, showing legacy scheduled suspends | |
Objects Scheduled for legacy Suspend | No | Scheduled suspends are processed by above rules without change | No longer processed | |
Scheduled Delete | AD Groups | Enforce Object Retention (Delete) | No | Rule continues to work without change | Rule continues to work without change |
AD users | Enforce Object Retention (Delete) | No | Rule continues to work without change | Rule continues to work without change | |
Objects Scheduled for Deletion | No | Processed and deleted without change | Processed and deleted 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 object |
Undo Suspend 365 Web action | Yes | Upgraded web action continues to work using legacy undo | Legacy undo for legacy objects, new undo for new object | |
Scheduled Undo | AD Groups | Process Scheduled Undo Suspends | No | Rule continues to work without change | Rule continues to work without change |
AD Users | Process Scheduled Undo Suspends | No | Rule continues to work without change | 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 Microsoft 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 |
N/A, upgraded
|
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.