Microsoft Dynamics NAV

Requirements for Microsoft Dynamics NAV 2013

System Requirements for Microsoft Dynamics NAV 2013 ......................................................................................... 1 System Requirements for the Microsoft Dynamics NAV Windows Client ..............................................................1 System Requirements for Microsoft Dynamics NAV 2013 Web Client ...................................................................2 System Requirements for Microsoft Dynamics NAV Server ...................................................................................3 System Requirements for Microsoft Dynamics NAV 2013 Database Components for SQL Server ........................5 System Requirements for Microsoft Dynamics NAV Portal Framework for Microsoft SharePoint 2010 ...............5 System Requirements for Automated Data Capture System for Microsoft Dynamics NAV 2013 ..........................6 System Requirements for Microsoft Office Outlook Add-In ...................................................................................6 Installation Considerations for Microsoft SQL Server ................................................................................................ 7 SQL Server Components to Install...........................................................................................................................9 SQL Server Components ......................................................................................................................................9 Setup Options for Microsoft SQL Server .................................................................................................................9 Instance Configuration ........................................................................................................................................9 Server Configuration ............................................................................................................................................9 Data Encryption Between Microsoft Dynamics NAV Server and SQL Server .........................................................9 Product Architecture ................................................................................................................................................ 10 The Microsoft Dynamics NAV Three-Tier Architecture........................................................................................ 10 Additional Components ....................................................................................................................................... 11

SYSTEM REQUIREMENTS FOR MICROSOFT DYNAMICS NAV 2013

The following sections list the minimum hardware and software requirements to install and run Microsoft Dynamics NAV 2013. Minimum means that later versions (such as SP1, SP2, or R2 versions) of a required software product are also supported. Note For updated System Requirements, see the Microsoft Dynamics NAV page on the microsoft.com site.

SYSTEM REQUIREMENTS FOR THE MICROSOFT DYNAMICS NAV WINDOWS CLIENT

The following table shows the minimum system requirements for the Microsoft Dynamics NAV Windows client. Operating system The Microsoft Dynamics NAV Windows client runs on the following versions of Windows:

Windows 8 Professional or Enterprise (32-bit or 64-bit editions). Windows 7 Professional, Enterprise, or Ultimate (32-bit or 64-bit editions). Windows Server 2012. Windows Server 2008 R2. Windows Server 2008 (32-bit or 64-bit editions).

On 64-bit editions of Windows, the Microsoft Dynamics NAV Windows client runs in WOW64 emulation mode. Hardware resources Hard disk space:

30 MB.
Memory:

1 GB.
Additional software

Microsoft .NET Framework 4.5.

Microsoft Dynamics NAV 2013 Setup installs this software if it is not already present on the target computer.

Microsoft Lync 2010 or Microsoft Office Communicator 2007 is required for Microsoft Office 2010 is required for mail merge. Microsoft Office 2010 or
Microsoft Office 2007 SP1 is required for Outlook client integration, budget import and export to and from Microsoft Excel and Office XML, and SharePoint links. Note Microsoft Dynamics NAV 2013 Setup can only install the Excel Addin if Excel 2010 is present on the target computer. instant messaging and Telephony API (TAPI).

Microsoft Office 2010 is required for OneNote integration. However, OneNote

integration is not supported for 64-bit editions of Microsoft Office 2010 running REQUIREMENTS FOR MICROSOFT DYNAMICS NAV 2013 1

on Windows Server 2008. Active Directory and Microsoft Exchange Server 2010 are required for email logging. Reports You design and upgrade reports using the Microsoft Dynamics NAV Development Environment. By default, the development environment is installed with the Microsoft Dynamics NAV Windows client. You run reports in the Microsoft Dynamics NAV Windows client or on Microsoft Dynamics NAV Server.

Microsoft Visual Studio 2010 SP1 Professional, Premium, or Ultimate and

Microsoft Report Viewer 2010 SP1 are required for designing reports in the development environment. Microsoft Dynamics NAV 2013 Setup installs Microsoft Report Viewer 2010 SP1 if it is not already present on the target computer.

