### Install Python Dependencies for QuickStart Script

Source: https://github.com/netwrix/docs/blob/main/docs/privilegesecure/4.2/discovery/admin-guide/configuration-settings/quickstart-script.md

This command installs the necessary Python packages from `requirements.txt` and specifically forces the installation of `openpyxl` version 3.0.10. It addresses potential compatibility issues with newer `openpyxl` versions and ensures all required libraries are available for the QuickStart script. Run this command from the directory where the QuickStart script files have been extracted.

```Bash
pip install --trusted-host pypi.org --trusted-host files.pythonhosted.org -r requirements.txt && pip install --force-reinstall openpyxl==3.0.10
```

--------------------------------

### Configure MDX with esbuild

Source: https://github.com/netwrix/docs/blob/main/reference-docs/mdx/getting-started.mdx

Provides an example of integrating MDX with esbuild. It shows how to use the `@mdx-js/esbuild` plugin within an esbuild configuration to process `.mdx` files.

```js
import mdx from '@mdx-js/esbuild';
import esbuild from 'esbuild';

await esbuild.build({
  entryPoints: ['index.mdx'],
  format: 'esm',
  outfile: 'output.js',
  plugins: [
    mdx({
      /* jsxImportSource: …, otherOptions… */
    }),
  ],
});
```

--------------------------------

### Configure MDX with Webpack

Source: https://github.com/netwrix/docs/blob/main/reference-docs/mdx/getting-started.mdx

Shows a Webpack configuration example for processing MDX files. It demonstrates using `@mdx-js/loader` within Webpack's module rules, with an optional `babel-loader` for further processing.

```js
/**
 * @import {Options} from '@mdx-js/loader'
 * @import {Configuration} from 'webpack'
 */

/** @type {Configuration} */
const webpackConfig = {
  module: {
    // …
    rules: [
      // …
      {
        test: /\.mdx?$/,
        use: [
          // Babel is optional:
          { loader: 'babel-loader', options: {} },
          {
            loader: '@mdx-js/loader',
            /** @type {Options} */
            options: {
              /* jsxImportSource: …, otherOptions… */
            },
          },
        ],
      },
    ],
  },
};

export default webpackConfig;
```

--------------------------------

### SSO Application Start Parameters Example

Source: https://github.com/netwrix/docs/blob/main/docs/passwordsecure/9.1/user-guides/applications/learning-applications.md

Demonstrates how start parameters are defined using placeholders and how they are resolved with actual field values when an SSO application is launched. This example uses the Salamander application to transfer folder paths.

```Configuration
-L {field:Left Path} -R {field:Right Path}
```

```Configuration
-L "C:\Projekte\" -R "C:\Ablage\Projekte"
```

--------------------------------

### Install Quickstart Script Dependencies

Source: https://github.com/netwrix/docs/blob/main/docs/privilegesecure/4.2/discovery/getting-started.md

Installs required Python packages for the Privilege Secure Quickstart script using pip. This command ensures all necessary libraries are available for the script to run correctly, requiring Python 2.7 and PIP to be installed.

```Python
pip install -r requirements.txt
```

--------------------------------

### SSO Application Start Parameter Example with Placeholders

Source: https://github.com/netwrix/docs/blob/main/docs/passwordsecure/9.2/core-features/applications/application-configuration.md

This example demonstrates how start parameters are defined using placeholders for dynamic field values and how these placeholders are resolved into actual data when the SSO application is launched. It illustrates the transformation from a placeholder-based string to a concrete path.

```Configuration
Template:
-L {field:Left Path} -R {field:Right Path}

Resolved Example:
-L "C:\Projekte\" -R "C:\Ablage\Projekte"
```

--------------------------------

### Run Docusaurus Development Server

Source: https://github.com/netwrix/docs/blob/main/reference-docs/docusaurus/installation.mdx

Commands to navigate into the Docusaurus project directory and start the local development server. This allows for live preview of changes as files are edited, typically opening a browser window at http://localhost:3000.

```bash
cd my-website
npm run start
```

--------------------------------

### Install MDX TypeScript Types

Source: https://github.com/netwrix/docs/blob/main/reference-docs/mdx/getting-started.mdx

Installs the `@types/mdx` package using npm, which provides TypeScript type definitions for MDX files, enabling type checking for imported MDX components.

```sh
npm install @types/mdx
```

--------------------------------

### TypeScript MDX Import Typing Example

Source: https://github.com/netwrix/docs/blob/main/reference-docs/mdx/getting-started.mdx

Illustrates how TypeScript automatically infers types for imported MDX files (e.g., `.mdx`) after the `@types/mdx` package is installed, making `Post` imports type-safe.

```js
// @filename: types.d.ts
import type {} from 'mdx'
// @filename: example.js
// ---cut---
import Post from './post.mdx' // `Post` is now typed.
```

--------------------------------

### Install Robot Framework Selenium Library

Source: https://github.com/netwrix/docs/blob/main/docs/identitymanager/6.1/connectors-integration/connector-tutorials/index.md

Command to install or upgrade the Robot Framework Selenium Library using pip. This is a crucial first step for setting up your automation environment.

```bash
pip install --upgrade robotframework-seleniumlibrary
```

--------------------------------

### Install Password Reset Server to Custom Directory

Source: https://github.com/netwrix/docs/blob/main/docs/passwordreset/3.3/getting-started/installation.md

Example command to install the Password Reset Server to a directory other than the default, using the SERVERDIR parameter with the setup wizard. This allows for flexible installation paths.

```cmd
APR330.exe SERVERDIR="D:\Programs\NPR\"
```

--------------------------------

### Start Single Product Development (Legacy Support)

Source: https://github.com/netwrix/docs/blob/main/README.md

Provides examples of `npm` commands to start the development server for a specific product or version, primarily for backward compatibility, though full site starts are now faster.

```bash
# Examples (optional - full site starts quickly now)
npm run start 1secure
npm run start accessanalyzer/12.0
npm run start identitymanager/saas
```

--------------------------------

### Example Command Line Installation for Activity Monitor Agent

Source: https://github.com/netwrix/docs/blob/main/docs/activitymonitor/7.1/installation/agents.md

Demonstrates a full command-line example for installing the Activity Monitor Agent silently, specifying a custom port, installation path, management group, and verbose logging.

```cmd
msiexec.exe /i C:\\SBFileMonAgent.msi AGENT_PORT=1234 AGENTINSTALLLOCATION="D:\\AMAgent" MANAGEMENT_GROUP=AMDOMAIN\\AMGROUP /l*v c:\\amagent.log /qn
```

--------------------------------

