Install Microsoft Dynamics Nav 2017 with Powershell: PowerShell Deployment in 5 Commands

Installing Microsoft Dynamics NAV 2017 with PowerShell cut my deployment time from hours to five commands—and I’ve done this dance enough times to know the shortcuts. Back in my uncle’s basement workshop in 1998, I learned that automation saves headaches; this is just that, but for enterprise software.

The real magic happens when you bypass the GUI and let PowerShell handle the heavy lifting, especially for IT admins juggling multiple environments.

You’ll need PowerShell 5.1 or later (NAV 2017’s sweet spot) and admin rights on the target machine, but the fun part is the commands themselves. Start with Install-Module -Name MicrosoftDynamicsNav—this pulls in the NAV-specific cmdlets you’ll use repeatedly.

Then Import-Module MicrosoftDynamicsNav loads them into your session, where they’ll handle everything from database setup to role assignments. The rest is just orchestration: New-NAVServerInstance, New-NAVDatabase, and New-NAVUser—each one a building block for a fully automated deployment.

Where most guides trip up is permissions. NAV 2017’s installer can be finicky about SQL Server access or service accounts, so run PowerShell as Administrator and pre-check your execution policy with Get-ExecutionPolicy. I’ve seen deployments fail silently because of this, and the error messages rarely point to the real issue.

Once you’ve got those basics locked down, the five-command workflow becomes foolproof—I’ve used it to spin up test environments in under 10 minutes, a timesaver that pays for itself on day one.

For the edge cases—like when your SQL Server instance isn’t listed or the NAV service won’t start—bookmark Microsoft’s NAV 2017 PowerShell deployment guide and keep Get-NAVServiceStatus in your toolkit. It’s saved me more than once when a deployment seemed stuck.

The key is treating PowerShell as your co-pilot, not just a script runner. Now let’s get into the commands that make this all click.

What you need

Step-by-Step instructions for deploying Microsoft Dynamics NAV 2017 via PowerShell

Here’s the streamlined approach I use to automate NAV 2017 deployment—no manual installer headaches.

Open an elevated PowerShell session as Administrator. First, verify the presence of the NAV Server installation media. The Microsoft Dynamics NAV Server 2017 setup files must be accessible from a local or network path—this is critical for script execution. I always mount the ISO or copy the contents to C:\NAV2017Setup to avoid path-related errors during deployment.

Run the following to ensure the Windows PowerShell execution policy allows script execution: Set-ExecutionPolicy RemoteSigned -Scope CurrentUser This prevents execution blocks that derail automation. Next, import the NAV module by navigating to the installation directory and loading the Microsoft.Dynamics.Nav.Model.Tools module. If this fails, the installation media may be corrupted—double-check the integrity of the downloaded files.

Create a new PowerShell script file (e.g., Deploy-NAV2017.ps1) and paste the core deployment command: `Install-WindowsFeature -Name "NAV-Server" -Source "C:\NAV2017Setup\NAVServer\amd64" -IncludeAllSubFeature` This command automates the NAV Server feature installation, pulling files directly from the mounted media. The -IncludeAllSubFeature flag ensures all dependencies (like SQL Server components) are bundled in one pass—this avoids fragmented installations that require manual intervention.

Monitor the progress until the script completes without errors. If you encounter access denied prompts, ensure the PowerShell session remains elevated. The installation typically takes 15-25 minutes, depending on system resources. Once finished, verify the service status by running: Get-Service -Name "MicrosoftDynamicsNavServer__MDLINK_GUARD_8__lt;InstanceName>" The service should show Running in the status column.

After the server install completes, switch to the NAV Development Shell (launched via Start > Microsoft Dynamics NAV > Development Environment). Here, you’ll deploy the NAV 2017 application database using a PowerShell one-liner: `New-NAVServerInstance -ServerInstance "NAV2017" -DatabaseName "NAV2017DB" -DatabaseServer "YourSQLServer" -LicenseFile "C:\NAV2017License.flf"` Replace YourSQLServer with your SQL instance name and ensure the license file (.flf) is accessible. This step ties the database to the server instance, enabling client connections.

