Mitigate slowness or timeouts when importing Active Directory .actdir files

[#1]

This article contains instructions and scripts that you can use to help mitigate the following known issue: Active Directory data may not be updated due to the import process for .actdir files timing out (or taking a long time) at the "Reconciling Computers" or "Reconciling Organizations" step (IOJ-2250105)

Delete records of inactive computers in Active Directory

Data pertaining to inactive computers in Active Directory should be deleted from the inventory database. Deleting a large number of computers can take a long time, potentially leading to database timeouts occurring while .actdir files containing Active Directory data are imported.

Use the attached ManualComputerCleanupOnDN.sql script to manually delete computer data to mitigate this problem when it occurs.

1. Ideally, pick a time to perform the following steps when no Active Directory data imports are running and when the inventory import process reading from the FlexNet Manager Suite inventory database is not running.
   
   
2. Modify the distinguished name DC=x,DC=x,DC=x on line 2 in the ManualComputerCleanupOnDN.sql script to reflect the actual distinguished name of your domain.
   
   
3. Execute the script using a tool such as SQL Management Studio.
   
   Be aware that this process can take a long time (hours or even days) to complete if there are many thousands of records to be deleted. The process can be safely canceled at any point and later restarted without losing work.

Updated ReconcileComputers stored procedure

The attached ReconcileComputers_NoBatch (2019R2 or later).sql file contains an update to the dbo.ReconcileComputers stored procedure that you can use with FlexNet Manager Suite 2019 R2 or later installations. This update can help reduce the chance of these issues occurring in the future once an initial manual cleanup is performed by changing the import process to delete records one at a time instead of in large batches.

To apply the update:

1. Take a backup of the dbo.ReconcileComputers stored procedure so that you can revert the changes if needed.
   
   
2. Execute the ReconcileComputers_NoBatch (2019R2 or later).sql script against the inventory database.

[russellwood]

Have implemented both and still times out.

Type: 'System.Data.SqlClient.SqlException'
Message: 'Execution Timeout Expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
Operation cancelled by user.
Reconciling Computers in DC=global,DC=x,DC=x,DC=com'
Source: '.Net SqlClient Data Provider'
Error Number: '-2'
State: '0'
Procedure: ''

[schandran]

This needs to have an additional step. After executing the "ReconcileComputers_NoBatch (2019R2 or later).sql" file, we need to execute the below queries.

DECLARE @Domain_ID int
SELECT @Domain_ID = OrganizationID FROM Domain where DN = 'DC=x,DC=x,DC=x'

Exec ReconcileComputers @Domain_ID

This will execute the procedure that is created by the "ReconcileComputers_NoBatch (2019R2 or later).sql".