Microsoft SQL Server Report Builder for Microsoft SQL Server 2012 or Microsoft
SQL Server 2008 R2 Report Builder 3.0 is required for updating reports in the development environment. Microsoft Dynamics NAV 2013 Setup installs Microsoft SQL Server Report Builder for Microsoft SQL Server 2012 if none of the above is already installed on the target computer. Setup only installs Microsoft SQL Server Report Builder for Microsoft SQL Server 2012 if the development environment is included in the install.

Microsoft Report Viewer 2010 SP1 is required for running reports in the Microsoft
Dynamics NAV Windows client or on Microsoft Dynamics NAV Server. Microsoft Dynamics NAV 2013 Setup installs this software if it is not already installed on the target computer.

SYSTEM REQUIREMENTS FOR MICROSOFT DYNAMICS NAV 2013 WEB CLIENT

The following table shows the minimum system requirements for the Microsoft Dynamics NAV 2013 web client. Server component

Microsoft .NET Framework 4.5.

Microsoft Dynamics NAV 2013 Setup installs this software if it is not already present on the target computer.

Internet Information Server 7.0 on Windows 7, Windows Server 2008, and

Windows Server 2008 R2 or Internet Information Server 8.0 on Windows 8 and Windows Server 2012. The following features must be enabled:

.NET Extensibility in IIS 7.0 or .NET Extensibility 4.5 in IIS 8.0 ASP .NET in IIS 7.0 or ASP .NET 4.5 in IIS 8.0 ISAPI Extensions ISAPI Filters 2

REQUIREMENTS FOR MICROSOFT DYNAMICS NAV 2013

Request Filtering Windows Authentication Static Content HTTP Activation For more information, see How to: Install Internet Information Services for Microsoft
Dynamics NAV Web Client

Note Microsoft Dynamics NAV 2013 Setup installs IIS with the required features enabled if it is not already present on the target computer.

Report Viewer 2010.

Supported browsers Note The browser must be able to install the Report Viewer ActiveX control to be able to print. Supported:

Internet Explorer 9 or Internet Explorer 8 on Windows 7, Windows Server 2008

R2, or Windows Server 2008 (32-bit or 64-bit editions).

Supported with limitations:

Internet Explorer 10 on Windows 8 or Windows Server 2012. Google Chrome 16 on Windows 7, Windows Server 2008 R2, or Windows Server Mozilla Firefox 9 on Windows 7, Windows Server 2008 R2, or Windows Server Safari 5.1.2 on iOS (iPad).
2008 (32-bit or 64-bit editions). 2008 (32-bit or 64-bit editions).

For a list of limitations, see Browser Limitations with the Microsoft Dynamics NAV Web Client.

SYSTEM REQUIREMENTS FOR MICROSOFT DYNAMICS NAV SERVER

The following table shows the minimum system requirements for Microsoft Dynamics NAV Server. Operating system Microsoft Dynamics NAV Server only runs on 64-bit editions of the following versions of Windows:

Windows 8 Professional or Enterprise. Windows 7 Professional, Ultimate, or Enterprise. Windows Server 2012. Windows Server 2008 R2. 3

REQUIREMENTS FOR MICROSOFT DYNAMICS NAV 2013

 Windows Server 2008.

Warning The Microsoft Dynamics NAV Server Administration tool does not run on Windows Server 2008. It does run on Windows Server 2008 R2.

Windows Small Business Server 2008. Windows Small Business Server 2011
Hardware resources Hard disk space:

500 MB.
Memory:

2 GB.
Additional software

Microsoft .NET Framework 4.5.

Microsoft Dynamics NAV 2013 Setup installs this software if it is not already present on the target computer.

Active Directory is required for the Microsoft Dynamics NAV Portal Framework for Windows PowerShell 2.0 is required for the cmdlets for Microsoft Dynamics NAV
Administration. Windows PowerShell 2.0 is included with Windows Server 2008 R2 and Windows 7. Microsoft Report Viewer 2010 is required for Save as Excel or Save as PDF functionality. Microsoft Dynamics NAV 2013 Setup installs this software if it is not already present on the target computer. Microsoft SharePoint 2010.