### Install Python Dependencies for QuickStart

Source: https://github.com/netwrix/docs/blob/main/docs/privilegesecure/4.2/discovery/admin-guide/configuration-settings/advanced-fields.md

Installs required Python packages from `requirements.txt` to set up the QuickStart reporting tool. This step ensures all necessary libraries are available for script execution.

```Python
pip install -r requirements.txt
```

--------------------------------

### Initialize Docusaurus Project using npm

Source: https://github.com/netwrix/docs/blob/main/reference-docs/docusaurus/installation.mdx

This command provides an alternative method to initialize a new Docusaurus project using npm's `init` command. It offers another option for project setup, complementing the `npx create-docusaurus` approach.

```bash
npm init docusaurus
```

--------------------------------

### Launch Usercube Server via CLI

Source: https://github.com/netwrix/docs/blob/main/docs/identitymanager/6.1/getting-started/quick-start.md

This command-line snippet launches the Usercube server. It should be executed from the Runtime folder after the configuration has been successfully deployed. This command starts the application, making it accessible via a web browser.

```Command Line
./identitymanager-Server.exe
```

--------------------------------

### Docusaurus Monorepo Folder Structure Example

Source: https://github.com/netwrix/docs/blob/main/reference-docs/docusaurus/installation.mdx

Illustrates a typical monorepo directory layout for a Docusaurus project, showing how a Docusaurus website can coexist with other project packages and share dependencies. This structure facilitates integrated development and documentation.

```bash
my-monorepo
├── package-a # Another package, your actual project
│   ├── src
│   └── package.json # Package A's dependencies
├── website   # Docusaurus root
│   ├── docs
│   ├── src
│   └── package.json # Docusaurus' dependencies
├── package.json # Monorepo's shared dependencies
```

--------------------------------

### Basic Vite Configuration with MDX Rollup Plugin

Source: https://github.com/netwrix/docs/blob/main/reference-docs/mdx/getting-started.mdx

This snippet demonstrates the fundamental setup for integrating MDX into a Vite project. It shows how to import and include the `@mdx-js/rollup` plugin within the `plugins` array of your `vite.config.js` file.

```JavaScript
import mdx from '@mdx-js/rollup';
import { defineConfig } from 'vite';

const viteConfig = defineConfig({
  plugins: [mdx(/* jsxImportSource: …, otherOptions… */)],
});

export default viteConfig;
```

--------------------------------

### Example Provisioning Order JSON Structure

Source: https://github.com/netwrix/docs/blob/main/docs/identitymanager/6.1/connectors-integration/connector-tutorials/index.md

This JSON object illustrates the structure of a provisioning order passed to the `Fulfill-CSV` function, detailing user information, resource types, and changes.

```JSON
{
    "ProvisioningOrdersList": [
        {
            "AssignedResourceTypeId": "3930001",
            "ChangeType": "Added",
            "WorkflowInstanceId": "81",
            "Owner": {
                "Id": "21511",
                "InternalDisplayName": "007 - Bond James",
                "Identifier": "007",
                "EmployeeId": "007",
                "PhotoTag": -3065,
                "MainFirstName": "James",
                "MainLastName": "Bond",
                ...
            },
            "ResourceType": {
                "Id": "-41",
                "SourceEntityType": {
                    "Id": "51",
                    "Identifier": "Directory_User"
                },
                "TargetEntityType": {
                    "Id": "70",
                    "Identifier": "PowerShellCsv_User"
                },
                "Identifier": "PowerShellCsv_User_NominativeUser"
            },
            "Changes": {
                "identifier": "007",
                "firstName": "James",
                "lastName": "Bond"
            }
        }
    ]
}
```

--------------------------------

### Launch Identity Manager Server

Source: https://github.com/netwrix/docs/blob/main/docs/identitymanager/saas/getting-started/quick-start.md

This command launches the Identity Manager server. It should be executed from the Runtime folder after the configuration has been successfully deployed.

```Shell
./identitymanager-Server.exe
```

--------------------------------

### Robot Framework: Complete Provisioning Script Example

Source: https://github.com/netwrix/docs/blob/main/docs/identitymanager/6.1/connectors-integration/connector-tutorials/index.md

This comprehensive Robot Framework script demonstrates a full provisioning workflow. It includes settings, variables, mandatory provisioning keywords (`ExecuteAdd`, `ExecuteDelete`, `ExecuteModify`), and utility keywords for interacting with File Explorer (opening, navigating, setting file properties). It concludes with a `Run Provisioning` test case.

```Robot Framework
*** Settings ***
Resource C:/identitymanagerDemo/Runtime/identitymanagerRobotFramework.resource
Library FlaUILibrary

*** Variables ***
${FOLDERNAME} RobotFrameworkIdentity
${FOLDERPATH} C:/identitymanagerDemo/${FOLDERNAME}

*** Keywords ***
ExecuteAdd
    [Arguments] ${order}
    Log To Console ExecuteAdd is not implemented

ExecuteDelete
    [Arguments] ${order}
    Set File To Read Only ${order}

ExecuteModify
    [Arguments] ${order}
    Log To Console ExecuteModify is not implemented

Open Explorer
    Launch Application explorer
    Attach Application By Name explorer
    Open Folder

Open Folder
    Click /Window[@Name='File Explorer']/Pane[2]/Pane[3]/ProgressBar/Pane/ToolBar/SplitButton
    Set Text To Textbox /Window[@Name='File Explorer']/Pane[2]/Pane[3]/ProgressBar/ComboBox/Edit[@Name='Address'] ${FOLDERPATH}
    Press Key s'ENTER'

Get File Name
    [Arguments] ${order}
    [return] ${order['Changes']['Identifier']}.txt

Set File To Read Only
    [Arguments] ${order}
    ${FileName}= Get File Name ${order}
    Open File Properties ${FileName}
    Select ReadOnly ${FileName}

Open File Properties
    [Arguments] ${filename}
    Right Click /Window[@Name='${FOLDERNAME}']/Pane[3]/Pane/Pane[2]/List/ListItem[@Name='${filename}']/Image
    Click /Menu[@Name='Context']/MenuItem[@Name='Properties']

Select Read Only
    [Arguments] ${filename}
    Click /Window[@Name='${filename} Properties']/CheckBox[@Name='Read-only']
    Click /Window[@Name='${filename} Properties']/Button[@Name='OK']

Close Explorer
    Click /Window[@Name='${FOLDERNAME}']/TitleBar/Button[@Name='Close']

*** Test Cases ***
Run Provisioning
    Open Explorer
    Launch Provisioning
    Close Explorer
```

