You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
> - Return to the main workflow page: [Access Analyzer Upgrade Workflow](/docs/kb/accessanalyzer/access-analyzer-upgrade-workflow.md).
24
-
> - Return to the previous section: [Access Analyzer Upgrade Workflow — Upgrade](/docs/kb/accessanalyzer/access-analyzer-upgrade-workflow-upgrade.md).
25
-
> - Proceed to the next section: [Access Analyzer Upgrade Workflow — Access Information Center](/docs/kb/accessanalyzer/access-analyzer-upgrade-workflow-aic.md).
23
+
> - Return to the main workflow page: [Access Analyzer Upgrade Workflow Articles](/docs/kb/accessanalyzer/access-analyzer-upgrade-workflow.md).
24
+
> - Return to the previous section: [Upgrading Access Analyzer](/docs/kb/accessanalyzer/access-analyzer-upgrade-workflow-upgrade.md).
25
+
> - Proceed to the next section: [Upgrading Access Information Center (AIC)](/docs/kb/accessanalyzer/access-analyzer-upgrade-workflow-aic.md).
> **NOTE:** Return to the main workflow page here: [Access Analyzer Upgrade Workflow](/docs/kb/accessanalyzer/access-analyzer-upgrade-workflow.md).
24
-
> Proceed to the next section: [Access Analyzer Upgrade Workflow — Upgrade](/docs/kb/accessanalyzer/access-analyzer-upgrade-workflow-upgrade.md).
23
+
> **NOTE:** Return to the main workflow page here: [Access Analyzer Upgrade Workflow Articles](/docs/kb/accessanalyzer/access-analyzer-upgrade-workflow.md).
24
+
> Proceed to the next section: [Upgrading Access Analyzer](/docs/kb/accessanalyzer/access-analyzer-upgrade-workflow-upgrade.md).
> - Return to the main workflow page: [Access Analyzer Upgrade Workflow](/docs/kb/accessanalyzer/access-analyzer-upgrade-workflow.md)
24
-
> - Return to the previous section: [Access Analyzer Upgrade Workflow — Preparations](/docs/kb/accessanalyzer/access-analyzer-upgrade-workflow-preparations.md)
25
-
> - Proceed to the next section: [Access Analyzer Upgrade Workflow — Post-Upgrade](/docs/kb/accessanalyzer/access-analyzer-upgrade-workflow-post-upgrade.md)
23
+
> - Return to the main workflow page: [Access Analyzer Upgrade Workflow Articles](/docs/kb/accessanalyzer/access-analyzer-upgrade-workflow.md)
24
+
> - Return to the previous section: [Preparing for Access Analyzer Upgrade](/docs/kb/accessanalyzer/access-analyzer-upgrade-workflow-preparations.md)
25
+
> - Proceed to the next section: [Completing Access Analyzer Upgrade](/docs/kb/accessanalyzer/access-analyzer-upgrade-workflow-post-upgrade.md)
> **NOTE:** Return to the main workflow page via this link: [Console Migration Workflow](/docs/kb/accessanalyzer/console-migration-workflow.md).
26
26
>
27
-
> Return to the previous section via this link: [Console Migration Workflow: Step 2—Prepare the Database](/docs/kb/accessanalyzer/console-migration-workflow-step-2-prepare-the-database.md).
27
+
> Return to the previous section via this link: [Console Migration Workflow: Step 2—Prepare the Database](/docs/kb/accessanalyzer/console-migration-workflow.md)
28
28
>
29
-
> Proceed to the next section via this link: [Console Migration Workflow: Step 4—Validating the Migration](/docs/kb/accessanalyzer/console-migration-workflow-step-4-validate-the-migration.md)
30
-
29
+
> Proceed to the next section via this link: [Console Migration Workflow: Step 4—Validate the Migration](/docs/kb/accessanalyzer/console-migration-workflow.md).
31
30
## Overview
32
31
33
32
This article lists the steps for rebuilding the Netwrix Access Analyzer console during the Access Analyzer Migration.
@@ -37,7 +36,7 @@ This article lists the steps for rebuilding the Netwrix Access Analyzer console
37
36
Follow the steps below to rebuild the Access Analyzer Console on the new server. Before installation, ensure that the `NAA_Migration` folder with the `StealthAUDIT.lic` license file is stored locally on the new Access Analyzer Console so it can be referenced during the installation process.
38
37
39
38
1. Confirm that the prerequisites have been met on the Access Analyzer Console Server.
40
-
- Netwrix Help Center | Netwrix Access Analyzer 12.0 System Requirements: https://docs.netwrix.com/docs/accessanalyzer/12_0
39
+
-[Netwrix Access Analyzer 12.0 System Requirements] (https://docs.netwrix.com/docs/accessanalyzer/12_0)
41
40
2. Install the Access Analyzer application, as well as the Access Information Center (AIC) application if the server will host both.
42
41
43
42
> IMPORTANT: Do **NOT** start the Access Analyzer or AIC applications at this time.
@@ -64,36 +63,36 @@ Follow the steps below to rebuild the Access Analyzer Console on the new server.
64
63
|`%SAInstallDir%\FSAA`| Contains short-term data related to file server collections |
65
64
|`C:\Windows\System32\Tasks`| Specifically task names beginning with `SA*.job`|
66
65
67
-
2. After you have copied the Reports folder from the old server to the new one, change the report hostname path to show it in the web server:
66
+
2. After you have copied the Reports folder from the old server to the new one, change the report hostname path to show it in the web server:
68
67
` %SAInstallDir%Reports\v3\<NewServerHostName>`
69
68
70
69
3. After you have copied the Scheduled Tasks to `C:\Windows\System32\Tasks`, run the script below from an Admin PowerShell to register them:
4. Open `\NAA_Migration\NAA\Web\webserver.exe.config` and copy the content between `<appSettings></appSettings>` and paste it in place of the `<appSettings></appSettings>` block in `%SAInstallDir%Web\webserver.exe.config`.
Copy file name to clipboardExpand all lines: docs/kb/accessanalyzer/error-removed-host-name-in-aic-andor-fsaa-host-table.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -27,7 +27,7 @@ You have used the **Remove host data** option in the **FILESYSTEMACCESS** Data C
27
27
28
28
Re-run the job used to remove the host data against the full **!Removed-…** name.
29
29
30
-
- This is typically a custom job that was created. If you are unsure what job was run, please see the following article for how to create a custom job to drop File Server host data: [How to Drop Data for Decommissioned File Servers](/docs/kb/activitymonitor/dropping_file_system_data.md).
30
+
- This is typically a custom job that was created. If you are unsure what job was run, please see the following article for how to create a custom job to drop File Server host data: [How to Drop File System Data from Netwrix Access Analyzer](/docs/kb/activitymonitor/dropping_file_system_data.md).
31
31
32
32
- If you have already rerun the job and it throws a timeout error, then change the job timeout to a longer value.
33
33
@@ -37,4 +37,4 @@ Re-run the job used to remove the host data against the full **!Removed-…** na
37
37
38
38
## Related Article
39
39
40
-
-[How to Drop Data for Decommissioned File Servers](/docs/kb/activitymonitor/dropping_file_system_data.md)
40
+
-[How to Drop File System Data from Netwrix Access Analyzer](/docs/kb/activitymonitor/dropping_file_system_data.md)
Copy file name to clipboardExpand all lines: docs/kb/accessanalyzer/out-of-scope_resources_still_appear_in_the_aic_or_reporting_console_after_scoping_changes.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -28,7 +28,7 @@ Scoping options are applied at the time of a scan and are used to determine whic
28
28
If you no longer want to retain or see data for out-of-scope resources:
29
29
30
30
1.**Delete all File System data** for the specific host from the database.
31
-
- See the following article for instructions to drop data for a specific file server: [Dropping File System Data](/docs/kb/activitymonitor/dropping_file_system_data.md).
31
+
- See the following article for instructions to drop data for a specific file server: [How to Drop File System Data from Netwrix Access Analyzer](/docs/kb/activitymonitor/dropping_file_system_data.md).
32
32
33
33
2.**Rescan the host** with the updated scoping rules in place.
34
34
- This will ensure that only resources matching the current scoping criteria are imported and retained going forward.
@@ -37,4 +37,4 @@ If you no longer want to retain or see data for out-of-scope resources:
37
37
38
38
## Related Link
39
39
40
-
-[Dropping File System Data](/docs/kb/activitymonitor/dropping_file_system_data.md)
40
+
-[How to Drop File System Data from Netwrix Access Analyzer](/docs/kb/activitymonitor/dropping_file_system_data.md)
Copy file name to clipboardExpand all lines: docs/kb/activitymonitor/displays_data_for_resources_that_are_out_of_scope.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -33,7 +33,7 @@ There are two options for removing out-of-scope data:
33
33
34
34
Netwrix Support can assist with dropping all file system data for the specified host. This removes all collected data for that host, not just the out-of-scope folders.
35
35
36
-
Refer to [Dropping File System Data](/docs/kb/activitymonitor/dropping_file_system_data.md) for detailed instructions.
36
+
Refer to [How to Drop File System Data from Netwrix Access Analyzer](/docs/kb/activitymonitor/dropping_file_system_data.md) for detailed instructions.
37
37
38
38
**Considerations:**
39
39
@@ -55,4 +55,4 @@ For more granular removal (e.g., specific folders or paths), a one-time cleanup
55
55
56
56
## Related Link
57
57
58
-
-[Dropping File System Data](/docs/kb/activitymonitor/dropping_file_system_data.md)
58
+
-[How to Drop File System Data from Netwrix Access Analyzer](/docs/kb/activitymonitor/dropping_file_system_data.md)
0 commit comments