REQUIREMENTS FOR MICROSOFT DYNAMICS NAV 2013

SYSTEM REQUIREMENTS FOR MICROSOFT DYNAMICS NAV 2013 DATABASE COMPONENTS FOR SQL SERVER
The following table shows the minimum system requirements for Microsoft Dynamics NAV 2013 database components for SQL Server. SQL Server The database components run on the following versions and editions of SQL Server:

Microsoft SQL Server 2008 R2 Express, Workgroup, Standard, or Enterprise (64-bit Microsoft SQL Server 2008 Express, Workgroup, Standard, or Enterprise (64-bit
editions only). The 64-bit edition of SQL Server 2012 Express is automatically installed before the Microsoft Dynamics NAV 2013 database components by Microsoft Dynamics NAV 2013 Setup if a supported SQL Server product is not already installed on the target computer. If the operating system on the target computer does not support SQL Server 2012 Express (for example, Windows Server 2008), Setup displays a pre-requisite warning. In this case you should exit Setup and then update the operating system on the computer to one that does support SQL Server 2012 Express (for example, Windows Server 2008 SP2 or Windows Server 2008 R2 SP1). Then run Setup again. editions only).

SYSTEM REQUIREMENTS FOR MICROSOFT DYNAMICS NAV PORTAL FRAMEWORK FOR MICROSOFT SHAREPOINT 2010
The following table shows the minimum system requirements for Microsoft Dynamics NAV Portal Framework for Microsoft SharePoint 2010. Operating system Microsoft Dynamics NAV Portal Framework for Microsoft SharePoint 2010 runs on the following versions of Windows:

Windows Server 2012. Windows Server 2008 R2. Windows Server 2008 (64-bit editions only).
Additional software

Microsoft .NET Framework 3.5.

Microsoft Dynamics NAV 2013 Setup installs this software if it is not already present on the target computer.

Microsoft SharePoint Foundation 2010, SharePoint Server 2010, or SharePoint SQL Server 2008 R2 (64-bit editions only) or SQL Server 2008 (64-bit editions only).
Supported browsers Browser requirements are provisional and might be subject to change before the original release of Microsoft Dynamics NAV 2013, based on partner feedback and 5 Server 20102 SP1.

REQUIREMENTS FOR MICROSOFT DYNAMICS NAV 2013

schedule constraints. Supported:

Internet Explorer 9 or Internet Explorer 8 on Windows 7, Windows Server 2008

R2, or Windows Server 2008 (32-bit or 64-bit editions). Supported with limitations:

Internet Explorer 10 on Windows 8 or Windows Server 2012. Google Chrome 16 on Windows 7, Windows Server 2008 R2, or Windows Server Mozilla Firefox 9 on Window 7, Windows Server 2008 R2, Windows Server 2008
(32-bit or 64-bit editions). For a list of limitations, see Browser Limitations with the Microsoft Dynamics NAV SharePoint Client. 2008 (32-bit or 64-bit editions).

SYSTEM REQUIREMENTS FOR AUTOMATED DATA CAPTURE SYSTEM FOR MICROSOFT DYNAMICS NAV 2013
The following table shows the minimum system requirements for Automated Data Capture System (ADCS) for Microsoft Dynamics NAV 2013. Additional software

MSXML version 6.0. Telnet or Microsoft Windows HyperTerminal.

Note HyperTerminal is no longer included with Windows. For more information, see What happened to HyperTerminal? in the Windows Help.

VT100 Plug-in, which acts as a virtual Telnet server and is required for each Microsoft Loopback Adapter.
computer on which you install ADCS.

SYSTEM REQUIREMENTS FOR MICROSOFT OFFICE OUTLOOK ADD-IN

The following table shows the system requirements for the Microsoft Office Outlook Add-In. Additional software A 32-bit edition of Microsoft Office 2007 or 2010.

REQUIREMENTS FOR MICROSOFT DYNAMICS NAV 2013