--------------------------------

### Install Password Reset Server to Custom Directory

Source: https://github.com/netwrix/docs/blob/main/docs/passwordpolicyenforcer/10.2/password-reset/installation.md

Example command-line syntax to install the Password Reset Server to a directory other than the default, using the SERVERDIR parameter with the setup wizard.

```Shell
APR330.exe SERVERDIR="D:\Programs\NPR\"
```

--------------------------------

### Install Netwrix Docs Repository and Dependencies

Source: https://github.com/netwrix/docs/blob/main/README.md

Clones the documentation repository, installs required Node.js dependencies, and provides commands to start the development server for all products or a single product.

```bash
# Clone the repository
git clone https://github.com/netwrix/docs.git
cd docs

# Install dependencies
npm install

# Start development server (all products)
npm run start

# Single product mode (recommended for development)
npm run start 1secure
npm run start accessanalyzer/12.0
```

--------------------------------

### Scaffold Docusaurus Project with Classic Template

Source: https://github.com/netwrix/docs/blob/main/reference-docs/docusaurus/installation.mdx

This bash command uses `create-docusaurus` to initialize a new Docusaurus website named 'my-website' using the recommended 'classic' template. The classic template provides a quick start with standard documentation, a blog, custom pages, and a CSS framework including dark mode support.

```bash
npx create-docusaurus@latest my-website classic
```

--------------------------------

### Launch Identity Manager Server

Source: https://github.com/netwrix/docs/blob/main/docs/identitymanager/6.2/getting-started/quick-start.md

This command launches the Identity Manager server using the `identitymanager-Server.exe` executable. It should be executed from within the Runtime folder to start the application server, making it accessible via a web browser.

```shell
./identitymanager-Server.exe
```

--------------------------------

### Install and Configure PostgreSQL for PingCastle Enterprise (Ubuntu)

Source: https://github.com/netwrix/docs/blob/main/docs/pingcastle/enterpriseinstall.md

These commands guide through the installation of PostgreSQL on Ubuntu 17, followed by creating a dedicated user 'pingcastle', setting its password, and finally creating a database 'pingcastle' owned by this user. This setup is required for PingCastle Enterprise to connect to a PostgreSQL database.

```bash
sudo apt-get install postgresql postgresql-contrib

sudo /etc/init.d/postgresql start

sudo -u postgres createuser pingcastle

sudo -u postgres psql
alter user pingcastle with password 'pingcastle';

sudo -u postgres createdb -O pingcastle pingcastle
```

--------------------------------

### Netwrix Auditor Installation Steps for Small Environments

Source: https://github.com/netwrix/docs/blob/main/docs/auditor/10.6/reference/deployment-scenarios.md

Provides a step-by-step guide for installing Netwrix Auditor in a small environment. This includes preparing a virtual machine, performing a full installation of server and client components, and configuring the Audit database with SQL Server Express Edition.

```English
1. Prepare a virtual machine meeting the following requirements:
2. Download and install Netwrix Auditor on that VM, selecting Full installation to deploy both server and client components.
3. When prompted to configure the Audit database settings, proceed with installing SQL Server Express Edition with Advanced Services on the same VM.
```

--------------------------------

### Install Password Reset to Custom Directory via Command Line

Source: https://github.com/netwrix/docs/blob/main/docs/passwordreset/3.23/installation-setup/installation-guide.md

This snippet demonstrates how to specify a custom installation directory for the Password Reset Server using the SERVERDIR parameter when running the setup executable.

```Command Line
APR323.exe SERVERDIR="D:\\Programs\\APR\\"
```

--------------------------------

### Example: Check Microsoft Edge Web Driver

Source: https://github.com/netwrix/docs/blob/main/docs/identitymanager/6.1/connectors-integration/connector-tutorials/index.md

A specific example demonstrating how to check for the Microsoft Edge web driver's presence in the system PATH using PowerShell.

```powershell
gcm MicrosoftWebDriver
```

--------------------------------

### Compile MDX with Preact JSX Runtime

Source: https://github.com/netwrix/docs/blob/main/reference-docs/mdx/getting-started.mdx

This example demonstrates how to compile MDX content using Preact as the JSX import source. The `jsxImportSource` option in `ProcessorOptions` is set to `'preact'`.

```js
import { compile } from '@mdx-js/mdx';

const js = String(await compile('# hi', { jsxImportSource: 'preact' /* otherOptions… */ }));
```

--------------------------------

### CSV: Example Output Format for Robot Framework Script

Source: https://github.com/netwrix/docs/blob/main/docs/identitymanager/6.1/connectors-integration/connector-tutorials/index.md

Illustrates the expected format of the CSV file that the Robot Framework script aims to generate. It shows the required header row and an example data row, demonstrating how provisioning orders are appended to the file.

```CSV
command;identifier;firstName;lastName
...
Insert;007;James;Bond
...
```

--------------------------------

### Deploy Identity Manager Configuration

Source: https://github.com/netwrix/docs/blob/main/docs/identitymanager/saas/getting-started/quick-start.md

This command deploys the Identity Manager configuration. It requires replacing placeholder attributes for the database connection string and the configuration path with custom values. Execute this command from the Runtime folder.

```Shell
./identitymanager-Deploy-Configuration.exe -s "<data source=.;Database=Usercube;Integrated Security=SSPI;Min Pool Size=10;encrypt=false;>" -d "<C:/identitymanagerBootstrap/Conf>"
```

--------------------------------

### Example CSV Output for PowerShell Provisioning

Source: https://github.com/netwrix/docs/blob/main/docs/identitymanager/6.1/connectors-integration/connector-tutorials/index.md

This snippet illustrates the expected format of the CSV file generated by the PowerShell provisioning script. It shows the header row with command, identifier, firstName, and lastName fields, followed by an example data row for an 'insert' command.

```CSV
command;identifier;firstName;lastName
...
insert;007;James;Bond
...
```

--------------------------------

### Scripted Installation and Configuration of Gen 7 Agent RPM

Source: https://github.com/netwrix/docs/blob/main/docs/changetracker/8.1/installation-deployment/agent-installation/linux.md

Performs a complete installation, configuration, and service start of the Gen 7 Agent on Linux using a single command. This includes installing the RPM, configuring the agent with hub details, and immediately starting the service.

```Bash
rpm -ivh nnt-changetracker-gen7agentcore-7.0.1.9-252.noarch.rpm ;
/opt/nnt/gen7agentcore/configure-gen7agentcore.sh https://192.168.1.107/api agent passWord121
/opt/nnt/agent/bin GenVII- ; /sbin/service nntgen7agent start
```

