Creating Firewall Rules for NetVault 13.X.X using PowerShell on Windows Server (4371227)

Creating Firewall Rules for NetVault 13.X.X using PowerShell on Windows Server

Users running NetVault 13 on Windows Server might encounter issues related to firewall settings that block communication between NetVault processes and other components, such as clients or storage devices.

The cause of the issue is often the lack of appropriate Windows Firewall rules allowing inbound and outbound connections for NetVault processes. This can lead to problems like backup failures, inability to manage clients, or other operational issues.

Follow the steps below to create the necessary Windows Firewall rules for NetVault 13.X.X processes using a PowerShell script. If you have any additional plugins, you will need to modify the script to include the binary and path for each plugin.

Step 1: Prepare the PowerShell script

Copy the PowerShell script below, which creates inbound and outbound rules for specified NetVault processes:

# Define the processes and their locations
$processes = @{ 
    "nvpmgr"       = "C:\Program Files\Quest\NetVault\bin\nvpmgr.exe" 
    "nvconsolesvc" = "C:\Program Files\Quest\NetVault\bin\nvconsolesvc.exe" 
    "nvstatsmngr"  = "C:\Program Files\Quest\NetVault\bin\nvstatsmngr.exe" 
    "nvwpview"     = "C:\Program Files\Quest\NetVault\bin\nvwpview.exe" 
    "nvcoreplg"    = "C:\Program Files\Quest\NetVault\bin\nvcoreplg.exe" 
    "nvraw"        = "C:\Program Files\Quest\NetVault\bin\nvraw.exe" 
    "nvfs"         = "C:\Program Files\Quest\NetVault\plugins\filesystem\nvfs.exe" 
    "nvsqlserver"  = "C:\Program Files\Quest\NetVault\plugins\sqlserver\nvsqlserver.exe" 
} # Add any additional application plugin installed

# Loop through the processes and create inbound and outbound rules for each process 
foreach ($processName in $processes.Keys) { 
    $processPath = $processes[$processName]

    # Create the inbound rule 
    New-NetFirewallRule -DisplayName "Inbound Rule - $processName" -Direction Inbound -Program $processPath -Action Allow -Profile Domain,Private,Public -Enabled True
    
    # Create the outbound rule 
    New-NetFirewallRule -DisplayName "Outbound Rule - $processName" -Direction Outbound -Program $processPath -Action Allow -Profile Domain,Private,Public -Enabled True
}

Save the script as a PowerShell (.ps1) file (e.g., CreateFirewallRules.ps1).

Step 2: Run the PowerShell script

1. Open PowerShell with administrative privileges by right-clicking on the PowerShell icon and selecting "Run as administrator".

2. Navigate to the directory where the script is located and execute the script by running the following command:

.\CreateFirewallRules.ps1

This command will create the necessary inbound and outbound firewall rules for the specified NetVault processes.

Step 3: Verify the firewall rules

1. Press Win + R to open the Run dialog.

2. Type wf.msc and press Enter to open the Windows Firewall with Advanced Security console.

3. Navigate to "Inbound Rules" and "Outbound Rules" to check for the newly created rules corresponding to the NetVault processes. You should see the rules with the display names "Inbound Rule - [processName]" and "Outbound Rule - [processName]" for each process specified in the script.

By following the steps in this knowledge base article, the inbound and outbound Windows Firewall rules for NetVault 13 processes can be correctly configured using a PowerShell script on Windows Server. These rules help ensure secure communication for the application. It should be ensured that the paths in the script match the actual locations of the processes on the system. If you have any issues or need additional help, please contact Quest Support.