INSTALLATION CONSIDERATIONS FOR MICROSOFT SQL SERVER

This topic describes the requirements for installing and configuring Microsoft SQL Server to work with Microsoft Dynamics NAV 2013.

HARDWARE GUIDE FOR SQL SERVER

STANDARD HARDWARE AND SYSTEM REQUIREMENTS

Windows Edition (min.)

SQL Server Edition (min.)

Concurrent Number of Users

SQL Database Size

Processors or Processor Cores (min.)

RAM (GB) (min.)

Network Interface Card (min.)

Microsoft Windows 2012 Server Standard Edition 64-bit Microsoft Windows 2012 Server Standard Edition 64-bit Microsoft Windows 2012 Server Standard Edition 64-bit Microsoft Windows 2012 Server Enterprise Edition 64-bit Microsoft Windows 2012 Server Enterprise Edition 64-bit Microsoft Windows 2012 Server Enterprise Edition 64-bit

Microsoft SQL Server 2012 Standard Edition 64-bit Microsoft SQL Server 2012 Standard Edition 64-bit Microsoft SQL Server 2012 Standard Edition 64-bit Microsoft SQL Server 2012 Enterprise Edition 64-bit Microsoft SQL Server 2012 Enterprise Edition 64-bit Microsoft SQL Server 2012 Enterprise Edition 64-bit

10

Very Small 2 x 3GHz (5GB) 2MB L3 Cache Small (5-40GB) 2 x 3GHz 2MB L3 Cache 4 x 3GHz 2MB L3 Cache 4 x 3GHz 2MB L3 Cache 6 x 3GHz 2MB L3 Cache 8 x 3GHz 2MB L3 Cache

4GB

100Mb Ethernet LAN 1Gb Ethernet LAN / Fibre 2Gb Ethernet LAN / Fibre 2Gb Ethernet LAN / Fibre 2Gb Ethernet LAN / Fibre 2Gb Ethernet LAN / Fibre

11-50

4GB

51-100

Medium (40-80GB)

8GB

101-150

Medium (40-80GB)

16GB

151-200

Large (80160GB) Velika (>160GB)

16GB

201-250

32GB

INSTALLATION CONSIDERATIONS FOR MICROSOFT SQL SERVER AND PRODUCT ARCHITECTURE

STORAGE FOR MICROSOFT SQL SERVER

Storage Solution (min.) Technology (min.) SQL Database Size Concurrent Number of Users Number of Disks for Data (min.) Number of Disks for Transaction Log (min.)

Internal Storage Internal Storage or Direct Attached Storage (DAS) Direct Attached Storage (DAS) or Storage Area Network (SAN) Storage Area Network (SAN)

SAS SCSI SAS SCSI

Very Small (10GB) Small (1140GB)

10

2 HDD Mirrored @ 10-15K 1 HDD Mirrored @ 10-15K RPM RPM RAID 1 RAID 1 4-6 HDD+ Mirrored @ 15K 2 HDD Mirrored @ 15K RPM RPM RAID 10 RAID 10

11-50

SAS SCSI Fiber/SCSI

Medium (4180GB)

51-150

8-12 HDD+ Mirrored @ 15K RPM RAID 10

4 HDD Mirrored @ 15K RPM RAID 10

Fiber/SCSI Large Fiber/Fiber (>80GB)

151-250

12-18 HDD+ Mirrored @ 15K RPM RAID 10

8 HDD Mirrored @ 15K RPM RAID 10