--------------------------------

### Launch Provisioning Process

Source: https://github.com/netwrix/docs/blob/main/docs/identitymanager/6.1/connectors-integration/connector-tutorials/index.md

Initiates the provisioning process as defined by the provisioning orders. This keyword is essential and required for any provisioning activities to take place.

```APIDOC
Launch Provisioning:
  Description: Launches the provisioning defined by the provisioning orders. This keyword is required for any provisioning to happen.
```

--------------------------------

### Netwrix Client Installation Command Line Parameters Reference

Source: https://github.com/netwrix/docs/blob/main/docs/passwordsecure/9.2/installation-setup/client-installation/installation-parameters.md

Detailed reference for available command line parameters to customize the Netwrix Password Secure client installation. These parameters control the installation of specific components and services, allowing for fine-grained control over the client setup.

```APIDOC
Parameters:
  AUTOFILL_ADDON_AUTOSTART="0": Deactivates launching the Autofill Add-on in Windows autostart.
  INSTALL_AUTOFILL_ADDON="0": Deactivates the installation of the Autofill Add-on. In the list of the components to be installed in the setup, a check mark has not been set but this can be set again by the user.
  INSTALL_OFFLINE_ADDON="0": Deactivates the installation of the Offline Add-on. In the list of the components to be installed in the setup, a check mark has not been set but this can be set again by the user.
  IGNORE_TS_SERVICES="1": Deactivates the installation of the terminal server services, no matter on which system the installation is running.
  INSTALL_IDP_SERVICE="1": Activates the installation of the IDP Service.
```

--------------------------------

### Bootstrap Meta Open Source Docusaurus Project

Source: https://github.com/netwrix/docs/blob/main/reference-docs/docusaurus/installation.mdx

This command is specific to Meta open source projects, used to bootstrap a new Docusaurus website within an internal repository. It applies useful Meta-specific default configurations, streamlining the setup process for internal projects.

```bash
scarf static-docs-bootstrap
```

--------------------------------

### Compile MDX with Emotion JSX Runtime

Source: https://github.com/netwrix/docs/blob/main/reference-docs/mdx/getting-started.mdx

This example demonstrates how to compile MDX content using Emotion as the JSX import source. The `jsxImportSource` option in `ProcessorOptions` is set to `'@emotion/react'`.

```js
import { compile } from '@mdx-js/mdx';

const js = String(await compile('# hi', { jsxImportSource: '@emotion/react' /* otherOptions… */ }));
```

--------------------------------

### Start the Docusaurus development server

Source: https://github.com/netwrix/docs/blob/main/reference-docs/docusaurus/introduction.mdx

Navigates into the newly created Docusaurus project directory and starts the local development server, typically accessible at http://localhost:3000 for live preview.

```bash
cd my-website
npx docusaurus start
```

--------------------------------

### Robot Framework Keyword: Get Secure Data

Source: https://github.com/netwrix/docs/blob/main/docs/identitymanager/6.1/connectors-integration/connector-tutorials/index.md

Documents the 'Get Secure Data' keyword, which expects the Robot Framework process to receive a JSON list of attributes via the stdin stream. An example of the expected JSON format is provided for manual input.

```APIDOC
Get Secure Data:
  Description: This keyword expects the Robot Framework process to receive a json list of attributes in the stdin stream.
  Input: JSON string via stdin (e.g., {"Login":"login","Password":"password"})
```

--------------------------------

### Install Threat Prevention Agent with Logging

Source: https://github.com/netwrix/docs/blob/main/docs/threatprevention/7.5/troubleshooting/msilogs.md

Example command to install the Threat Prevention Agent, specifying a log file named SIAgentLog.log in the current directory. This command initiates the main installation process.

```cmd
"SI Agent.exe\" /L SIAgentLog.log
```

--------------------------------

### Initialize Usercube Database using sqlcmd CLI

Source: https://github.com/netwrix/docs/blob/main/docs/identitymanager/6.1/installation-setup/database-setup.md

This command-line example demonstrates how to initialize the Usercube database using the `sqlcmd` utility. It connects to a specified SQL Server instance, targets the Usercube database, and executes the `Usercube.sql` script.

```CLI
sqlcmd -S <ComputerName>\<InstanceName> -d Usercube<Organization_name> -i <Usercube.sql>
```

--------------------------------

### Example Docusaurus Site Directory Structure

Source: https://github.com/netwrix/docs/blob/main/reference-docs/docusaurus/guides/docs/docs-create-doc.mdx

Illustrates a typical Docusaurus site directory, showing the `docs` folder and a nested guide file. This structure is used to demonstrate default URL generation.

```bash
website # Root directory of your site
└── docs
    └── guide
        └── hello.md
```

--------------------------------

### Create a new Docusaurus site

Source: https://github.com/netwrix/docs/blob/main/reference-docs/docusaurus/introduction.mdx

Installs Node.js and initializes a new Docusaurus project with the classic template, preparing the directory for further development.

```bash
npx create-docusaurus@latest my-website classic
```

--------------------------------

### Usercube Agent: SharePoint Connection Credentials Example

Source: https://github.com/netwrix/docs/blob/main/docs/identitymanager/6.1/connectors-integration/connector-tutorials/index.md

Provides an example of how to configure the "Server", "Login", and "Password" attributes for a SharePoint connection within the "SharePointExportContoso" section of the `appsettings.agent.json` file. This snippet demonstrates direct credential input, though more secure methods are recommended for production environments.

```JSON
{ ... "Connections": { ... "SharePointExportContoso": { "Server": "https://contoso.sharepoint.com/", "Login": "usercube.service@contoso.com", "Password": "19f23f48379d50a9a50b8c" } } }
```

--------------------------------

### Netwrix Auditor Installation Steps for Regular Environments

Source: https://github.com/netwrix/docs/blob/main/docs/auditor/10.6/reference/deployment-scenarios.md

Provides a step-by-step guide for installing Netwrix Auditor in a regular environment. This includes preparing a physical or virtual machine, installing Netwrix Auditor, deploying required clients on remote machines, and configuring the Audit database with SQL Server Express Edition.

```English
1. Prepare a physical or a virtual machine meeting the following requirements:
2. Download and install Netwrix Auditor on that machine. Deploy the required number of Netwrix Auditor clients on the remote Windows machines.
3. When prompted to configure the Audit database settings, proceed with installing SQL Server Express Edition with Advanced Services.
```

--------------------------------

### Install Password Reset Server to Custom Directory

Source: https://github.com/netwrix/docs/blob/main/docs/passwordpolicyenforcer/11.0/password-reset/installation.md

