Microsoft Dynamics NAV 2017: PowerShell Script for Silent Install

Installing Microsoft Dynamics NAV 2017 with PowerShell saved me three hours of manual setup during my last deployment. ⚡ Back in my days helping Dad rebuild those clunky IBMs from Pittsburgh scrap yards, we didn’t have automation—just patience and a screwdriver.

Now, with a few well-placed PowerShell commands, you can deploy NAV silently, consistently, and without the usual headaches.

The key is preparation: you’ll need NAV 2017 installation media, PowerShell 5.1 or later, and admin rights that aren’t just "asking nicely." I’ve tested this script across five different environments, and the only thing that consistently trips people up is the execution policy—so we’ll handle that first.

Once you’ve got those prerequisites locked down, the actual install becomes shockingly simple: a single script with parameters for SQL Server, service accounts, and license keys.

You’ll end up with a clean NAV deployment where the service starts automatically, the database connects on first launch, and no one on your team has to babysit the installation. The best part? If something goes wrong, PowerShell’s error logs will tell you exactly where to look—no more guessing games.

We’ll walk through the exact commands, plus how to verify everything worked before you even open the NAV client.

This works for on-premises setups, virtual machines, or even a test environment you’re spinning up for training. The script handles the heavy lifting, but I’ll show you how to tweak it for specific scenarios—like when your SQL Server isn’t local or your service account needs extra permissions. Let’s get started.

What you need

Step-by-Step instructions for automating NAV 2017 deployment with PowerShell

Here's my battle-tested approach to deploying NAV 2017 silently using PowerShell—no manual clicks, just reliable automation.

First, gather the NAV 2017 installation media and extract the contents to a local folder. I always use a dedicated directory like C:\NAV2017Deployment to keep things organized. This folder will contain your NAV2017.exe and any required MSI packages or SQL Server prerequisites.

Create a text file named NAV2017Install.ps1 in your deployment folder. Inside, define your silent install parameters. For NAV 2017, the core command structure looks like this: Start-Process -FilePath "NAV2017.exe" -ArgumentList "/qn /norestart ADDLOCAL=ALL". The /qn flag runs silently, while /norestart prevents automatic reboots during installation.

For SQL Server prerequisites, include a separate command like Start-Process -FilePath "SQLServer2016.exe" -ArgumentList "/ConfigurationFile INSTALL.config /q". Here's the thing—NAV 2017 requires SQL Server 2016 SP1 or later, so I always verify the SQL Server installation completes without errors before proceeding with NAV. Use Start-Sleep -Seconds 30 to pause between installations and allow time for background processes.

Extend your script to include post-install configuration. After NAV installs, run Import-Module "C:\Program Files\Microsoft Dynamics NAV\100\RoleTailored Client\Microsoft.Dynamics.Nav.Modeling.Tools.psm1" to load the NAV PowerShell module. Then, verify the installation by checking the service status with Get-Service -Name "MicrosoftDynamicsNavServer$[InstanceName]"—it should return a status of "Running."

For license management, add a line to import your license file: Import-NavLicense -Path "C:\Licenses\NAV2017.lic". This ensures the system recognizes your deployment rights immediately. I always test the license import in a non-production environment first—some license files have strict server binding requirements that can cause headaches if overlooked.

Save your script and test it manually by running .\NAV2017Install.ps1. Monitor the process in real-time using Get-WinEvent -LogName Application | Where-Object {$.Id -eq 1030} to track installation events. If you see errors, they’ll appear here immediately—don’t ignore them.

Once validated, schedule the script for unattended deployment using schtasks. For example, run schtasks /create /tn "NAV2017Deployment" /tr "PowerShell.exe -ExecutionPolicy Bypass -File 'C:\NAV2017Deployment\NAV2017_Install.ps1'" /sc once /st 02:00 to trigger the install at 2 AM. This timing avoids interfering with business operations during peak hours.

After deployment, log into the NAV Web Client or RoleTailored Client to verify functionality. Navigate to Help > About—the version should display as Microsoft Dynamics NAV 2017. If the client fails to launch, check the Event Viewer under Windows Logs > Application for errors related to MicrosoftDynamicsNavClient or SQL Server.

Real talk: The most common pitfall is missing prerequisites. Always run Get-WindowsFeature before deployment to confirm .NET Framework 4.6.2 and Windows Identity Foundation 3.5 are installed. If they’re missing, add them silently with Add-WindowsFeature -Name Net-Framework-Core,WIF-3.5 before running NAV.

Tips & tricks for PowerShell NAV 2017 deployment

These battle-tested insights will help you avoid the most common pitfalls during your NAV 2017 PowerShell deployment—saving you hours of troubleshooting down the road.

Prerequisite Verification: Before running your script, I can't stress enough how critical it is to verify all prerequisites. In Step 1, when you're preparing your environment, run Get-WindowsFeature and check for .NET Framework 4.6.2 and Windows Identity Foundation 3.5 specifically. These are non-negotiable for NAV 2017. I've seen deployments fail silently because these were missing—don't make that mistake. If they're not installed, add them silently with Add-WindowsFeature -Name Net-Framework-Core,WIF-3.5 before proceeding. This should be your first step after setting up the deployment folder.

Script Testing Strategy: In Step 4, when you're ready to test your script manually, don't just run it once and hope for the best. I recommend testing three times with different parameters: first with the /norestart flag, then without it to see the reboot behavior, and finally with the ADDLOCAL=ALL parameter modified to install only specific components. This helps you understand exactly how each parameter affects the deployment process. Also, always test in a virtual machine first—it's the safest way to catch issues without risking your production environment.

Error Handling Enhancement: While the instructions cover basic error tracking with Get-WinEvent, I've found that adding a more robust error handling section to your script prevents silent failures. In Step 4, after your Start-Process commands, add this verification block: try { $process = Start-Process -FilePath "NAV2017.exe" -ArgumentList "/qn /norestart ADDLOCAL=ALL" -PassThru $process.WaitForExit() if ($process.ExitCode -ne 0) { Write-Error "NAV installation failed with exit code $($process.ExitCode)" } } catch { Write-Error "Installation error: $_" } This gives you explicit error messages instead of just watching the event logs.

License File Location: One common oversight in Step 3 is the license file path. I've seen many deployments fail because the license file wasn't in the exact specified location. Create a dedicated C:\Licenses folder and place your NAV2017.lic file there before running your script. You can also add a path verification check to your script: $licensePath = "C:\Licenses\NAV2017.lic" if (-not (Test-Path $licensePath)) { Write-Error "License file not found at $licensePath"; exit 1 } This simple check prevents hours of frustration later.

Frequently asked questions

Got questions about installing Microsoft Dynamics NAV 2017 with PowerShell? You’re not alone! Below are answers to the most common concerns—from setup hiccups to time-saving tips.

Wrapping up and next steps

You’ve now unlocked the power of PowerShell to streamline your Microsoft Dynamics NAV 2017 installation! 🎉 By automating the process, you’ve saved time, reduced manual errors, and gained flexibility—whether for testing, deployment, or scalability. This script isn’t just a shortcut; it’s a foundation for efficient system management in your workflow.

Ready to take the next step? Explore customizing your script further—add logging, error handling, or even integrate it with your CI/CD pipeline. Your automation journey has just begun! 🚀