EXAMPLE: C:\.... Operating System, Page File, and SQL Server program files D:\....\data SQL data files (*.mdf and *.ndf) E:\....\NAVlog SQL log file (*.ldf) F:\....\back-up SQL database and transaction log back-ups + The two numbers specified for the recommend numbers of spindles (drives) it meant to cover both ends of the concurrent users count spectrum for that section. For example, with the concurrent user count of 11-50 the recommend number of spindles (drives) for the lower end of that range would be 2 and the recommended number of spindles (drives) for the upper end of the range would be 6. It is also recommend that you have a separate set of disks for the SQL database back-ups and transaction log back-ups. We recommend that the log file drive for each SQL Server database be a separate set of physical and logical drives. For best performance, you always want the read/write head of the disk at the end of the log file and if multiple log files reside on the same set of disks, the read/write head will need to switch back and forth potentially causing performance issues. Microsoft Dynamics NAV is not a heavy user of TempDB; the decision of whether or not to place TempDB on its own set of drives will depend on the volume and usage of each individual customer and must be evaluated individual basis. The same goes for the usage of extra SQL data files and file groups, these decisions must be evaluated on an individual basis. STRIPE SIZE AND DISK ALIGNMENT

INSTALLATION CONSIDERATIONS FOR MICROSOFT SQL SERVER AND PRODUCT ARCHITECTURE

Disk alignment can have a significant impact on disk performance. Since proper configuration can vary greatly by manufacturer, please consult your hardware manufacturing to verify the proper disk alignment and offset settings. The allocation or stripe size should be >=8k to prevent torn pages we recommend 64k to match the size of the SQL Server Extent (8 8K pages).

SQL SERVER COMPONENTS TO INSTALL

Microsoft Dynamics NAV 2013 is compatible with 64-bit editions of SQL Server 2012, SQL Server 2008, and SQL Server 2008 R2. 32-bit editions are no longer supported.

SQL SERVER COMPONENTS

If you are installing SQL Server to use with Microsoft Dynamics NAV, then install the following components: Database Engine Services Client Tools Connectivity Management Tools - Complete

SETUP OPTIONS FOR MICROSOFT SQL SERVER

When you are running Microsoft SQL Server Setup, you must provide additional information. Your responses can affect how you use SQL Server with Microsoft Dynamics NAV 2013.

INSTANCE CONFIGURATION
If you plan on installing the Microsoft Dynamics NAV Demo database with Microsoft Dynamics NAV 2013, and you want Microsoft Dynamics NAV Setup to use an already installed version of SQL Server (and not to install SQL Server 2012 Express) you must create a SQL Server instance named NAVDEMO in SQL Server before you install Microsoft Dynamics NAV 2013. Otherwise, Microsoft Dynamics NAV Setup will install SQL Server 2012 Express automatically, even if there is a valid version of SQL Server already on the computer. If you do not plan to install the Demo database, or if you have no objection to using SQL Server 2012 Express, you are free to use the default instance and Instance ID on the Instance Configuration page, or to specify any instance name.

SERVER CONFIGURATION
We recommend that you use a dedicated domain user account that you create specifically for your Microsoft Dynamics NAV Server instances and for your Microsoft Dynamics NAV instance on SQL Server, instead of a Local System account or the Network Service account.

DATA ENCRYPTION BETWEEN MICROSOFT DYNAMICS NAV SERVER AND SQL SERVER
When SQL Server and Microsoft Dynamics NAV Server are running on different computers, you can make this data channel more secure by encrypting the connection with IPSec. (Other encryption options are not supported.) For information on how to do this, see Encrypting Connections to SQL Server, which is part of SQL Server 2008 Books Online in MSDN library.

INSTALLATION CONSIDERATIONS FOR MICROSOFT SQL SERVER AND PRODUCT ARCHITECTURE

PRODUCT ARCHITECTURE
The Microsoft Dynamics NAV 2013 architecture comprises three core components as well as various additional tools and components. Use Microsoft Dynamics NAV Setup to install all components.

THE MICROSOFT DYNAMICS NAV THREE-TIER ARCHITECTURE

For every deployment of Microsoft Dynamics NAV 2013 you must install the core components, which are the three tiers that make up the Microsoft Dynamics NAV architecture. 1. The RoleTailored client is the client tier, which includes a Microsoft Dynamics NAV Windows client and a Microsoft Dynamics NAV Web client. In addition to the RoleTailored client, Microsoft Dynamics NAV 2013 also supports additional client types, including web service clients, a SharePoint client through Microsoft Dynamics NAV Portal Framework, and a NAS services client for programmatic access. For details on the various client types, see Client Types. 2. Microsoft Dynamics NAV Server is the middle or server tier, managing all business logic and communication. 3. SQL Server, augmented by Microsoft Dynamics NAV 2013 database components, is the data tier.