Example command-line argument for the Password Reset Setup wizard (APR330.exe) to install the Password Reset Server to a directory other than the default '\Program Files\Netwrix Password Reset\'.

```CMD
APR330.exe SERVERDIR="D:\\Programs\\NPR\\"
```

--------------------------------

### Install PostgreSQL and PostgreSQL Contrib on Ubuntu

Source: https://github.com/netwrix/docs/blob/main/docs/pingcastle/proinstall.md

These commands install PostgreSQL and its contrib package on an Ubuntu 17 system. It then starts the PostgreSQL service.

```Bash
sudo apt-get install postgresql postgresql-contrib
sudo /etc/init.d/postgresql start
```

--------------------------------

### Install Password Reset Server to Custom Directory

Source: https://github.com/netwrix/docs/blob/main/docs/passwordreset/3.23/installation-setup/installation-guide.md

Demonstrates how to use the SERVERDIR parameter with the Password Reset Setup wizard (APR323.exe) to install the Password Reset Server to a non-default folder.

```CMD
APR323.exe SERVERDIR="D:\\Programs\\APR\\"
```

--------------------------------

### Configure MDX with Rollup

Source: https://github.com/netwrix/docs/blob/main/reference-docs/mdx/getting-started.mdx

Illustrates how to set up MDX with Rollup. The configuration includes the `@mdx-js/rollup` plugin and optionally `@rollup/plugin-babel` for transpilation of the resulting JavaScript.

```js
/**
 * @import {RollupOptions} from 'rollup'
 */

import mdx from '@mdx-js/rollup';
import { babel } from '@rollup/plugin-babel';

/** @type {RollupOptions} */
const config = {
  // …
  plugins: [
    // …
    mdx({
      /* jsxImportSource: …, otherOptions… */
    }),
    // Babel is optional:
    babel({
      // Also run on what used to be `.mdx` (but is now JS):
      extensions: ['.js', '.jsx', '.cjs', '.mjs', '.md', '.mdx'],
      // Other options…
    }),
  ],
};

export default config;
```

--------------------------------

### Install Netwrix Password Reset with Custom Server Directory

Source: https://github.com/netwrix/docs/blob/main/docs/passwordreset/3.3/getting-started/installation.md

This command-line example demonstrates how to install the Netwrix Password Reset Server to a custom directory using the `SERVERDIR` parameter. This allows administrators to specify an installation path different from the default `\Program Files\NetwrixPassword Reset\` folder during the setup wizard execution.

```CMD
APR330.exe SERVERDIR="D:\\Programs\\NPR\\"
```

--------------------------------

### Robot Framework Web Automation Error Handling Example

Source: https://github.com/netwrix/docs/blob/main/docs/identitymanager/6.1/connectors-integration/connector-tutorials/index.md

Demonstrates robust error handling in Robot Framework for web applications. This example uses `Try Keyword` and `Catch Keyword` to restart the browser and retry navigation if a page fails to load, ensuring subsequent operations are not affected by previous failures.

```Robot Framework
Open Usercube Website
    Open Browser
    Connect To Usercube
    [Teardown] Close Browser

Restart Browser
    [Arguments] ${url}
    Log Debug An error has occured, restarting the browser
    Close Browser
    Open Browser ${url}

Connect To Usercube
    Try Keyword Go To Usercube.com
    Catch Keyword Restart Browser Usercube.com
    Page Should Contain Usercube
```

--------------------------------

### Install PolicyPak Cloud Client with Join Token via Command Line

Source: https://github.com/netwrix/docs/blob/main/docs/endpointpolicymanager/cloud/interface/tools.md

Demonstrates how to install the PolicyPak Cloud Client using `msiexec` and a `JOINTOKEN` from the command line. The `JOINTOKEN` ensures the client automatically joins specified groups, picks up XML directives, CSE versions, and upgrades to the latest client version. Two examples are provided: a basic installation and an automated quiet installation with logging.

```cmd
msiexec /i "PolicyPak Cloud Client.msi" JOINTOKEN="AQOLsGUcYHV6OL03pP88Qe0="
```

```cmd
msiexec /i "PolicyPak Cloud Client.msi" /qn /norestart /log "c:\temp\ppcloudinstall.log" JOINTOKEN="AQOLsGUcYHV6OL03pP88Qe0="
```

--------------------------------

### Initialize Identity Manager Database using sqlcmd CLI

Source: https://github.com/netwrix/docs/blob/main/docs/identitymanager/saas/installation/production-setup/database.md

This command-line example demonstrates how to initialize the Identity Manager database using the `sqlcmd` utility. It connects to a specified SQL Server instance and executes the `Usercube.sql` script on the target database.

```CLI
sqlcmd -S <ComputerName>\<InstanceName> -d Usercube<Organization_name> -i <Usercube.sql>
```

--------------------------------

### Start Docusaurus v2 Development Server

Source: https://github.com/netwrix/docs/blob/main/reference-docs/docusaurus/migration/v2/migration-automated.mdx

Navigate into the newly migrated v2 website directory, install dependencies, and start the local development server to view the website.

```bash
cd ./v2-website
npm install
npm start
```

--------------------------------

### Robot Framework: Full Provisioning and User Management Script

Source: https://github.com/netwrix/docs/blob/main/docs/identitymanager/6.1/connectors-integration/connector-tutorials/index.md

This complete Robot Framework script demonstrates a comprehensive setup for Usercube provisioning and testing. It defines resources, libraries, variables, and a wide range of keywords for executing add, delete, and modify operations on users, managing groups, setting passwords, and handling browser interactions for a banking application.

```Robot Framework
*** Settings ***
Resource C:/identitymanagerDemo/Runtime/identitymanagerRobotFramework.resource
Library SeleniumLibrary

*** Variables ***
${BROWSER} edge
${BANKINGURL} http://localhost:5011

*** Keywords ***
ExecuteAdd
    [Arguments] ${order}
    Log To Console ExecuteAdd is not implemented

ExecuteDelete
    [Arguments] ${order}
    Log To Console ExecuteDelete is not implemented

ExecuteModify
    [Arguments] ${order}
    Try Keyword Modify User ${order}
    Catch Keyword Restart Banking And Fail

Modify User
    [Arguments] ${order}
    Try Keyword Set Password ${order}
    Catch Keyword Go To ${BANKINGURL}/User
    Title Should Be All Users - Banking System
    Add All Groups ${order}
    Remove All Groups ${order}

Restart Banking And Fail
    Close Browser
    Launch Banking App
    Fail ${Provisioning failed, restarting the browser}

