Install Microsoft Dynamics NAV 2017 With PowerShell: Streamlined Deployment Script

I remember the first time I automated a Dynamics NAV deployment back in my Microsoft days. PowerShell turned a 4-hour manual slog into a 15-minute scripted breeze.

Helping Dad rebuild those old IBMs taught me the value of repetition. This method eliminates human error from the NAV 2017 install process with a single, reusable script you can adapt across environments.

You’ll get a consistent, reproducible setup every time, whether you’re deploying to one server or a dozen. The script handles prerequisites, configuration, and verification automatically.

Works on Windows Server 2012 R2 through 2019. No more missed checkmarks or forgotten services.

What Youll Need

Instructions

This method delivers a clean, automated setup that saves hours of manual configuration.

Open PowerShell as Administrator—I always verify by checking the title bar says “Administrator: Windows PowerShell.” This prevents permission errors during installation. Set the execution policy to allow scripts with Set-ExecutionPolicy RemoteSigned -Force.

Install the Windows Assessment and Deployment Kit (ADK) if it’s not already present. This provides necessary cmdlets for the deployment. Run Get-WindowsCapability -Online | Where-Object Name -like ‘ADK*’ to confirm the components are available.

Download the Microsoft Dynamics NAV 2017 installation media from the official Microsoft site. I recommend using the DVD ISO for consistency. Mount the ISO and copy the contents to a local folder like C:\NAV2017.

Verify the extracted files by checking for the Setup.exe and Prerequisites folders. Missing files indicate a corrupted download, and you’ll need to repeat this step. This ensures all components are ready for the script.

Create a new PowerShell script file named DeployNAV2017.ps1 in the same directory as the extracted files. Use a text editor like Notepad++ for accuracy. Start the script with the Install-NAVServer cmdlet, specifying the server instance name and service account.

Include parameters for the Database Server, Database Name, and Service Account. For example, Install-NAVServer -ServerInstance NAV2017 -DatabaseServer .\SQLEXPRESS -DatabaseName “Demo Database NAV (10-0)” -ServiceAccount “DOMAIN\NAVService”. This ensures the server installs with your specific configuration.

Run the script from the PowerShell window by navigating to the directory with cd C:\NAV2017 and executing .\DeployNAV2017.ps1. Watch for any errors in the console output—red text indicates issues that need immediate attention.

Wait for the script to complete without errors. You’ll see a confirmation message when the installation finishes successfully. This typically takes 10-20 minutes depending on your system’s performance.

Open the Microsoft Dynamics NAV 2017 Administration console to confirm the server instance is running. Check that the service status shows Running and the Database is connected.

Launch the NAV Windows Client and connect to the server instance. Verify you can log in and see the default demo data. If you encounter connection issues, double-check the service account permissions and database connectivity in the administration console.

Tips and Common Mistakes

These insights will help you avoid the most common pitfalls during deployment.

Execution Policy Precision: In Step 1, don’t skip the -Force parameter with Set-ExecutionPolicy RemoteSigned. I learned this the hard way after getting permission prompts that stalled the process. This single flag ensures the policy change takes effect immediately without confirmation dialogs.

Verification Strategy: When confirming ADK components in Step 1, run the verification command twice. The first run initializes the check, while the second confirms all dependencies are properly registered. Missing this can lead to silent failures during script execution.

Script Location Matters: For Step 3, always create your DeployNAV2017.ps1 in the same directory as your extracted files. I once placed it on the desktop and spent hours troubleshooting path errors. The script relies on relative paths to locate installation files.

Monitoring Technique: During Step 4’s execution, pipe the output to a log file using .\DeployNAV2017.ps1 | Out-File -FilePath C:\NAV2017\log.txt. This lets you review errors after the fact, especially useful for the 10-20 minutes the process typically takes.

Frequently Asked Questions

Installing Microsoft Dynamics NAV 2017 with PowerShell simplifies deployment, saves time, and reduces manual errors. 🎯 By automating the process, you ensure consistency and free up resources for other critical tasks. Ready to take the next step? Test your script in a sandbox environment before rolling it out to production!