- 9 minutes to read

Post-installation

Unlock the full potential of your Nodinite installation by following these essential post-installation steps. This guide helps you secure your environment, optimize performance, and ensure business continuity with best practices for backup, monitoring, and regular updates. Access your Web Client to manage and monitor your installation, and use the Monitoring Agents to keep an eye on Nodinite itself.

On this page, you will learn how to

✅ Exclude critical folders and processes from antivirus scanning for optimal performance
✅ Monitor disk usage and prevent downtime
✅ Back up your SQL Server databases and secure your data
✅ Harden your environment with encryption and security best practices
✅ Stay up-to-date with the latest features and improvements

In the post-installation steps, you should fulfill the business requirements and perform your planned maintenance tasks as previously detailed in the Nodinite Planning Guide.

Inspiration for post-installation steps
Inspiration: Keep your Nodinite environment running smoothly with proactive post-installation steps. Image source: Unsplash

Understanding the Post-Installation Cycle

Post-installation is not a one-time task. You harden and protect the installation once, and then keep a regular cycle of monitoring, backups, and updates.

graph LR roInstall["fa:fa-rocket Installed with
the CLI package"] roAV["fa:fa-filter Antivirus
exclusions"] roHarden["fa:fa-lock Hardening
TLS, gMSA, least privilege"] roMonitor["fa:fa-monitor-waveform Monitor disk,
databases, and services"] roBackup["fa:fa-box-archive Back up
the databases"] roUpdate["fa:fa-arrow-turn-up Monthly update
with the CLI"] roInstall --> roAV roAV --> roHarden roHarden --> roMonitor roMonitor --> roBackup roBackup -->|"backup before update"| roUpdate roUpdate -->|"repeat every month"| roMonitor style roInstall fill:#2678BD,color:#fff style roAV fill:#3F827B,color:#fff style roHarden fill:#3F827B,color:#fff style roMonitor fill:#E47528,color:#fff style roBackup fill:#E47528,color:#fff style roUpdate fill:#E47528,color:#fff

After the CLI installation (blue), the one-time tasks (teal) are antivirus exclusions and Hardening. The recurring cycle (orange) is monitoring with the Windows Server and Database Monitoring Agents, backing up the Configuration Database and Log Databases, and applying the monthly update.

Directories and file name extensions to exclude from virus scanning

Real-time antivirus scanning of database files and of the Nodinite web sites slows down logging and monitoring, and can lock files during an update. Keep the exclusions narrow: exclude only the folders, files, and processes listed below, never whole system folders or executable file types (.dll, .exe, .config) across the machine.

SQL Server Exclusions

Microsoft recommends excluding SQL Server files and processes from antivirus scanning. Apply Microsoft's guidance on every SQL Server that hosts the Configuration Database and the Log Databases; this has the largest effect on performance.

Nodinite

  • C:\Program Files\Nodinite\ (the default; the actual folder is the Install path you set per server in the Portal, Step 4: Servers)

IIS

Folder or process Purpose
C:\inetpub\temp\IIS Temporary Compressed Files Compressed versions of site files.
C:\inetpub\logs\LogFiles IIS logs; scanning slows down logging.
%SystemRoot%\System32\inetsrv\w3wp.exe (process) IIS worker process that runs each Nodinite web site.
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Temporary ASP.NET Files Only on servers where the BizTalk or Windows Server Monitoring Agent runs in IIS on .NET Framework 4.8.

Exclude PowerShell Script Example

Note

Adjust the paths to your environment and company policy. Run the SQL Server part on the SQL Server, and only after you have checked Microsoft's guidance above.

# Run this as Administrator

# Nodinite and IIS folders (Core Services and agent servers)
$exclusionPaths = @(
    "C:\Program Files\Nodinite\",                    # Install path set in the Portal
    "C:\inetpub\temp\IIS Temporary Compressed Files",
    "C:\inetpub\logs\LogFiles"
    # "C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Temporary ASP.NET Files"  # Only for .NET Framework agents in IIS
)

# IIS worker process
$exclusionProcesses = @(
    "$env:SystemRoot\System32\inetsrv\w3wp.exe"
)

# SQL Server data and log files (run on the SQL Server; see Microsoft's guidance)
$exclusionExtensions = @(".mdf", ".ldf", ".ndf")

foreach ($path in $exclusionPaths) {
    Add-MpPreference -ExclusionPath $path -ErrorAction SilentlyContinue
}
foreach ($proc in $exclusionProcesses) {
    Add-MpPreference -ExclusionProcess $proc -ErrorAction SilentlyContinue
}
foreach ($ext in $exclusionExtensions) {
    Add-MpPreference -ExclusionExtension $ext -ErrorAction SilentlyContinue
}

Write-Host "Windows Defender exclusions for Nodinite added."

You can see the current exclusions using the following command:

Get-MpPreference|Select-Object ExclusionPath, ExclusionProcess, ExclusionExtension

Monitor Disk Usage

The most severe incidents in our support are usually the result of systems running out of disk space. When you run out of disk space, Nodinite is no longer operational.

Make sure to monitor your disk usage. Nodinite has the following helpful monitoring agents with disk usage-related monitoring:

Also monitor the Nodinite Core Services themselves. On Windows Server, every Core Service is its own IIS web site, so use the IIS - Web Sites and IIS - Application Pools monitoring of the Windows Server Monitoring Agent to get an alert when one of them stops. A stopped MCP Server can be by design when Keep the MCP Server stopped is selected in the Portal (Keep the MCP Server Stopped).

Backup your SQL Server Databases

Make sure your IT organization, among many other things, performs a regular backup of your Nodinite installation.

It will help if you use the Nodinite Database Monitoring Agent to ensure that backups of the databases are regular. Regardless of who is responsible, if the backups fail, or are not created, in the end, if the IT department fails to back up your environment and data gets lost, it will be your problem!

Create a Full Database Backup - Microsoft documentation

You need to make sure you are performing timely backups according to your policy of the following Nodinite databases:

Remove the backups of the databases (retention) according to your company policy. We recommend at least 4 days to manage a long weekend.

Boost SQL Server Performance

  • Ensure there is at least one TEMPDB file with 128 MB in fixed size per CPU core (up to 8), and at least one that is allowed to grow beyond the fixed size limit.
  • Bump the Database compatibility level to match the SQL Server version in use.

    Nodinite ships with low numbers to support older versions of SQL Server.

  • Compress the backup if possible.
  • If you have SQL maintenance plans, please disable the Nodinite DatabaseMaintenance system parameter if these are competing.
  • Please tune the recovery interval according to your policy. We recommend the following settings:
    • Standalone, 60.
    • High availability (AOAG), 0 - (default).

Hardening your environment

For comprehensive security hardening guidance including HTTPS/TLS configuration, SQL Server encryption, certificate management, and network security, see:

This guide covers:

  • IIS HTTPS/TLS - Certificate requirements, DNS setup, and IIS bindings for Nodinite v7
  • SQL Server encryption - Connection string encryption and certificate validation
  • SMB/NFS encryption - File share security for untrusted networks
  • IPSec - Network-level encryption for all communication
  • Certificate management - Best practices for the certificate lifecycle. Identify the TLS certificate by its subject in the Portal (Core host Configuration); after a renewal, rerun the update and the CLI binds the new certificate
  • Authentication - Modern authentication with OpenID Connect
  • Group Managed Service Accounts (gMSA) - Replace local or domain service accounts with gMSA for automated password management and improved security. Recommended for the IIS application pool identities in v7; the account still needs the Log on as a service right.
  • Least privilege in SQL Server - Reduce the install-time sysadmin right after installation, see SQL Server Sysadmin Requirements

Tip

The SQL Server Connection Strings guide provides detailed examples for configuring encryption across all Nodinite components.

Stay up-to-date

We constantly develop new features and fine-tune the product with better performance. Nodinite follows a monthly release cadence aligned with Microsoft's .NET patch cycle to ensure you benefit from the latest security updates, performance improvements, and new capabilities.

Update Cadence and Support Policy

  • Monthly Updates - New releases typically available within days of Microsoft's monthly .NET patches
  • Security Patches - Critical security updates delivered as soon as available
  • Support Requirement - Active support coverage requires running the latest version as per your software agreement

Important

Support Policy: To receive technical support, you must be running the latest available version of Nodinite. This requirement is specified in all customer and partner software agreements and ensures you benefit from the latest security patches and bug fixes.

Why Regular Updates Matter

  • Enhanced Security - Benefit from regular patch updates and modern security features, keeping your environment protected
  • Superior Performance - .NET 10 delivers faster execution, improved scalability, and lower resource consumption compared to .NET Framework 4.8
  • Reduced Maintenance - Automated updates and simplified deployment lower operational costs and downtime
  • Future-Proof Technology - Stay ahead with Microsoft's latest innovations and long-term support
  • Cloud-Ready - Seamlessly deploy and scale in cloud environments for maximum agility
  • Modern Authentication - Integrates with OAuth 2.0/OIDC identity providers for secure, flexible login options
  • Cross-Platform Flexibility - Future option to run Nodinite on non-Windows, Linux, and containers
  • Rich Ecosystem - Access the latest libraries, tools, and integrations for rapid development and innovation

Best Practices for Updates

  1. Test in Non-Production - Always test updates in a non-production environment first
  2. Plan Update Windows - Schedule updates during low-traffic periods to minimize impact
  3. Backup Before Update - Always back up databases and configuration before applying updates
  4. Monitor Release Notes - Check the Release Notes regularly to see what's new and plan accordingly
  5. Apply Updates Promptly - Apply updates as soon as possible to maintain security and support eligibility

Tip

While you can defer updates for testing purposes, we recommend applying updates within 30-60 days of release. Skipping multiple update cycles may:

  • Invalidate your support agreement
  • Expose your environment to known security vulnerabilities
  • Make future updates more complex due to accumulated changes
  • Prevent access to new features and performance improvements

Update Resources

Note

If you have concerns about applying a specific update or need to defer an update beyond the recommended timeframe, contact Support page or your partner to discuss your specific situation.

Previous Step

6. Working with Nodinite - Start using your monitoring solution

Next Steps

Recommended tracking settings for BizTalk Server default pipelines - Optimize BizTalk logging
Updating Nodinite - Keep your installation current
POC Guide - Prove the value of Nodinite with real scenarios

Planning your Nodinite Installation - Review your implementation plan
Configuration Database - Central configuration storage
Hardening - Security best practices
Release Notes - Latest features and updates
Uninstall Nodinite v7 - Remove installation if needed
Updating from v6 to v7 - Migrate from the unsupported v6
Core Services - The services you just installed
Web Client - Access your monitoring portal
Log Databases - Message logging storage