Launch Banking App
    Open Browser ${BANKINGURL} ${BROWSER}
    Title Should Be Home Page - Banking System

Set Password
    [Arguments] ${order}
    Go To ${BANKINGURL}/User/SetPassword/${login}
    Title Should Be Edit ${login} - Banking System
    ${password}= Generate Password
    Input Text id:Password ${password}
    Click Element xpath:/html/body/div/main/div[1]/div/form/div[2]/input
    Send Password Notification

Add Group To User
    [Arguments] ${groupName}
    Select From List By Value name:group ${groupName}
    Click Element at Coordinates name:group 250 0
    Click Element xpath:/html/body/div/main/div[1]/div/form/div[2]/input
    Title Should Be All Users - Banking System

Search User And Add Group
    [Arguments] ${login} ${groupName}
    Go To ${BANKINGURL}/User/AddGroup/${login}
    Title Should Be Add Group to ${login} - Banking System
    Add Group To User ${groupName}

Add Groups
    [Arguments] ${order} ${length}
    FOR ${i} IN RANGE ${length}
        Search User And Add Group ${order['Resource']['login']} ${order['Changes']['groups_add'][${i}]['name']}
    END

Add All Groups
    [Arguments] ${order}
    ${status} ${length}= Run Keyword And Ignore Error Get Length ${order['Changes']['groups_add']}
    Run Keyword If '${status}' == 'PASS' Add Groups ${order} ${length}

Remove Group From User
    [Arguments] ${login} ${groupName}
    Go To ${BANKINGURL}/User/RemoveGroup/${login}?groupId=${groupName}

Remove Groups
    [Arguments] ${order} ${length}
    FOR ${i} IN RANGE ${length}
        Remove Group From User ${order['Resource']['login']} ${order['Changes']['groups_remove'][${i}]['name']}
    END

Remove All Groups
    [Arguments] ${order}
    ${status} ${length}= Run Keyword And Ignore Error Get Length ${order['Changes']['groups_remove']}
    Run Keyword If '${status}' == 'PASS' Remove Groups ${order} ${length}

*** Test Cases ***
Run Provisioning
    Launch Banking App
    Launch Provisioning
    [Teardown] Close Browser
```

--------------------------------

### Calling the Web Application URLs

Source: https://github.com/netwrix/docs/blob/main/docs/passwordsecure/9.1/installation/web-application/installation-web-application.md

Examples of how to access the Web Application based on its deployment configuration (root directory, subdirectory, or custom port).

```URL
https://hostname
```

```URL
https://hostname/path-to-subdirectory
```

```URL
https://hostname:port/path-to-subdirectory
```

--------------------------------

### Example: Full XPath Element Locator

Source: https://github.com/netwrix/docs/blob/main/docs/identitymanager/6.1/connectors-integration/connector-tutorials/index.md

An example of a full XPath that uniquely identifies an element on a web page. While precise, XPaths can be brittle and may require maintenance if the page structure changes.

```XPath
/html/body/section/div[2]/div[3]/div[1]/pre[4]/span
```

--------------------------------

### Install Password Reset with Custom Directory

Source: https://github.com/netwrix/docs/blob/main/docs/passwordpolicyenforcer/11.0/password-reset/installation.md

Demonstrates how to install the Password Reset Server to a custom folder by specifying the SERVERDIR parameter when running the setup executable.

```Command Line
APR330.exe SERVERDIR="D:\\Programs\\NPR\\"
```

--------------------------------

### Example JSON Response for Get Policies

Source: https://github.com/netwrix/docs/blob/main/docs/activitymonitor/7.1/integrations/rest-api/resources.md

Provides a sample JSON array representing policy objects returned by the GET policies API call. Each object includes policy ID, URL, name, description, path, GUID, enablement status, and last update timestamp.

```JSON
[
  {
    "id": "10013",
    "url": "https://localhost:4494/api/v1/domains/TEST01/policies/10013",
    "name": "LDAP Monitor",
    "description": "",
    "path": "Policies\\Auditing",
    "guid": "8f5e4870-6d28-4f32-af18-2e6e6ed623ce",
    "isEnabled": true,
    "updatedAt": "2019-04-19T10:17:32.0546644Z"
  },
  {
    "id": "10014",
    "url": "https://localhost:4494/api/v1/domains/TEST01/policies/10014",
    "name": "Authentication Monitor",
    "description": "",
    "path": "Policies\\Auditing",
    "guid": "8f5e4870-6d28-4f32-af18-2e6e6ed623cf",
    "isEnabled": true,
    "updatedAt": "2019-04-19T10:17:32.0546644Z"
  }
]
```

--------------------------------

### Default Server Configuration Example (appsettings.json)

Source: https://github.com/netwrix/docs/blob/main/docs/identitymanager/6.1/installation-setup/server-configuration.md

This JSON snippet provides an example of the default server configuration within appsettings.json. It demonstrates settings for IdentityServer (including X509KeyFilePath and X509KeyFilePassword for token signing certificates) and Authentication (covering RequireHttpsMetadata, TestUserStore enablement and password, and AllowLocalLogin). Attributes enclosed in <> are placeholders that must be replaced with custom values.

```json
{
    "IdentityServer": {
        // Token signing certificate stored in a file
        "X509KeyFilePath": "<./identitymanagerContoso.pfx>",
        // Optional certificate password
        "X509KeyFilePassword": "<secret>"
    },
    "Authentication": {
        "RequireHttpsMetadata": false,
        "TestUserStore": {
            "Enabled": "<true>",
            "Password": "<secret>"
        },
        "AllowLocalLogin": true
    }
}
```

--------------------------------

### Deploy Usercube Configuration via CLI

Source: https://github.com/netwrix/docs/blob/main/docs/identitymanager/6.1/getting-started/quick-start.md

This command-line snippet deploys the Usercube configuration. It requires replacing placeholders for the database connection string (e.g., data source, database name, security) and the configuration directory path. The command should be executed from the Runtime folder.

```Command Line
./identitymanager-Deploy-Configuration.exe -s "<data source=.;Database=Usercube;Integrated Security=SSPI;Min Pool Size=10;encrypt=false;>" -d "<C:/identitymanagerBootstrap/Conf>"
```

--------------------------------

### Start Gen 7 Agent Service on Linux

Source: https://github.com/netwrix/docs/blob/main/docs/changetracker/8.1/installation-deployment/agent-installation/linux.md

Starts the Gen 7 Agent service after installation and configuration. This command uses the 'service' utility, common in many Linux distributions, to manage the agent's running state.

```Bash
/sbin/service gen7agentcore start
```

--------------------------------

### Robot Framework Telnet Connection Example

Source: https://github.com/netwrix/docs/blob/main/docs/identitymanager/6.1/connectors-integration/connector-tutorials/index.md

This Robot Framework script demonstrates how to establish a Telnet connection to a specified IP address. It defines a variable for the IP, a keyword to open the connection, and a test case to execute the connection. It also highlights Robot Framework's syntax rule of requiring two spaces between instructions for function and parameter separation.

```Robot Framework
*** Settings ***
Library Telnet

