Installing the Nodinite Pickup Log Events Service Logging Agent
Deploy the Nodinite Pickup Log Events Service Logging Agent with the right approach for your infrastructure. This guide covers two installation methods: the modern Portal-based approach (recommended for most environments) and the legacy MSI method (for remote servers only).
Understanding Your Installation Options
Portal-Based Installation (Recommended)
The Portal-based installation leverages the Nodinite Portal to generate automated PowerShell scripts that handle agent installation, configuration, and service account setup. This approach:
- Reduces manual errors - Scripts validate prerequisites and configuration automatically
- Enables centralized management - Configure multiple agents from one location
- Provides intelligent diagnostics - AI-powered error analysis with helpful solutions
- Supports modern .NET 10 - Latest runtime for optimal performance
- Simplifies troubleshooting - Consistent installation across environments
Legacy MSI Installation (Remote Servers Only)
The MSI-based installation is a manual, wizard-driven approach preserved for remote servers or legacy v6 environments. This method:
- Requires manual steps - Each step configured individually through installer screens
- Increases installation time - Multiple clicks and manual configuration required
- Lacks automation benefits - No centralized management or validation
- May be retired - Legacy approach not recommended for new deployments
Recommendation: Use Portal-based installation unless your infrastructure constraints prevent automated PowerShell script execution.
Nodinite v7.0.4 and Later (Portal-Based Installation - Recommended)
New 7.0.4
The modern Portal-based installation method is the recommended approach for all new Nodinite v7.0.4+ deployments. This section explains why this approach is superior and how to execute it.
How to Install with Portal-Based Approach
Step 1: Register Your Environment in Nodinite Portal
Access the Nodinite Portal and register your environment if not already done.
Step 2: Select Pickup LogEvents Service Agent
In the Portal's Agents configuration tab, select the Pickup LogEvents Service Agent for installation.
Step 3: Configure Agent Settings
Specify the following configuration:
- Agent port - Network port for agent communications
- Service account - Windows or gMSA account that runs the agent
- Pickup directories - Source locations for log events
Step 4: Download Installation Package
Download the installation package containing embedded PowerShell scripts tailored to your configuration.
Step 5: Execute PowerShell Script
Run the provided PowerShell script on the target server. The script automatically:
- Validates prerequisites
- Installs the agent
- Configures the Windows Service
- Initializes pickup directories
- Establishes connectivity to Nodinite
For complete step-by-step instructions with screenshots, see:
Install Nodinite v7 - Portal-Based Installation - Comprehensive guide with detailed screenshots and troubleshooting tips
Legacy Installation (Remote Servers Only - Not Recommended)
Warning
Deprecated: The MSI-based installation method is legacy and intended only for remote server installations where the Portal-based approach cannot be used. This method is not recommended for new deployments and may be retired in future versions.
Important
Version 7.0.4+ Users: If you are installing Pickup Log Events Service Logging Agent v7.0.4 or later, use the Portal-based installation method (see section below) instead. The MSI approach below is for legacy v6 installations or remote servers only.
When to Use MSI Installation
Use this method only if:
- You are installing on a remote server that cannot be managed via Portal scripts
- You are maintaining a legacy v6 environment (upgrade to v7 recommended)
- You have specific infrastructure constraints preventing automated installation
Prerequisites for MSI Installation
Ensure you meet all prerequisites for the Nodinite Pickup Log Events Service Logging Agent.
MSI Installation Steps
Step 1: Start the Installer
Double-click the MSI file to launch the Nodinite Pickup Log Events Service Logging Agent installer.
Example of the MSI installer file.
Step 2: Welcome Screen
When the installer starts, you will see the Welcome screen.
Example of the Welcome screen in the installer.
Click Next to proceed or Cancel to exit the installer.
Step 3: Accept the EULA
You must accept the End User License Agreement (EULA) to continue. If you do not accept the terms, you cannot install the logging agent.
Example of the EULA acceptance screen.
Click Next to proceed or Cancel to exit the installer.
Step 4: Custom Setup
Select the components and installation location. Default settings are recommended for most users.
Example of the Custom Setup screen.
Click Next to proceed or Cancel to exit the installer.
Step 5: Service Account Information
Enter the credentials for the account that will run the Nodinite Pickup Log Events Service Logging Agent. This account may be used to access and query monitored databases, depending on your configuration.
Domain
Enter the domain name. For local accounts, use the server name or a dot (.) as the domain.
User
Enter the account username.
Password
Enter the account password.
The account must have 'Log on as a Service' rights.
Example of the service account credentials screen.
Click Next to proceed or Cancel to exit the installer.
Insufficient Privileges
If the account information does not meet the prerequisites, you will see an error message.
The image below shows the Insufficient Privileges error.
Common causes include the account not being allowed to run as a service or not being a local administrator. Follow the How to set Logon as a Service right guide and click Retry. If the issue persists, click Cancel and restart the installer with valid credentials.
Tip: Check the Windows Event Logs (System and Application) for additional error details.
Step 6: Complete the Setup
The final step displays either a successful installation or a premature exit.
Successful Installation
Example of a successful installation completion.
Failed Installation
A failed installation results in a premature exit.
Example of a failed installation with premature exit.
Click Finish to exit the installer.
Support
If you encounter issues you cannot resolve, contact Support.
Additional troubleshooting information may be available in the Windows Event Logs.