Bob Richardson retired from Cordant Inc. on 4th February 2016. Bob’s information was removed from Active Directory on the day he retired.
The example figure below summarizes the process that Provisioning Solutions used when Bob Richardson left Cordant and the corresponding user object was deleted from Active Directory on 4th February 2016.
User’s State:
The time period up until 4th February 2016 Bob Richardson was in an:
- Alive State in the Active Directory cache
- Alive State in Provisioning Solutions
On 5th February 2016, the first Active Directory Plug-in synchronization occurred after Bob Richardson had retired, and had been deleted from Active Directory. Bob was not found in Active Directory after synchronization as he had already been deleted and therefore was transitioned to:
- Tombstoned State in the Active Directory cache
- Styx State in Provisioning Solutions
Bob Richardson remained in Styx State which is a holding state in Provisioning Solutions, to ensure that there were no errors in the Active Directory synchronization. The Styx State in which Bob Richardson was held uses the default configuration setting of 10 days using the configurations setting UserTombstoneThreshold. This configuration setting is used to configure the length of time the user remains in Styx State.
On 16th February 2016, the Tombstone Threshold had been exceeded and Bob Richardson was transitioned from the holding Styx State to the Provisioning Solutions Tombstone State. The Tombstone State in this example used the default configuration setting of 180 days using the configuration setting UserTombstoneMaxAge. This configuration setting is used to configure the length of time the user remains in Tombstoned State.
Bob Richardson continues to remain in Tombstone State within Active Directory cache.
On August 3rd 2016, the 180 days Tombstone Max Age had been exceeded and Bob Richardson was deleted from Provisioning Solutions, and Active Directory.
Phone Number and Phone Number Allocation State:
During the time period until February 16 2016, the Phone Number Allocation remained as Assigned, whilst Bob Richardson was classed as Alive and in Styx State in both Active Directory cache and Provisioning Solutions. The Phone Number had an Allocation, and therefore it was in Used State.
The reason the Phone Number Allocation remained Assigned during the Styx State was to ensure that there was no error in Active Directory synchronization, therefore while Provisioning Solutions ensured that Active Directory Synchronization was working correctly, the Phone Number remained Assigned to Bob Richardson.
On February 16 2016, once Bob Richardson was transitioned to the Tombstoned State, the Phone Number was revoked automatically from Bob Richardson. The Sweeper Rule was configured in the Rules Engine run to revoke Phone Numbers for users, resulting in the Phone Number Allocation being transitioned to Tombstoned State during the next Rules Engine run. The length of time a Phone Number Allocation remains in the Tombstoned State is configured using the Pnms.DefaultTombstoneExpirationDays configuration setting. In this example the default setting of 30 days was used.
On March 18th 2016, the Phone Number Allocation was in the Tombstoned State for 30 days, the Phone Number Allocation was automatically removed and the Phone Number was released to be used again, and then the Phone Number changed to Available State.
NOTE:
The Phone Number in this example only had one Phone Number Allocation, which was the Lync Assignment for Bob Richardson. During the time that the figure illustrates the AD plug in and Rules Engine are run daily.