grafana-prtg/setup.md

@@ -57,10 +57,11 @@ You will need to configure PRTG to add an `Access-Control-Allow-Origin` HTTP hea
 3. Select **Download ZIP** and save
 4. Unzip the downloaded file > Navigate to the `jasonlashua-prtg-datasource` directory; drag `jasonlashua-prtg-datasource` into the Grafana directory (on the Grafana server): **data/plugins** - on a Windows machine, this is `C:\Program Files\GrafanaLabs\grafana\data\plugins`
 5. Go to `services.msc` and restart the **Grafana** service
-6. Select the **Datasource** page and click the "**Add new**" button
-7. Under Edit Data Source, Choose a simple name, e.g., "PRTG" and select "prtg" as the data source type.
-8. Under HTTP Settings, provide the API URL (http://prtg.example.com/api)
-9. Typically you should chose "**Server**" as the **access** mode unless you specifically want the web browser to directly communicate with PRTG
-10. Skip the **Http Auth** section
-11. Under **PRTG API Configuration**, provide the username for the account you will be accessing the API as. For the passhash, you will find this in the PRTG account page for that user. **Providing the password will not work.** ![PRTG Data Source](img/prtg-data-source.png)
-12. Click the "Test Connection" button to verify your datasource connection ![Test Successful](img/test-successful.png)#
+6. Open the Grafana web UI at http://localhost:3000/ if you're connected to the server where Grafana is installed, or http://<grafana's-server-IP-address>:3000 otherwise. Log in with user admin and password admin. Grafana will ask you to change the default password upon the first login.
+7. Select the **Datasource** page and click the "**Add new**" button
+8. Under Edit Data Source, Choose a simple name, e.g., "PRTG" and select "prtg" as the data source type.
+9. Under HTTP Settings, provide the API URL (http://prtg.example.com/api)
+10. Typically you should chose "**Server**" as the **access** mode unless you specifically want the web browser to directly communicate with PRTG
+11. Skip the **Http Auth** section
+12. Under **PRTG API Configuration**, provide the username for the account you will be accessing the API as. For the passhash, you will find this in the PRTG account page for that user. **Providing the password will not work.** ![PRTG Data Source](img/prtg-data-source.png)
+13. Click the "Test Connection" button to verify your datasource connection ![Test Successful](img/test-successful.png)#

networking/fortigate/obtain-msi-vpn-only.md

@@ -31,6 +31,8 @@ Obtaining the MSI & PKGs allows for pushing updates to your users via MDM, easil
 
 ## Deploying the MSI / PKG
 - MSI - No issues, like any other MSI
+  - **Caveat:** If you send the update while the user is online/Forticlient is running, it will not actually update and if they attempt to do check/use it after, it will make them reboot before the update commences.  A preinstall script is necessary.
+
 - PKG - For some reason, it would not upload into Filewave, renaming it to **Forticlientx.x.x.pkg** allowed it to upload without any issues
   - During deployment, the user will receive the following popup:
   > "Fortitray" Would Like to Add VPN Configurations
@@ -54,3 +56,6 @@ Obtaining the MSI & PKGs allows for pushing updates to your users via MDM, easil
 
 ## Another Approach
 The following link: `https://filestore.fortinet.com/forticlient` has XML content of the latest installers.
+
+## MDM Deployment
+My notes for MDM deployment of Forticlient to Macs can be found at [filewave-scripts/mac/forticlient-vpn](https://github.com/angela-d/filewave-scripts/mac/forticlient-vpn)