*** Variables ***
${IPADDRESS} 192.168.1.22

*** Keywords ***
Open Telnet Connection
    Open Connection ${IPADDRESS} prompt=$

*** Test Cases ***
Run Provisioning
    Open Telnet Connection

```

--------------------------------

### Agent Installation Command with Logging

Source: https://github.com/netwrix/docs/blob/main/docs/threatprevention/7.4/troubleshooting/msilogs.md

This command-line example demonstrates how to run the Threat Prevention Agent installer and specify a log file. The /L switch enables logging, and SIAgentLog.log is the name of the log file to be created in the current directory.

```cmd
SI Agent.exe" /L SIAgentLog.log
```

--------------------------------

### Configure WinRM for Quick Setup

Source: https://github.com/netwrix/docs/blob/main/docs/directorymanager/11.0/getting-started/installation/preparation-tool.md

This command initializes WinRM on a system, setting up default listeners and firewall exceptions. It's a common first step for enabling remote management, including GroupID's connection to Exchange.

```PowerShell
winrm /quickconfig
```

--------------------------------

### Configure MDX with Next.js

Source: https://github.com/netwrix/docs/blob/main/reference-docs/mdx/getting-started.mdx

This snippet shows how to configure Next.js to support MDX files as pages using `@next/mdx`. It extends the default page extensions to include `.md` and `.mdx`.

```js
import nextMdx from '@next/mdx';

const withMdx = nextMdx({
  // By default only the `.mdx` extension is supported.
  extension: /\.mdx?$/,
  options: {
    /* otherOptions… */
  }
});

const nextConfig = withMdx({
  // Support MDX files as pages:
  pageExtensions: ['md', 'mdx', 'tsx', 'ts', 'jsx', 'js']
});

export default nextConfig;
```

--------------------------------

### Get Policies Response Example (JSON)

Source: https://github.com/netwrix/docs/blob/main/docs/activitymonitor/8.0/integrations/rest-api/api-reference.md

This JSON array provides an example of the policy objects returned when retrieving policies for a domain. Each object includes policy details such as ID, URL, name, description, path, GUID, enabled status, and last update timestamp.

```json
[
  {
    "id": "10013",
    "url": "https://localhost:4494/api/v1/domains/TEST01/policies/10013",
    "name": "LDAP Monitor",
    "description": "",
    "path": "Policies\\Auditing",
    "guid": "8f5e4870-6d28-4f32-af18-2e6e6ed623ce",
    "isEnabled": true,
    "updatedAt": "2019-04-19T10:17:32.0546644Z"
  },
  {
    "id": "10014",
    "url": "https://localhost:4494/api/v1/domains/TEST01/policies/10014",
    "name": "Authentication Monitor",
    "description": "",
    "path": "Policies\\Auditing",
    "guid": "8f5e4870-6d28-4f32-af18-2e6e6ed623cf",
    "isEnabled": true,
    "updatedAt": "2019-04-19T10:17:32.0546644Z"
  }
]
```

--------------------------------

### Starting Docusaurus v2 Development Server

Source: https://github.com/netwrix/docs/blob/main/reference-docs/docusaurus/migration/v2/migration-manual.mdx

Commands to navigate into the 'website' directory and start the Docusaurus v2 development server using npm or yarn.

```bash
cd website
npm start
```

```bash
cd website
yarn start
```

--------------------------------

### Example JSON for SourcesRootPaths Configuration

Source: https://github.com/netwrix/docs/blob/main/docs/identitymanager/6.1/installation-setup/agent-configuration.md

Illustrates the expected JSON format for configuring the 'SourcesRootPaths' property, showing how to specify multiple root directories for file-based connections.

```JSON
{
    "SourcesRootPaths": [ "C:/identitymanagerContoso/SourceHR", "C:/identitymanagerContoso/SourcesPhone" ]
}
```

--------------------------------

### Custom Script Keywords Reference

Source: https://github.com/netwrix/docs/blob/main/docs/identitymanager/6.1/connectors-integration/connector-tutorials/index.md

Detailed documentation for custom keywords used within the script, outlining their purpose, actions, and specific usage contexts.

```APIDOC
Keyword: Modify User
  Description: Sets a password for the user, then applies the provisioning order. This keyword does everything the `Execute Modify` keyword should do, so that it can be used for error handling. As the provisioned resource type may not have password reset settings, the password generation could fail, which is why it is called by the `Try Keyword` keyword.

Keyword: Restart Banking And Fail
  Description: Restarts the Banking Application, then fails the keyword execution. This keyword should be used when the Banking application is in an unknown state.

Keyword: Launch Banking App
  Description: Launches the Banking web application. To check that the web browser is on the right page, the title of the page is verified with the `Title Should Be` keyword.

Keyword: Set Password
  Description: Generates a password for the provisioned user, sets their Banking password to that password, then sends a notification. This keyword attempts to send the notification as soon as the password is set. First, this ensures that the notification is sent even if the rest of the script would crash. Second, this keeps the password in memory for the least amount of time possible, which reduces security risks.

Keyword: Add Group To User
  Description: Selects the group that should be added, and clicks the **Save** button. This keyword also verifies that the web browser has the expected title. The `Click Element At Coordinates` keyword is used to reset the state of the page, as selecting the group hides the **Save** button.

Keyword: Search User And Add Group
  Description: Goes to the page to add groups to the right user, and calls `Add Group To User`. This keyword also verifies that the web page has the expected title.

Keyword: Add Groups
  Description: Calls `Search User And Add Group` for each group in the provisioning order.

Keyword: Add All Groups
  Description: Computes the number of groups to add, and if there is at least one, calls `Add Groups`. The only way to find the number of groups to add is in the **Changes** > **groups_add** section of the provisioning order. This section does not exist if there are no groups to add, so the `Run Keyword And Ignore Error` is called to avoid propagating the error.
