Skip to content

Commit 9d04d6a

Browse files
authored
Update Installation.md
Signed-off-by: DaveHodgeDev <47575373+DaveHodgeDev@users.noreply.github.com>
1 parent 460a952 commit 9d04d6a

File tree

1 file changed

+38
-9
lines changed

1 file changed

+38
-9
lines changed

Installation.md

Lines changed: 38 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -5,11 +5,14 @@ To deploy the MIM Auditor, the following high level tasks must be performed:
55
- Create the Log Analytics Workspace
66
- Install the service on each server with the MIM Service installed
77

8+
## **Prerequisites**
9+
1. Ensure that .Net 4.7.2 is installed on the server
10+
811
## **Preparing for installation**
912

10-
1. Download the latest version of the MIM Auditor
13+
1. Download the latest version of the MIM Auditor (source code or compiled binaries)
1114

12-
2. Compile the code to the latest version
15+
2. Compile the code to the latest version or download the compiled version
1316

1417
## **Create the Log Analytics Workspace**
1518

@@ -39,15 +42,41 @@ These following steps can be used for a default configuration of the Log Analyti
3942

4043
2. Enable Hybrid Reporting Request Logging
4144
- Launch a PowerShell window as an Administrator
42-
- Run the Enable_Hybrid_Reporting.ps1 script
45+
- Run the **Enable_Hybrid_Reporting.ps1** script
4346

44-
3. Run Setup.exe as an Administrator to install MIM Auditor
45-
- Add the workspaceID and WorkspaceKey from the Log Analytics Workspace deployment
47+
3. Run MIM Auditor's **Setup.exe** as an Administrator
48+
- Add the workspaceID from the Log Analytics Workspace deployment
4649

47-
4. Start the MIMAuditor service
50+
4. Run the Encrypt utility
51+
- Launch a PowerShell window as an Administrator
52+
- Switch the root of C: by typing: **CD\**
53+
- Switch the default location of MIM Auditor by typing: **CD 'C:\Program Files\Microsoft\MIM Auditor'**
54+
- Encrypt the Workspace Key by typing: **.\Encrypt.exe -certificate localhost -string <Workspace Key>**
55+
56+
![image](https://user-images.githubusercontent.com/47575373/205304471-e80cddd3-6280-472c-adcb-b0f02a0733da.png)
57+
58+
> **Note:** The utility will encrypt the workspace key and update the configuration files for the Auditor service and scavenger utility.
59+
60+
> **Note:** The encrypt utility uses the certificate defined in the .config file. **If the certificate is refreshed or if the workspace key is refreshed, the utility should be run again. **.
61+
62+
> **Note:** By default, the localhost certificate is used. However, the site's SSL certificate could be used to standardize when the workspace key encrypted value should be refreshed.
63+
64+
5. Configure the MIM Service to have a dependency on the MIM Auditor service to prevent the MIM Service from running when the MIM Auditor is no longer running.
4865
- Launch a PowerShell window as an Administrator
49-
- Start-Service -Name "MIMAuditor"
66+
- Set the dependency by typing: **Set-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Services\FIMService" -Name DependOnService -Value @("MIMAUDITOR")**
67+
- Reboot the server
68+
69+
![image](https://user-images.githubusercontent.com/47575373/205305791-21e259f8-61a3-4629-9771-ff4325aaf464.png)
70+
71+
> **Note:** It is important to prevent the MIM Service from issuing requests while the MIM Auditor is not watching for the log events to prevent coverage gaps.
72+
73+
6. Start the MIMAuditor service
74+
- Logon to the server as an Administrator (if you had rebooted in the previous step)
75+
- Launch a PowerShell window as an Administrator
76+
- Validate/Start the Service: Start-Service -Name "MIMAuditor"
77+
78+
7. Create an event and validate that the event is sent to the Log Analytics Workspace
5079

51-
5. Create an event and validate that the event is sent to the Log Analytics Workspace
80+
8. Create a scheduled task to run the Scavenger utility to process any requests that may not have been written to the Log Analytics Workspace. Any failure to write the log successfully to the Log Analytics Workspace will be captured to the **C:\Program Files\Microsoft\MIM Auditor\Requests** folder
5281

53-
6. Repeat steps 1 to 5 on each of your MIM Service Servers.
82+
9. Repeat steps 1 to 8 on each of your MIM Service Servers.

0 commit comments

Comments
 (0)