Important
When you install Microsoft Dynamics NAV 2013, all components must be from the same version and build of Microsoft Dynamics NAV for the software to run correctly.

You can have multiple instances of any of the core components in a production environment. The following diagram shows a simple installation with two Microsoft Dynamics NAV Windows clients and a Microsoft Dynamics NAV Web client connecting to a single Microsoft Dynamics NAV Server computer, which in turn connects to a computer with SQL Server and the Microsoft Dynamics NAV database components.

INSTALLATION CONSIDERATIONS FOR MICROSOFT SQL SERVER AND PRODUCT ARCHITECTURE

10

Some common configurations are: All three components on the same computer. This is the configuration for a demo install, and is also typical for a development environment, so that a developer can work on Microsoft Dynamics NAV applications without worrying about network connections and inter-component security. See Walkthrough: Installing the Demo Version. RoleTailored client and Microsoft Dynamics NAV Server on the same computer, data tier on a separate computer. This scenario is described in Walkthrough: Installing the Three Tiers On Two Computers. Each of the three tiers on a separate computer. This scenario is described in Walkthrough: Installing the Three Tiers on Three Computers.

ADDITIONAL COMPONENTS
In addition to the three core components, there are additional components that enhance or supplement the core components. Component
Microsoft Dynamics NAV Server Administration Tool

Purpose A tool for configuring and managing Microsoft Dynamics NAV Server and Microsoft Dynamics NAV sites.

Microsoft Dynamics NAV Portal Framework for Microsoft SharePoint

A set of components that you use to build SharePoint web applications that display Microsoft Dynamics NAV pages and reports.

Development Environment (C/SIDE)

The Development Environment for creating and modifying Microsoft

INSTALLATION CONSIDERATIONS FOR MICROSOFT SQL SERVER AND PRODUCT ARCHITECTURE

11

Dynamics NAV applications in C/AL.

Microsoft Office Outlook Add-In

A component for synchronizing data, such as to-dos, contacts, and tasks, between Microsoft Dynamics NAV and Outlook.

Automated Data Capture System

A Microsoft Dynamics NAV tool for accurately capturing data for inbound, outbound, and internal documents, primarily in connection with warehouse activities. With ADCS, company employees use handheld devices and radio frequency technology to continuously validate warehouse inventories.

WebMicrosoft DynamicsSee How to: integrated, adaptable business management solutions that NAV Server Components. is a line of The components that are needed to enable Microsoft Dynamics enables you and your people to Web clients to connect with a browser. confidence. Microsoft make business decisions with greater Install the Web Server Components for Dynamics works like and with the Microsoft Dynamics NAV Web Client. familiar Microsoft software, automating and streamlining financial,

customer relationship, and supply chain processes in a way that helps you drive business success.

ClickOnce Installer Tools. A set of tools designed to create ClickOnce deployments for applications See Deploying Microsoft Dynamics NAV for the Microsoft Dynamics NAV Windows client. United States and Canada toll free: (888) 477-7989 Using ClickOnce.

Worldwide: (1) (701) 281-6500 www.microsoft.com/dynamics

The information contained in this document represents the current view of Microsoft Corporation on the issues discussed as of the date of publication. Because Microsoft must respond to changing market conditions, this document should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information presented after the date of publication. This white paper is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED, OR STATUTORY, AS TO THE INFORMATION IN THIS DOCUMENT. Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in, or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation. Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property.

2012 Microsoft. All rights reserved. Microsoft, Microsoft Dynamics, the Microsoft Dynamics logo, Internet Explorer, Outlook, SharePoint, SQL Server, Windows, Windows PowerShell, and Windows Server are trademarks of the Microsoft group of companies.

INSTALLATION CONSIDERATIONS FOR MICROSOFT SQL SERVER AND PRODUCT ARCHITECTURE

12