Next, install the NAV client tools by running: Install-Package -Name "Microsoft.Dynamics.Nav.Client" -Version "14.0.0.0" -Force This ensures the RoleTailored Client and Web Client are available post-deployment. Verify the installation by launching the client from the Start menu—you should see the NAV 2017 tile without connection errors.

Open the NAV Administration Shell and run: Test-NAVServerConnection -ServerInstance "NAV2017" -DatabaseName "NAV2017DB" This command checks if the server can communicate with the database. If the test fails, review SQL permissions—ensure the NAV service account has sysadmin rights on the SQL instance. For permission errors, grant access via SQL Server Management Studio before retrying.

For deployment failures, check the Windows Event Viewer under Applications and Services Logs > Microsoft > Dynamics > NAV. Errors here often point to missing dependencies or corrupted setup files. If the NAV Server service fails to start, manually register the COM components by running: `cd "C:\Program Files\Microsoft Dynamics NAV\140\Service" && NAVServer.exe /register` This step is rarely needed but resolves COM registration issues that block service startup.

To streamline user setup, create a final script to configure default company data and permissions. Start by importing the NAV module again and running: `New-NAVCompany -ServerInstance "NAV2017" -CompanyName "DefaultCo" -Template "Standard Template"` This provisions a base company with default configurations. Next, assign user permissions: `New-NAVUserPermissionSet -UserName "AdminUser" -PermissionSetId "SUPER" -ServerInstance "NAV2017"` Replace AdminUser with your administrative account. Finally, export the configuration for backup: `Export-NAVConfiguration -ServerInstance "NAV2017" -Path "C:\NAVBackup\Config.xml"` This ensures you have a clean slate for future deployments or rollbacks.

With these steps, your NAV 2017 environment is fully deployed, validated, and ready for users. The entire process—from server install to client setup—takes under 45 minutes when executed sequentially.

Tips & tricks for PowerShell deployment of Microsoft Dynamics NAV 2017

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

Path Organization: I can't stress enough how critical this is: Always verify your NAV Server installation files are accessible at the exact path specified in Step 1. I've seen deployments fail because of a simple typo in the path—double-check that you've mounted the ISO to C:\NAV2017Setup or copied the files there. Consider creating a shortcut on your desktop to this folder for quick access during troubleshooting. The 15-25 minute installation window will pass much smoother when you're not hunting for files mid-script.

Execution Policy Pitfalls: The RemoteSigned execution policy in Step 1 is non-negotiable for this deployment. If you skip this or use a different policy, you'll encounter permission errors that derail the entire process. Here's what I do: After running Set-ExecutionPolicy, immediately verify it took effect by running Get-ExecutionPolicy. If it shows anything other than RemoteSigned, your script will fail. This is where most deployment attempts stall—don't be that person who assumes it worked when it didn't.

Service Account Preparation: Before you reach Step 4's validation, ensure your NAV service account has sysadmin rights on the SQL instance. I've seen deployments fail at the connection test because of this oversight. Create the service account with these permissions before starting the deployment—it's much easier to set up permissions before you need them rather than troubleshooting later. The connection test in Step 4 will either succeed completely or fail spectacularly—there's no in-between.

Backup Strategy: While the instructions don't explicitly mention this, I always create a system restore point before starting any NAV deployment. This is your safety net if something goes wrong during the 15-25 minute installation window. Windows includes this feature built-in—just search for "Create a restore point" in the Start menu. It takes two minutes and could save you hours of recovery work if the deployment encounters unexpected issues.

Frequently asked questions

Got questions about installing Microsoft Dynamics NAV 2017 with PowerShell? You’re not alone! Here are answers to the most common concerns—whether you're troubleshooting, optimizing, or just curious about the process.