```

--------------------------------

### PingCastle Enterprise appsettings.json: PostgreSQL Connection String Example

Source: https://github.com/netwrix/docs/blob/main/docs/pingcastle/enterpriseinstall.md

This JSON snippet provides an example of a PostgreSQL connection string as configured in the appsettings.json file for PingCastle Enterprise. It shows how to specify the server, username, password, and database name. This string is assigned to the DefaultConnection parameter within the application settings.

```JSON
"DefaultConnection":
"Server=localhost;username=pingcastle;password=pingcastle;database=pingcastle"
```

--------------------------------

### Configure PolicyPak Least Privilege Manager for Skype Installer

Source: https://github.com/netwrix/docs/blob/main/docs/endpointpolicymanager/video/fslogix/profiles.md

Outlines the process of creating a new Windows Installer Policy in PolicyPak Least Privilege Manager. This policy allows standard users to install 'SkypeSetup.exe' by combining path and digital signature conditions, ensuring only legitimate installers are elevated.

```APIDOC
PolicyPak Least Privilege Manager:
  New Windows Installer Policy:
    - Rule Type: Combo Rule
    - Conditions:
      - Path: "SkypeSetup"
      - Signature: "Skype guys"
    - Action: Run with elevated privileges
```

--------------------------------

### Using Babel MDX Plugin with Babel Core API

Source: https://github.com/netwrix/docs/blob/main/reference-docs/mdx/getting-started.mdx

This example demonstrates how to integrate the custom `babelPluginSyntaxMdx` with `@babel/core` to transform MDX content. It shows how to call `babel.transformAsync` with the MDX document and the custom plugin, emphasizing the need to set a `filename` for the plugin to correctly identify and process MDX files.

```js
import babel from '@babel/core';
import { babelPluginSyntaxMdx } from './plugin.js';

const document = '# Hello, world!';

// Note that a filename must be set for our plugin to know it’s MDX instead of JS.
const result = await babel.transformAsync(document, {
  filename: 'example.mdx',
  plugins: [babelPluginSyntaxMdx]
});

console.log(result);
```

--------------------------------

### Initialize Identity Manager Database with sqlcmd CLI

Source: https://github.com/netwrix/docs/blob/main/docs/identitymanager/6.2/installation/pre-installation/database-setup.md

This command line example demonstrates how to initialize the Identity Manager database using the sqlcmd utility. It connects to a specified SQL Server instance, targets the newly created database, and executes the Usercube.sql script to apply the schema.

```CLI
sqlcmd -S <ComputerName>\<InstanceName> -d Usercube<Organization_name> -i <Usercube.sql>
```

--------------------------------

### Robot Framework Locator: Class Strategy

Source: https://github.com/netwrix/docs/blob/main/docs/identitymanager/6.1/connectors-integration/connector-tutorials/index.md

An example of a Robot Framework element locator using the 'class' strategy. This identifies elements based on their CSS class attribute.

```Robot Framework
class:copy-to-clipboard
```

--------------------------------

### Example SharePoint Connection Configuration

Source: https://github.com/netwrix/docs/blob/main/docs/identitymanager/6.2/reference/index.md

This example demonstrates how to configure a SharePoint connection in `appsettings.agent.json` for scanning at a detailed level (ListItem). It includes parameters for the SharePoint server URL, scan level, login credentials, and a path to a CSV file for additional URLs. Placeholder values like `example.sharepoint.com` and `account.example@usercube.com` should be replaced with actual environment-specific details.

```json
appsettings.agent.json
{
  ...
  "Connections": {
    ...
    "SharePointExport": {
        "Server": "https://example.sharepoint.com/",
        "Scanlevel": "ListItem",
        "Login": "account.example@usercube.com",
        "Password": "account'sexamplepassword",
        "CsvUrls": "C:/identitymanager/source/SP_others.csv¤URL¤,"
    }
  }
}
```

--------------------------------

### Run .NET Application Manually for Troubleshooting

Source: https://github.com/netwrix/docs/blob/main/docs/pingcastle/enterpriseinstall.md

This command allows you to manually start the PingCastleEnterprise.dll application. Running it directly from the command line can help identify startup issues such as TCP port conflicts or invalid connection strings, which might not be immediately apparent when run as a service.

```bash
dotnet.exe PingCastleEnterprise.dll
```

--------------------------------

### Fill Banking Database with Initial Data

Source: https://github.com/netwrix/docs/blob/main/docs/identitymanager/saas/connectors/how-to/demo-apps/banking.md

Command to populate the BankingSystem database using the provided executable from the Runtime folder. It requires the database connection string, path to SDK sources, and path to Banking SQL files.

```Shell
./identitymanager-FillBankingDatabase.exe --connection-string {connection string} --sources-path {sources path} --banking-sql-path {banking sql path}
```

--------------------------------

### Configure MDX for Vue

Source: https://github.com/netwrix/docs/blob/main/reference-docs/mdx/getting-started.mdx

This snippet shows how to configure MDX to compile for Vue by setting the `jsxImportSource` option to `'vue'`. This allows MDX to generate Vue-compatible JSX. Optionally, `@mdx-js/vue` can be installed for context-based component passing.

```js
import { compile } from '@mdx-js/mdx';

const js = String(await compile('# hi', { jsxImportSource: 'vue' /* otherOptions… */ }));
```

--------------------------------

### Configure MDX and React Plugins in Vite with Enforce Pre

Source: https://github.com/netwrix/docs/blob/main/reference-docs/mdx/getting-started.mdx

When using both `@mdx-js/rollup` and `@vitejs/plugin-react`, it's crucial to ensure the MDX plugin runs before the React plugin. This example illustrates how to enforce the 'pre' phase for the MDX plugin to prevent conflicts and ensure proper processing of MDX files.

```JavaScript
import mdx from '@mdx-js/rollup';
import react from '@vitejs/plugin-react';
import { defineConfig } from 'vite';
// …
const viteConfig = defineConfig({
  plugins: [
    {
      enforce: 'pre',
      ...mdx({
        /* jsxImportSource: …, otherOptions… */
      }),
    },
    react({ include: /\.(jsx|js|mdx|md|tsx|ts)$/ }),
  ],
});
// …
```

--------------------------------

### Install Activity Monitor Agent via Command Line

Source: https://github.com/netwrix/docs/blob/main/docs/activitymonitor/8.0/agents/management/manual-installation.md

Example command demonstrating a quiet installation of the Netwrix Activity Monitor Agent using `msiexec.exe` with custom port, installation location, management group, and verbose logging.

```Batch
msiexec.exe /i C:\SBFileMonAgent.msi AGENT_PORT=1234 AGENTINSTALLLOCATION=“D:\AMAgent” MANAGEMENT_GROUP=AMDOMAIN\AMGROUP /l*v c:\amagent.log /qn
```