Collection Scan Stuck in Running Status
Shows how to resolve an AD, Entra ID, or Okta collection scan stuck in Running status in Netwrix Identity Recovery by updating the TaskInstances table and restarting the Task Server service.
Shows how to resolve an AD, Entra ID, or Okta collection scan stuck in Running status in Netwrix Identity Recovery by updating the TaskInstances table and restarting the Task Server service.
Resolve the Access Denied (0x80070005) error that occurs when registering the RSAT Extension in the Netwrix Identity Recovery Configuration Utility by delegating the required Active Directory write permissions.
Netwrix Identity Recovery uses several distinct accounts for installation, console access, domain and forest backup, RSAT Extension registration, and cloud tenant recovery. This article identifies each account, where it is configured, and the minimum permissions it requires.
The Recovery Configuration Utility shows "RSAT Extension: Registered" as soon as any user registers it once, but that status only reflects the forest of whoever ran the registration. This article explains why the status label can be misleading in multi-forest environments and how to verify what is actually registered.
Registering the RSAT Extension in Netwrix Identity Recovery only affects the forest of the account currently logged into the machine running the Configuration Utility. This article explains why registration does not carry over to a second domain or forest joined by a trust, and how to register it correctly in each one.